TCP/IP Routing Problem
Novell Cool Solutions: Trench
Digg This -
Posted: 21 May 2001
We got a question from someone having a weird problem routing TCP/IP using a NetWare server. He said "Workstation A can ping Workstation B, but it cannot ping the Linux Firewall, nor as a result, any other networks. Workstation B has no problem reaching anything it wants to. There is a static default route on the NetWare server set to 10.100.1.1, it's also set to present the default route on the 10.0.x.x network.
It turned out to be a hardware problem (having to tighten the loose nut behind the keyboard :-), but we thought we'd share in case any of you come across it.
The problem was actually twofold:
- My 10.0.x.x and 10.100.x.x addressing scheme was fine, but I forgot to put in a static route from the Linux box back to the 10.0.x.x network. To fix this, I added the command:
"route add -net 10.0.0.0/16 gw 10.100.2.2"
to the /etc/rc.local script.
- My IPCHAINS configuration didn't know about the 10.0.x.x network, to fix this I edited the /etc/rc.firewall script.
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com