Suse 11.1 can't connect to internet

[stringzz]

I am having trouble connecting to the internet.

Details:
OpenSuse 11.1, Cable Modem, connected to Linksys Wireless N Router, hard line from router to ethernet port on my computer.

I checked network settings in YAST2, my ethernet is showing not connected. I have it set to start at boot, and when I look at /var/log/messages after boot, I see an error that says "eth0: no Ipv6 routers present"

[gogalthorp]

You need to set it to NOT use Ipv6

Edit the setup in Yast select advanced IVP6 and disable.

[stringzz]

You need to set it to NOT use Ipv6

Edit the setup in Yast select advanced IVP6 and disable.

I disabled that, rebooted and still the eth0 is not started.

Is there a way to start the device via command line?

[D-cat]

su

ifup eth0

If there's a problem, an error should show up here.

ifconfig eth0

will show you the current state of the net card.

[stringzz]

It looks like the ethernet device is running, I guess I am not connecting to the internet for some reason. You can see in the Yast screenshot the device is not connected.

linux-kc7u:~ # ifup eth0
eth0 device: Davicom Semiconductor, Inc. 21x4x DEC-Tulip compatible 10/100Ethernet (rev 31)
DHCP4 client is already running on eth0
linux-kc7u:~ # ifconfig
eth0 Link encap:Ethernet HWaddr 00:08:A1:15:C5:A2
inet addrxx.xxx.xxx.xxx Bcastxx.xxx.xxx.xxx Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:15 errors:26 dropped:0 overruns:0 frame:0
TX packets:17 errors:7 dropped:0 overruns:0 carrier:7
collisions:0 txqueuelen:1000
RX bytes:3386 (3.3 Kb) TX bytes:3277 (3.2 Kb)
Interrupt:16 Base address:0xec00

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:72 errors:0 dropped:0 overruns:0 frame:0
TX packets:72 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5606 (5.4 Kb) TX bytes:5606 (5.4 Kb)

[D-cat]

Huh. You look to be connected.

Looks to me more like a reliability thing...

RX packets:15 errors:26 dropped:0 overruns:0 frame:0
TX packets:17 errors:7 dropped:0 overruns:0 carrier:7

Try reconnecting or replacing the net cable, make sure it's at least CAT5. You can also try another port on the router switch. If there's any possibility you're using a crossover cable (you shouldn't be), try the downlink port (usually 4).

[gogalthorp]

You may need to turn IPV6 off in the browser also

In FireFox in address bar type

about:config

in the filter line type
IPV

set disable to true

[stringzz]

Huh. You look to be connected.

Looks to me more like a reliability thing...


Try reconnecting or replacing the net cable, make sure it's at least CAT5. You can also try another port on the router switch. If there's any possibility you're using a crossover cable (you shouldn't be), try the downlink port (usually 4).

But when I run YAST Network Settings, it shows my ethernet is not connected. I tried my other ports on the router and a different cable. No luck.

Should I try buying a new network card?

[D-cat]

It is possible that the card is defective, but I usually try to confirm that first. Replacing hardware is a last resort, and if the issue is with your net config, then a new card will not fix the issue. OTOH, if the config is good and the card is defective, replacing it is the only thing that'll fix it.

What happens if you try to ping your router?

ping 192.168.1.1 (or whatever your router's address is).

[Ctrl + C] to stop the ping.

If it pings, then we'll need to check the DNS and route settings (which are supposed to be automatically adjusted by the dhcp client).

if ifconfig eth0 shows you have an inet address (as above) and you fail to ping your router (or shows any dropped packets, it should never happen on a single hop), it may be time to change your net card. I do have a little more to try though, namely if it seems to be up but has no inet address (or not a typical class C).

[stringzz]

What happens if you try to ping your router?

ping 192.168.1.1 (or whatever your router's address is).

[Ctrl + C] to stop the ping.

If it pings, then we'll need to check the DNS and route settings (which are supposed to be automatically adjusted by the dhcp client).

if ifconfig eth0 shows you have an inet address (as above) and you fail to ping your router (or shows any dropped packets, it should never happen on a single hop), it may be time to change your net card. I do have a little more to try though, namely if it seems to be up but has no inet address (or not a typical class C).

I tried to ping my router (Brand new Linksys N Router) at 192.168.1.1, which is the correct ip, and no packets made it through, and ifconfig does show an inet address.

I have bought a new ethernet card ($4), and when I try to compile the driver source code, I am getting the following error:

make -C src/ clean
make[1]: Entering directory `/root/2.4.x_2.6.x/src'
rm -f *.o *.ko *~ core* .dep* .*.d .*.cmd *.mod.c *.a *.s .*.flags
make[1]: Leaving directory `/root/2.4.x_2.6.x/src'
make -C src/ modules
make[1]: Entering directory `/root/2.4.x_2.6.x/src'
make -C /lib/modules/2.6.27.7-9-pae/build SUBDIRS=/root/2.4.x_2.6.x/src modules
make[2]: Entering directory `/usr/src/linux-2.6.27.7-9-obj/i386/pae'
make[2]: *** No rule to make target `modules'.  Stop.
make[2]: Leaving directory `/usr/src/linux-2.6.27.7-9-obj/i386/pae'
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/root/2.4.x_2.6.x/src'
make: *** [modules] Error 2