Before I "add a route" I thought I would show you this, maybe you can see if it is no good and why: # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo Patrick McCabe wrote: > Assuming the green interface on ipcop is 192.168.0.1 > > manually, as root: > /sbin/route add default gw 192.168.0.1 > > On the ipcop box, in /var/ipcop/ethernet/settings, you should have the > line: > DEFAULT_GATEWAY=192.168.0.1 > This will set it up at boot. > > > Patrick > > > Todd Young wrote: > >> I think Rick's problem may be that he needs to add a route statement >> to his network configs. >> >> If I check "netstat -rn", one of my routing entries is as follows: >> Destination Gateway Genmask Flags MSS Window Iface >> 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 eth0 >> >> Obviously, this tells my Mandrake machine that for ALL IP addresses, >> it needs to go to my firewall to get it's information. I'm willing to >> bet that information is missing from his configs. I know how to add a >> route statement to Windows, but I can't seem to remember how to do it >> in Unix/Linux. Anyone out there want to pitch in? >> > > > > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > http://www.mn-linux.org tclug-list at mn-linux.org > https://mailman.real-time.com/mailman/listinfo/tclug-list > > -- Eric (Rick) Meyerhoff _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota http://www.mn-linux.org tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list