can ping router but can't connect to it, nor internet

tuneout · 06-05-2006, 06:06 PM

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?

drkstr · 06-05-2006, 06:14 PM

Quote:

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.

What do you mean by this? Does your router display computers that are connected to it through dhcp or something? How did you get the ipaddress to your NIC? Did you set it as static or are you using your routers dhcp? This may be a simple matter of adding the router IP to your '/etc/rc.d/rc.inet1.conf' file. Where it says GATEWAY="" you need to fill in the appropriate address.

regards,
...drkstr

kodon · 06-05-2006, 06:24 PM

sound like you might not have a lease

tuneout · 06-05-2006, 06:45 PM

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.

drkstr · 06-05-2006, 06:57 PM

Quote:

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.

yea, that would have only helped if you were not getting your IP from dhcp.

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?

tuneout · 06-05-2006, 07:54 PM

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?

gbonvehi · 06-05-2006, 08:31 PM

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?

drkstr · 06-05-2006, 08:35 PM

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

tuneout · 06-05-2006, 09:19 PM

Code:

root@Triton:/etc# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:08:A1:20:CB:15
          inet6 addr: fe80::208:a1ff:fe20:cb15/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:610 errors:313 dropped:0 overruns:0 frame:0
          TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:36980 (36.1 Kb)  TX bytes:2833 (2.7 Kb)
          Interrupt:3 Base address:0x8c00

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:36 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2808 (2.7 Kb)  TX bytes:2808 (2.7 Kb)

Code:

root@Triton:/etc# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo

Code:

root@Triton:/etc# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Code:

root@Triton:/etc# cat /etc/rc.d/rc.inet1.conf
# /etc/rc.d/rc.inet1.conf
#
# This file contains the configuration settings for network interfaces.
# If USE_DHCP[interface] is set to "yes", this overrides any other settings.
# If you don't have an interface, leave the settings null ("").

# You can configure network interfaces other than eth0,eth1... by setting
# IFNAME[interface] to the interface's name. If IFNAME[interface] is unset
# or empty, it is assumed you're configuring eth<interface>.

# Several other parameters are available, the end of this file contains a
# comprehensive set of examples.

# =============================================================================

# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]="yes"
DHCP_HOSTNAME[0]=""

Code:

from dmesg:
Linux Tulip driver version 1.1.13 (May 11, 2002)
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 3
PCI: setting IRQ 3 as level-triggered
ACPI: PCI Interrupt 0000:02:07.0[A] -> Link [LNKA] -> GSI 3 (level, low) -> IRQ 3
tulip0:  EEPROM default media type Autosense.
tulip0:  Index #0 - Media MII (#11) described by a 21140 MII PHY (1) block.
tulip0:  Index #1 - Media 10baseT (#0) described by a 21140 non-MII (0) block.
tulip0:  Index #2 - Media 100baseTx (#3) described by a 21140 non-MII (0) block.
tulip0:  Index #3 - Media 10baseT-FDX (#4) described by a 21140 non-MII (0) block.
tulip0:  Index #4 - Media 100baseTx-FDX (#5) described by a 21140 non-MII (0) block.
tulip0:  MII transceiver #1 config 3100 status 7809 advertising 01e1.
eth0: Davicom DM9102/DM9102A rev 49 at f0c58c00, 00:08:A1:20:CB:15, IRQ 3.
dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
0000:02:07.0: tulip_stop_rxtx() failed
eth0: Setting full-duplex based on MII#1 link partner capability of 41e1.
eth0: no IPv6 routers present
0000:02:07.0: tulip_stop_rxtx() failed
0000:02:07.0: tulip_stop_rxtx() failed

and for the record, i no longer am getting an IP address at all, and dhclient says it can't find eth0, so now i'm really stuck, and extremely desperate

drkstr · 06-05-2006, 10:39 PM

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

cwwilson721 · 06-05-2006, 11:19 PM

Looks like there is no need to recompile for your ethernet driver. You just don't get a dhcp address.
Try

Code:

dhcpcd eth0

dhclient isn't used anymore.

drkstr · 06-05-2006, 11:43 PM

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

Old_Fogie · 06-06-2006, 11:16 PM

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:

/sbin/route add default gw MyGateway.Ip.Address.Here

then in console I can finally ping my gateway.

edited for clarity.

drkstr · 06-07-2006, 12:14 AM

Quote:

for some reason 2.4 kernel weirds out on me on one of my pc's using dhcp.

I think you can also set your default gateway in your '/etc/rc.d/rc.inet1.conf'. However I just did it like you and put it in my 'rc.local'. At the time I didn't know about the rc.inet1.conf and just never got around to changing it. I think it might be helpful though if you have have to 'sh /etc/rc.d/rc.inet1 restart' then your routing table doesn't get reset. Maybe some day I'll get around to adding it

regards,
...drkstr