[lug] 3 Port Linux router

Nate Duehr nate at natetech.com
Tue Jun 12 18:09:06 MDT 2001


And if IP forwarding is turned on, is the 172 network expecting to see
only 172 network traffic?  Do you need IPMasq rules in IPCHAINS here to
masquerade the traffic out the 172 inteface as 172 network addresses?

On Tue, Jun 12, 2001 at 04:56:10PM -0600, Chip Atkinson wrote:
> Is IP forwarding turned on?  Are there any firewalling rules?  Can you 
> ping from a machine on 10.0.18 to 10.0.19.x?
> 
> Applegate,Kris wrote:
> 
> > We have an ambitious project that we are working on. We are currently
> > borrowing a Cisco 7200 from another division in order to do some routing
> > for one of our setups. We have been trying to build a Linux router that
> > will take the pace of the Cisco so we can give it back. The hitch is
> > that the router need to be a 3-port router, that is routing between two
> > class-c subnets as well as the internet. We are having some troubles
> > with the routing statements. Here is a run down on the setup:
> > 
> > OS: Redhat 6.2
> > 
> > Network 1 (internet via another private network):
> > eth0: 172.16.14.4
> > Subnet: 255.255.0.0
> > Gateway to Internet: 172.16.1.1
> > AMD PCI NIC
> > 
> > Network 2 (private)
> > eth1: 10.0.18.151
> > Subnet: 255.255.255.0
> > Intel Dual NIC #1
> > 
> > Network 3 (private)
> > eth2: 10.0.19.151
> > Subnet: 255.255.255.0
> > Intel Dual NIC #2
> > 
> > We have been able to establish routes between all the networks just
> > fine. However, when we try to hit the internet via eth1 or eth2 we get
> > no ping back. We can ping other IPs on the respective subnets, just
> > can't get to the internet. We can however get to the internet on the
> > actual router box. Here is the routing table from route:
> > 
> > Kernel IP routing table
> > Destination     Gateway         Genmask         Flags Metric Ref    Use
> > Iface
> > 172.16.14.4     *               255.255.255.255 UH    0      0        0
> > eth0
> > 10.0.18.151     *               255.255.255.255 UH    0      0        0
> > eth2
> > 10.0.19.151     *               255.255.255.255 UH    0      0        0
> > eth1
> > 172.16.0.0      10.0.18.151     255.255.255.0   UG    0      0        0
> > eth2
> > 172.16.0.0      10.0.19.151     255.255.255.0   UG    0      0        0
> > eth1
> > 10.0.18.0       10.0.19.151     255.255.255.0   UG    0      0        0
> > eth1
> > 10.0.18.0       *               255.255.255.0   U     0      0        0
> > eth2
> > 10.0.19.0       10.0.18.151     255.255.255.0   UG    0      0        0
> > eth2
> > 10.0.19.0       *               255.255.255.0   U     0      0        0
> > eth1
> > default         172.16.1.1      255.255.0.0     UG    0      0        0
> > eth0
> > 172.16.0.0      172.16.14.4     255.255.0.0     UG    0      0        0
> > eth0
> > 172.16.0.0      *               255.255.0.0     U     0      0        0
> > eth0
> > 127.0.0.0       *               255.0.0.0       U     0      0        0
> > lo
> > 
> > 
> > Any help would be greatly appreciated.
> > 
> > --------------------------------------
> > Kristopher Applegate
> > 
> >  
> > _______________________________________________
> > Web Page:  http://lug.boulder.co.us
> > Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> 
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug

-- 
Nate Duehr <nate at natetech.com>

GPG Key fingerprint = DCAF 2B9D CC9B 96FA 7A6D AAF4 2D61 77C5 7ECE C1D2
Public Key available upon request, or at wwwkeys.pgp.net and others.



More information about the LUG mailing list