On Fri, 2002-10-11 at 12:56, nate wrote: > Elizabeth Barham said: > > "nate" <[EMAIL PROTECTED]> writes: > > > >> david hong said: > > > So, if there is a host 192.168.0.11, and David attempts to ping it, the > > packet may *not* go out eth1 (in this example)? > > it might go out eth1, I am not certain. but 192.168.0.11 is a locally > connected system which doesn't require a gateway to access. the > problem comes into play when your trying to route through the gateway > on the 2nd interface in my experience.
I agree. But I don't even know if this is what David was asking, as his mail is very short and terse. If you want a dual gateway system (ie. two DEFAULT routes) that your system balances between (like having two ISP's), then have a read of the Advanced-Routing-HOWTO. If however its just an internal lan (192.168.*.*) and the world at large on the other interface, then the 192.168.*.* interface shouldn't have a gateway entry at all. More explanation of what your trying to achieve might be of aid here, David. Kind Regards Crispin Wellington
signature.asc
Description: This is a digitally signed message part
