Tom, thevenin:/etc# cat /proc/sys/net/ipv4/ip_forward 1
I did that explicitly. I probably should have installed shorewall but since all I want to do is forward all traffic between two internal nets I figured it would be easy enough just to dump a few rules into iptables. Wrong! thevenin:/etc/init.d# uname -a Linux thevenin 2.4.18-686 #1 Sun Apr 14 11:32:47 EST 2002 i686 unknown -- Sincerely, David Smead http://www.amplepower.com. On Sat, 18 May 2002, Tom Eastep wrote: > On Sat, 18 May 2002, David Smead wrote: > > > Tom, > > > > Thanks for the reply. Here's route on the 192.168.3.245. eth0 is down, > > otherwise it would have the route you suggest. > > > > knuth:/etc/init.d# route -n > > Kernel IP routing table > > Destination Gateway Genmask Flags Metric Ref Use Iface > > 192.168.3.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 > > 0.0.0.0 192.168.3.254 0.0.0.0 UG 0 0 0 eth1 > > > > From 192.167.3.245 I can ping both interfaces on thevenin - 192.168.254 > > and 192.168.8.24. I figued that some kind of forwarding must be happening > > there. > > No -- no forwarding is required there. > > > At the moment I have thevenin mounted on knuth over nfs, so a lot > > of stuff is working over the .3.0 net. > > > > > > >From the ruleset on your router, it appears that you haven't yet > configured Shorewall -- one of the things that Shorewall does is enable > forwarding via: > > echo 1 > /proc/sys/net/ipv4/ip_forward > > Have you done that via some other means. > > -Tom > _______________________________________________________________ Hundreds of nodes, one monster rendering program. Now that's a super model! Visit http://clustering.foundries.sf.net/ ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
