[lug] routing

[John Hernandez]

assuming that your workstation knows how to get to 192.168.0.4
(presumably via arp), try this:

route add -net 172.16.0.0 netmask 255.255.255.0 gw 192.168.0.4

maybe it wants the netmask argument too.

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).
> 
> Hugh
> 
> John Hernandez wrote:
> >
> > The setup for your second masquerading box will be essentially the same
> > as the box that masquerades your Internet traffic.  Define the internal
> > network, the external interface, and run ipchains ... -j MASQ or
> > iptables...
> >
> > http://www.linuxdoc.org has lots of HOWTO's regarding ipchains,
> > masquerading, etc.
> >
> > The tricky part is probably the routing on your 192.* nets.  Optimally,
> > individual nodes should have enough information to decide where to send
> > an IP datagram destined for 172.16.*, in addition to the default route.
> > This would involve either running an IGRP such as RIP or OSPF, or adding
> > static routes to nodes (easy to do for three workstations).
> > Alternatively, you can stick with default routing and have your Internet
> > router/masquerader could issue ICMP redirects, assuming it knows about
> > the 172.16.* route.
> >

-- 

John Hernandez, Network Engineer --------------------------------------
US Department of Commerce                             tel: 303-497-6392
NOAA/OAR - Mailstop R/OM12                            fax: 303-497-6005
325 Broadway                            e-mail: John.Hernandez at noaa.gov
Boulder, CO 80303                               http://boulder.noaa.gov
-----------------------------------------------------------------------