[lug] routing

[Michael J. Pedersen]

On Fri, Jan 12, 2001 at 01:34:53PM -0500, Hugh Brown wrote:
> My problem is I'm not sure what I set as the static route.  I tried to
> do
> 
> route add -net 172.16.0.0 gw 192.168.0.4 
> 
> and it told me that it wasn't feasible.  My thought was that I want all
> traffic destined for the net 172.16.0.0/24 to use 192.168.0.4 as the
> router.  So what static route can I add (I do only have 3 workstations
> so that will be easiest until I get more savvy about network things).

There's a mild trick to this that's easy to miss. 172.16.0.0 has a netmask of
255.255.0.0 (most likely). 192.168.0.4 cannot match that netmask, as such it
can't be found on the 172.16 network. As such, it can NOT be a gateway for
what you are trying to do. However, it is possible to do so. I'm gonna need a
few minutes to describe everything, so wanted to give you a short heads up.
I'll be sending another email in a minute.

-- 
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/d4343158/attachment.pgp>