On 7/29/06, Rony ronbillypop@yahoo.co.uk wrote:
In an office, there was a room with existing pcs on a lan with network of 192.168.0.0 and I had to setup 4 pcs in another room which were to be a seperate group. So I gave a different network id to this group and got them talking on a lan switch. However the printer was a lan based one on the first network so I linked the two switches with a cable. However I could not ping the other network. Ultimately I had to use the first network id itself and have seperate workgroups.
I don't know how to add routes in windows. In *Linux (*nix for that matter I guess) you do a 'route add' to specify the route to take when it encounters a packet of a certain destination.
I'll tell you how it is in Linux and you can look for similar functionality in windows. Probably some networking gurus (I'm not even close to being one) on list could explain better if this sounds fuzzy ;)
Config 1: Add host routes for all computers outside the home network. For this you use the route command to add host route (route add -host) to each of the computers in the foreign network. This is obviously very tedious. So I'd recommend config 2.
Config 2: Use an old box (one of the machines on your network should do I think) as a router. to route packets between them. That way you simply have to add a route to the router IP for the networks on either side. Eg: 1) Let router be 192.168.0.200 on one side and 192.168.1.200 on the other 2) For computers on the 192.168.0.0 network: 2.1) route add -net 192.168.1.0 -netmask <netmask> gw 192.168.0.200 dev $IFACE 3) For computers on the 192.168.1.0 network 3.1) route add -net 192.168.0.0 -netmask <netmask> gw 192.168.1.200 dev $IFACE
Read the manpages on the route command to know more about this. Needless to say you configure the router to forward packets either ways. You should be able to find this stuff on the net easily.
What do you mean by explicit route? Normally a router links 2 different networks.
route add -host $ip dev $IFACE It simply says that if a packet is destined for $ip then don't go through the gateway, it's directly connected to me.
Which is why my question rose in a way. I think we can always assume that the gateway is directly accessible so why not create a direct route to it at config time if it seems to be on a different network? Windows seems to do it automatically. Is it an error/flaw/security concern of any sort? Or is it just a "it's a bad design so we won't support it" thing?
Regards, Siddhesh