William C. VerSteeg (firstname.lastname@example.org)
18 Dec 87 19:55:12 GMT
The topic of discussion is how to tell a device that an IP network other
than his own is on his local cable. This _is_ an atypical configuration,
but one that can arise in the following situation.
A user has two ethernet cables joined by a link level (hardware address)
bridge. From each of these cables he has lots of IP traffic to the world
at large. He would want an IP router for each cable. The network numbers
should be different to limit traffic on the link level bridge. If the IP
network numbers were the same, the world would be forced to guess which
IP router to use, thus increasing load on the link level bridge.
Assuming distinct IP network numbers, an IP speaking
device on the first cable would then think that it had
to go out the IP router to the world. Each packet would then
rattle around the world, then go back in the second cable's
router to gain access to a machine on the other cable. A more efficient,
direct method would be to use the link level bridge.
This could be done in two ways that I know of.
This archive was generated by hypermail 2.0b3 on Thu Mar 09 2000 - 14:40:15 GMT