Linux CentOS 5.4 small three computer networking help
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Windows 7, RHEL 5.4, CENTOS 5.4, RHEL 6
Posts: 55
Rep:
Linux CentOS 5.4 small three computer networking help
Hi guys,
What I want to do is have two different networks connected with my switch. I want one computer to be the server and run dhcp with the ip address 10.3.2.1 and I want the other client machine to be 10.1.X.X. I want the X.X to be assigned automatically from DHCP running on the server. The subnet mask I believe should 255.255.255.0 for both networks. How can I get these two different networks to talk to each other when they are on completely different networks??
Without a router, you can't. Unless they are on the same subnet, which they will have to be in order to get DHCP working. your thread title mentions three machines. your content mentions two... maybe you're expecting this third machine to be involved?
Last edited by acid_kewpie; 01-19-2010 at 02:56 PM.
Distribution: Windows 7, RHEL 5.4, CENTOS 5.4, RHEL 6
Posts: 55
Original Poster
Rep:
Quote:
Originally Posted by acid_kewpie
Without a router, you can't. Unless they are on the same subnet, which they will have to be in order to get DHCP working. your thread title mentions three machines. your content mentions two... maybe you're expecting this third machine to be involved?
Thanks for your quick response. Well the third machine will most likely have the address 10.3.2.1 which i want to be able to talk to my server 10.3.2.1 but I dont want 10.3.2.1 to be able to talk to my the other client 10.1.X.X. I want this client to be able to see the server only? I'm so confused as even where to begin?
Hi guys,
What I want to do is have two different networks connected with my switch. I want one computer to be the server and run dhcp with the ip address 10.3.2.1 and I want the other client machine to be 10.1.X.X. I want the X.X to be assigned automatically from DHCP running on the server. The subnet mask I believe should 255.255.255.0 for both networks. How can I get these two different networks to talk to each other when they are on completely different networks??
well i'd suggest you're confused as, again, this makes no sense at all. in order to move between different IP subnets you need a Layer 3 device, e.g. a router, firewall, L3 switch or a forwarding server. If you take a server and give it two nics then it can be on both networks and off you go. Additionally, putting two different subnets in the same Layer 2 space (i.e. both on a dumb switch) is *really* *really* bad form too. very messy and against a trillion standards.
Distribution: Windows 7, RHEL 5.4, CENTOS 5.4, RHEL 6
Posts: 55
Original Poster
Rep:
Quote:
Originally Posted by acid_kewpie
well i'd suggest you're confused as, again, this makes no sense at all. in order to move between different IP subnets you need a Layer 3 device, e.g. a router, firewall, L3 switch or a forwarding server. If you take a server and give it two nics then it can be on both networks and off you go. Additionally, putting two different subnets in the same Layer 2 space (i.e. both on a dumb switch) is *really* *really* bad form too. very messy and against a trillion standards.
No there has to be a way to do it. If you set up different subnet masks I'm sure its possible. Its not really a different network but just so certain nodes can see each other and certain ones can't.
OK, well you go invent an entirely new set of networking protocols and standards. You have fun with that, let me know how it goes when you realise that actaully learning and following exisiting standards is a much better idea.
Distribution: Windows 7, RHEL 5.4, CENTOS 5.4, RHEL 6
Posts: 55
Original Poster
Rep:
[QUOTE=acid_kewpie;3833128]OK, well you go invent an entirely new set of networking protocols and standards. You have fun with that, let me know how it goes when you realise that actaully learning and following exisiting standards is a much better idea.[/QUOT
I guess I just invented something new because using a dummy switch I'm able to use different subnet masks to allow my 10.2.1.1 network talk to my 10.1.4.6 network and I also have a 10.4.X.X network that can only talk to my server and not to my 10.1.4.6 network.
"different subnets" presumably means breaking the standards that are there for very good reasons. If you want to describe in more detail what you've done, I can try and explain why it was such a bad idea ;-)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.