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?
|
Quote:
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.
|
Quote:
|
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.
|
[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 ;-)
|
All times are GMT -5. The time now is 06:23 PM. |