vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I have a dsl connection being serviced by a Slackware 9 running 2.6.7. Other tnan a complaint at boot, that my mount (2.11b) is older than the kernel, everything works fine. On the 2nd ethernet there is a 8.1(upgraded to current) that can communicate with the 2.6.7 Slack, but can not ping or traceroute out via that GWY. DNS is being resolved, but just timeouts going out. Same result, with/without fwall. Dont have a clue, since both boxes have been pretty much updated the same. Thanks on anything to check.... TonyB -- __ __ _ I N C. http://www.sysdev.org / __|\\// __|| \ __ __ / tonyb@sysdev.org \__ \ \/\__ \||)|/ O_)\/ / \/ System Tools / Utilities |___/ || ___/|_ /\___|\_/ WIntel / Linux Device Drivers |
| |||
| Joaco wrote: > On the 2nd ethernet there is a 8.1(upgraded to current) that > can communicate with the 2.6.7 Slack, but can not ping or > traceroute out via that GWY.**DNS*is*being*resolved,*but > just timeouts going out.**Same*result,*with/without*fwall. What does the output of `route -n` (as root) show? What does a traceroute to an external host (say www.google.com) show? Can the gateway machine see the outside world? On the gateway machine, what does `cat /proc/sys/net/ipv4/ip_forward` show? Does the gateway machine have anything set up to actually forward traffic from the internal LAN (the Slack 8.1 box) to the outside world? Cheers Dave P -- David Precious http://www.preshweb.co.uk/ |
| |||
| On Sun, 25 Jul 2004 22:03:37 +0100 David Precious <pinkmeat@preshweb.co.uk> wrote: DESCRIPTION: CPU1: has dsl modem on eth0, local net on eth1 CPU1: dual boot 2.4.20 or 2.6.7 CPU2: has the local lan on eth0 CPU2: 2.4.20 > What does the output of `route -n` (as root) show? CPU2's route shows the gwy, etc, exactly the same w/CPU1 2.6.7 as w.CPU1 2,4.20, the same applies to route and ifconfig CPU1 shows the same for both eth's 2.4.20 or 2.6.7 (route & ifconfig). CPU1 can connect to google, etc in either kernel (both build locally with pretty much a port of the src's .config > > What does a traceroute to an external host (say > www.google.com) show? CPU2: traceroute, just hangs, ping returns failed cnt. > > Can the gateway machine see the outside world? Its a static IP server, it can be seen from the outside and see the outside ditto, in both kernels. > > On the gateway machine, what does `cat > /proc/sys/net/ipv4/ip_forward` show? dont have 2.6.7 running on CPU1, right now, but the problem MIGHT be here, BECAUSE the firewall failed, since the insmod's did not have the .ko on the module names. However, I did fix that while in 2.6.7, reran the fwall and CPU2 still failed to see the outside (IT DOES SEE CPU1!!!) > > Does the gateway machine have anything set up to actually > forward traffic from the internal LAN (the Slack 8.1 box) to > the outside world? I have ran http:// www.sysdev.org for the last 5 years on it. > > Cheers > > Dave P > > -- > David Precious > http://www.preshweb.co.uk/ > Must be something stupid or would have seen it by now... Thanks TonyB -- __ __ _ I N C. http://www.sysdev.org / __|\\// __|| \ __ __ / tonyb@sysdev.org \__ \ \/\__ \||)|/ O_)\/ / \/ System Tools / Utilities |___/ || ___/|_ /\___|\_/ WIntel / Linux Device Drivers |
| |||
| Went back and started 2.6.7 again, and there is a problem with the /lib/modules/2.6.7 depmod tables on that dir cause I can insmod the iptables, if I go to the ipv4/netfilter dir, but not from / Therefore, some module that the kernel req's when my local net tries to go out might also not be loading. My local net hosts can talk and see the 2.6.7 GWY, they just can ip_forward thru it to the outside. Let me remake, install and try again, if not there is always Slack10's 2.6.7, but that is so much bigger than mine. TonyB -- __ __ _ I N C. http://www.sysdev.org / __|\\// __|| \ __ __ / tonyb@sysdev.org \__ \ \/\__ \||)|/ O_)\/ / \/ System Tools / Utilities |___/ || ___/|_ /\___|\_/ WIntel / Linux Device Drivers |
| |||
| Well its good to know I'm not the only one havin problems getting local net 2.4 boxes goin out to the INET via a 2.6.7 Slackware router. They can talk to the router, get DNS services but no routing. Tried the Slak10 testing kernel and modules with same result also... http://justlinux.com/forum/showthrea...hreadid=130613 -- __ __ _ I N C. http://www.sysdev.org / __|\\// __|| \ __ __ / tonyb@sysdev.org \__ \ \/\__ \||)|/ O_)\/ / \/ System Tools / Utilities |___/ || ___/|_ /\___|\_/ WIntel / Linux Device Drivers |
| ||||
| On Sun, 25 Jul 2004 01:20:25 +0000 Joaco <tonyb@invalid.org> wrote: > On the 2nd ethernet there is a 8.1(upgraded to current) that > can communicate with the 2.6.7 Slack, but can not ping or > traceroute out via that GWY. DNS is being resolved, but > just timeouts going out. Same result, with/without fwall. FYI: NOT COMPILING with the OPTIMIZE_FOR_SIZE enabled in your ..config's "General Setup Section", when using gcc-3.3.4, seems to solve the problem! TonyB -- __ __ _ I N C. http://www.sysdev.org / __|\\// __|| \ __ __ / tonyb@sysdev.org \__ \ \/\__ \||)|/ O_)\/ / \/ System Tools / Utilities |___/ || ___/|_ /\___|\_/ WIntel / Linux Device Drivers |