have you got ip forwarding turned on? I believe you need the following command to turn it on... echo 1 > /proc/sys/net/ipv4/ip_forward Steve On Sat, 2004-13-03 at 10:50 -0600, Jonathan Horne wrote: > im trying to get a better handle on routing, and here is what my > project consists of so far: > > > > pc1 > > eth0 192.168.0.1 > > eth1 172.16.0.1 > > > > router1 > > eth0 172.16.0.2 > > eth1 172.16.1.2 > > > > pc2 > > eth1 172.16.1.1 > > eth0 192.168.1.1 > > > > (pc2 I listed the eth1 and 0 backwards purely for asthetics of > presenting how they are physically connected on the network) needless > to day, router1 can ping pc1 and pc2, and vice versa. What I need to > accomplish, is for pc2 to be able to ping 172.16.0.1, and vice versa, > unrestricted thru router1. I donât think I want any natting, I think > I just want anything arriving at r1-eth0 bound for 172.16.0.0 passed > to pc1-eth0 as its default gateway, and of course, vice versa. > > > > Here is the routing table on router1: > > > > [root@router1 root]# netstat -rn > > Kernel IP routing table > > Destination Gateway Genmask Flags MSS Window > irtt Iface > > 172.16.0.0 0.0.0.0 255.255.255.0 U 0 0 > 0 eth0 > > 172.16.1.0 0.0.0.0 255.255.255.0 U 0 0 > 0 eth1 > > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 > 0 eth1 > > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 > 0 lo > > > > Pc1 and pc2 are already set up as they need to be, as they are > smoothwalls, and as soon as pc2 and 1 can ping their eth1âs from each > other, the eth0s will also be working. So router1 is really what im > trying to understand the innerworking of at this time. > > > > Thanks yall! > > jonathan > > > > > -- > Shrike-list mailing list > Shrike-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/shrike-list -- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
