oh... and of course: echo 1 > /proc/sys/net/ipv4/ip_forward On 12/7/05, Edmundo Carmona <eantoranz@xxxxxxxxx> wrote: > I wouldn't make it more difficult with separate routing tables. Just > set the firewall to allow traffic between the interfaces you want, > drop the rest and that's it. I mean: > > iptables -A FORWARD -i eth0 -o eth2 -j ACCEPT > iptables -A FORWARD -i eth2 -o eth0 -j ACCEPT > iptables -A FORWARD -i eth1 -o eth3 -j ACCEPT > iptables -A FORWARD -i eth3 -o eth1 -j ACCEPT > > # default policy > iptables -P FORWARD DROP > > That should make it.... only of this router is their default gw or at > least the router to the other network the hosts want to reach. > > On 12/7/05, Paul Lewis <paul.lewis@xxxxxxxxxxxxxxxxxxxxx> wrote: > > Hi, > > > > The output from route -n is shown below: > > > > 192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 > > 192.168.20.0 0.0.0.0 255.255.255.0 U 0 0 0 eth3 > > 192.168.14.0 0.0.0.0 255.255.254.0 U 0 0 0 eth4 > > 192.168.4.0 0.0.0.0 255.255.252.0 U 0 0 0 eth2 > > 192.168.0.0 0.0.0.0 255.255.252.0 U 0 0 0 eth1 > > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth4 > > 0.0.0.0 192.168.100.254 0.0.0.0 UG 0 0 0 eth0 > > > > And here is the output from ifconfig (edited down to save space): > > > > eth0 Link encap:Ethernet HWaddr 00:14:22:09:FB:1A > > inet addr:192.168.100.253 Bcast:192.168.100.255 > > Mask:255.255.255.0 > > inet6 addr: fe80::214:22ff:fe09:fb1a/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > > > eth1 Link encap:Ethernet HWaddr 00:04:23:BB:89:9C > > inet addr:192.168.3.253 Bcast:192.168.3.255 Mask:255.255.252.0 > > inet6 addr: fe80::204:23ff:febb:899c/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > > > eth2 Link encap:Ethernet HWaddr 00:04:23:BB:89:9D > > inet addr:192.168.7.253 Bcast:192.168.7.255 Mask:255.255.252.0 > > inet6 addr: fe80::204:23ff:febb:899d/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > > > eth3 Link encap:Ethernet HWaddr 00:14:22:09:FB:1B > > inet addr:192.168.20.253 Bcast:192.168.20.255 Mask:255.255.255.0 > > inet6 addr: fe80::214:22ff:fe09:fb1b/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > inet6 addr: ::1/128 Scope:Host > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > > > Cheers, > > > > Paul > > > > --- > > Paul Lewis (paul.lewis@xxxxxxxxxxxxxxxxx) > > Part II Student > > Materials Science > > University of Oxford > > > > > > > > -----Original Message----- > > From: Edmundo Carmona [mailto:eantoranz@xxxxxxxxx] > > Sent: 07 December 2005 16:00 > > To: Paul Lewis > > Subject: Re: Network Routing > > > > to start with: what is the output of route -n or ip route show default > > > > On 12/7/05, Paul Lewis <paul.lewis@xxxxxxxxxxxxxxxxxxxxx> wrote: > > > Hi, > > > > > > I have a linux router with 4 ethernet cards; eth0 through eth3. Basically, > > > all I want to do is route all traffic from eth2 to eth0, and all traffic > > > from eth1 to eth3. > > > > > > I've looked through the LARTC how-to, specifically at chapter 4, about > > > multiple providers. However, I am still a bit confused, and not sure how > > to > > > set up my routing tables, as my scenario differs from the one in the > > > example. > > > > > > Any help would be appreciated. > > > > > > Many thanks, > > > > > > Paul > > > > > > --- > > > Paul Lewis (paul.lewis@xxxxxxxxxxxxxxxxx) > > > Part II Student > > > Materials Science > > > University of Oxford > > > > > > > > > > > > > > > _______________________________________________ > > > LARTC mailing list > > > LARTC@xxxxxxxxxxxxxxx > > > http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc > > > > > > > > > > _______________________________________________ LARTC mailing list LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
