[lug] routing

Michael J. Pedersen marvin at keepthetouch.org
Fri Jan 12 13:24:08 MST 2001

On Fri, Jan 12, 2001 at 02:14:26PM -0600, charles at lunarmedia.net wrote:
> I'm not quite following what you mean by the 192.168 address is unable to
> match on that network. Linux should be able to add a route with any subnet
> mask all the way through /32 for routing purposes. If the local lan is
> 192.168.0/24 with a static route for 172.16/16 and a gateway of
>, I don't see what additional configuration would be required
> for the packet to exit the network correctly towards 172.16/16.
> I think however that the problem he may run into is for the return path of
> the packet. Even though you he may have his local lan configured
> correctly, to have packets destined for 172.16/16 to be sent to
>, all the machines on the 172.16/16 network, will need to be
> configured such that in order to reach 192.168.0/24, they will need to
> have a route set to hit the 172.16/16 of his dual interface machine.
> If you could elaborate on how the netmask would prevent this routing from
> occurring, I'd appreciate it.

Simply put, it was a misread. I thought he was trying to set the default
gateway for machines in the 172 network to use as the gateway.

Please pardon, it's turning out to be a very long week.

Michael J. Pedersen
My GnuPG KeyID: 4E724A60        My Public Key Available At: wwwkeys.pgp.net
My GnuPG Key Fingerprint: C31C 7E90 5992 9E5E 9A02 233D D8DD 985E 4E72 4A60
GnuPG available at http://www.gnupg.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <http://lists.lug.boulder.co.us/pipermail/lug/attachments/20010112/59ff1fb2/attachment.pgp>

More information about the LUG mailing list