can ping router but can't connect to it, nor internet
hey, finally installed 10.2 on my box after a tour with ubuntu for a while, and it's good to be back. however, i can't get on the internet. eth0 is up, and says its ip is 192.168.0.3, but when i go into the router's config page (from this computer, not the slack box), it doesn't see my slack box at all. from the slack box, i can ping the router, but no outside sites, nor this computer. i've run netconfig many times, unplugged/replugged the ethernet cable, etc. i had the same problem with slax, but never with ubuntu or its livecd. i did a lsmod and it is loading the tulip module for my card, so i have absolutely no idea what's wrong. any suggestions?
|
Quote:
regards, ...drkstr |
sound like you might not have a lease
|
the router is setup to provide IP addresses via DHCP, and this computer is working fine in that regard, and i tried setting the GATEWAY setting to 192.168.0.1 in my rc.inet1.conf file, to no avail.
|
Quote:
Since you are getting the correct IP from dhcp, it leads me to belive that the problem is with the router configuration. You might need to pass some extra options other then the default set up to get slackware to route traffic through your router. Try going though the configuration/documentation for your router and see why your slack-box does not show up in it, even though it gets an IP address. regards, ...drkstr **edit** what kind of router do you have? |
it's a netgear router, and i've had it work with slackware in the past (9.1 and 10.0) but for some reason it won't work with 10.2 now. i tried setting slack/router up with a static IP, that didn't work either. i tried running dhclient on eth0, still no luck. i'm having another problem with slack right now, maybe it's part of this problem. when i booted up, i got a kernel panic at the VFS thing, i don't remember exactly what it said, something about block (3,1), so i used the slack install disc 1 to boot up with the argument root=/dev/hda1 noinitrd ro
could this have anything to do with it? |
That VFS error has nothing to do with your network, it's probably because lilo wasn't configured properly.
Regarding the network problem, it may help if you post route -n and ifconfig eth0 output. You may not be able to ping your other machine because it may have a firewall activated which will ignore ping packets. If you can ping your router, that's a good thing. Probably some routing or dns stuff is missing. Did you try to ping a outside ip address? |
Probably not, but kernel panics are never good. Use 'dmesg' to check it out.
Try posting the following things, maybe I can get some useful info out of it. 'ifconfig' 'route -n' 'iptables -L' 'cat /etc/rc.d/rc.inet1.conf' and any parts of 'dmesg' you think could indicate a problem. regards, ...drkstr **edit** gbonvehi beat me to it |
Code:
root@Triton:/etc# ifconfig Code:
root@Triton:/etc# route -n Code:
root@Triton:/etc# iptables -L Code:
root@Triton:/etc# cat /etc/rc.d/rc.inet1.conf Code:
from dmesg: |
Ok, I think I might know what the problem is now. Have you ever compiled your kernel before? Your going to need to do a kernel config, go to Device Drivers-->Network Device-->Ethernet (10 or 100 Mbit)-->Tulip Family Support-->
Make sure you have Tulip Family Network support checked off, then go down to Davicom DM910x/DM980x support and enable it as a module. Compile and install your new kernel configuration, then restart and run 'netconfig' when you get back to your console. If still does not work, run 'lsmod' to see if the module you just compiled (dmfe) got loaded. If not post back. regards, ...drkstr |
Looks like there is no need to recompile for your ethernet driver. You just don't get a dhcp address.
Try Code:
dhcpcd eth0 |
Hopefully it will be as simple as that, but from what it sounded like in his first post, dhcpd was originally set up correctly with 'netconfig' but was acting buggy. I think he might have broke it further by running dhclient (I wouldn't know since I'm not sure what it is) The dmesg also indicates that there is a driver problem, probably using the standard tulip.o module instead of the tulip module specific to his card (dmfe.o). I don't belive this is enabled by default in Slackware kernel so if he has not done this already, will probably end up having to add in the module. Once he has the proper hardware support, running 'dhcpd eth0' or 'netconfig' should set up dhcp properly.
regards, ...drkstr |
for some reason 2.4 kernel weirds out on me using dhcp.
i have to add this in my /etc/rc.d/rc.local for boot up Quote:
edited for clarity. |
Quote:
regards, ...drkstr |
All times are GMT -5. The time now is 01:38 AM. |