routing & ipchains
Greetings All,
After upgrading from kernel 2.0.38 w/ slackware-3.4 to
kernel 2.2.16 w/ slackware-7.1 I have developed the following routing problems.
Hardware -
eth0 - 10meg on net 192.168.0.0 i/f 192.168.0.1 subnet 255.255.255.128 eth1 - 100meg on net 192.168.0.128 i/f 192.168.0.130 subnet
255.255.255.128
Quoted 1 line
From either network I can use ipchains and surf/telnet/ftp/... on
each network to the ppp0 dialup connection. I cannot ping or anything from eth0 to eth1 or back.
---------Route with ppp0 up----------------
Destination Gateway Genmask Flags Metric Ref
Use Iface
205.243.155.100 0.0.0.0 255.255.255.255 UH 0 0 0
ppp0
192.168.0.0 0.0.0.0 255.255.255.128 U 0 0 0
eth1
192.168.0.128 0.0.0.0 255.255.255.128 U 0 0 0
eth0
192.168.0.0 192.168.0.1 255.255.255.0 UG 0 0 0
eth1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 205.243.155.100 0.0.0.0 UG 0 0 0 ppp0 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth1 0.0.0.0 192.168.0.130 0.0.0.0 UG 0 0 0 eth0
-------------------End of Route Table------------------
TIA - if other files are needed, I can forward.
Best - Andy
Andrew B. Cramer - <[email protected]> Cramer Technical Services - <www.cramer-ts.com> Linux Resource Exchange - <www.linuxrx.com>
In message <3AE6208C.8379.146C84FE@localhost> you write:
Quoted 6 lines
Greetings All,
After upgrading from kernel 2.0.38 w/ slackware-3.4 to
kernel 2.2.16 w/ slackware-7.1 I have developed the following routing problems.Hardware -
Quoted 8 lines
eth0 - 10meg on net 192.168.0.0 i/f 192.168.0.1 subnet 255.255.255.128 eth1 - 100meg on net 192.168.0.128 i/f 192.168.0.130 subnet255.255.255.128
Quoted 1 line
From either network I can use ipchains and surf/telnet/ftp/... on
each network to the ppp0 dialup connection. I cannot ping or anything from eth0 to eth1 or back.
Um, I don't see what this has to do with ipchains, but my guess is:
echo 1 > /proc/sys/net/ipv4/ip_forward
Rusty.
--
Premature optmztion is rt of all evl. --DK
Quoted 1 line · Andrew B. Cramer
Greetings All,
Hey Andy - haven't heard from you since work on a replacement linuxHQ (ahh
- those were the days, lot's of free time :) )
Quoted 3 lines
After upgrading from kernel 2.0.38 w/ slackware-3.4 to
kernel 2.2.16 w/ slackware-7.1 I have developed the following routing problems.
When upgrading slackware (not a complete reinstall) it doesn't replace you rc scripts in /etc/rc.d. 2.2.x has a /proc entry to enable forwarding. You need to echo 1 > /proc/sys/net/ipv4/ip_forward to enable forwarding. Newer slackware does this in /etc/rc.d/rc.inet2.
I'm not sure this is your problem. If you installed slackware new without upgrading this probably isn't the answer.
James Rich
[email protected]