Wired Connection Doesn't Work Since Upgrade to 12.1

Hi,

I recently upgraded from 11.4 to 12.1, and took the opportunity to switch over to Xfce. I’ve been generally pleased with the upgrade, except for the difficulty I’ve been having getting my wired connection to work. I can rule out the router and the cable as the source of the issue as I’ve tested them on my backup machine. Luckily, my wireless connection has been working fine, but now that my router needs to have its firmware upgraded, it’s time for me to get my wired connection to work as well. I’m hoping that the issue is a Network Manager configuration issue, and not the ethernet port or interface. I generally use Network Manager, but am perfectly willing to use ifup if that’s the most straightforward way for me to resolve this issue.

Thanks in advance for any and all help. Now for the specifics:

/SBIN/ROUTE:


Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default          192.168.0.1     0.0.0.0            UG    0      0        0 eth0
loopback        *                   255.0.0.0         U     0      0        0 lo
192.168.0.0    *                   255.255.255.0   U     1      0        0 eth0
192.168.0.0    *                   255.255.255.0   U     2      0        0 wlan0

OR THIS


Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default          192.168.0.1     0.0.0.0           UG    0      0        0 wlan0
loopback        *                  255.0.0.0         U     0      0        0 lo
link-local        *                  255.255.0.0      U     0      0        0 eth0
192.168.0.0    *                  255.255.255.0   U     0      0        0 eth0
192.168.0.0    *                  255.255.255.0   U     2      0        0 wlan0

NM-TOOL:
NetworkManager Tool
State: connected (global)

  • Device: eth0 [Auto eth0] ----------------------------------------------------
    Type: Wired
    Driver: e1000e
    State: connected
    Default: yes
    HW Address: 00:1F:E2:12:00:2F

    Capabilities:
    Carrier Detect: yes
    Speed: 1000 Mb/s

    Wired Properties
    Carrier: on

    IPv4 Settings:
    Address: 192.168.0.104
    Prefix: 24 (255.255.255.0)
    Gateway: 192.168.0.1

    DNS: 192.168.0.1

IFCONFIG:

eth0 Link encap:Ethernet HWaddr 00:1F:E2:12:00:2F
inet addr:192.168.0.104 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::21f:e2ff:fe12:2f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:137 errors:0 dropped:0 overruns:0 frame:0
TX packets:146 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:12380 (12.0 Kb) TX bytes:18963 (18.5 Kb)
Interrupt:20 Memory:fe000000-fe020000

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:611 errors:0 dropped:0 overruns:0 frame:0
TX packets:611 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:55804 (54.4 Kb) TX bytes:55804 (54.4 Kb)

wlan0 Link encap:Ethernet HWaddr 00:1F:3C:9E:17:9D
inet addr:192.168.0.101 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::21f:3cff:fe9e:179d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2907 errors:0 dropped:0 overruns:0 frame:0
TX packets:2229 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1808391 (1.7 Mb) TX bytes:431965 (421.8 Kb)

FIREWALL STATUS:
Disabled for both wireless and ethernet interfaces.

PING:
I can ping my router (gateway) using my ethernet interface, but cannot ping google.

WHAT ELSE?:
If I have my ethernet cable plugged in, then my wireless won’t work. My wireless connection only works if I have my ethernet cable unplugged.

I can ping my router (gateway) using my ethernet interface, but cannot ping google.

When you say that you cannot ping google, do you mean you cannot ping an IP address like this

ping 74.125.224.7

or do you mean that

ping google.com

fails for you.

I suspect that you have a DNS issue.

What gets returned (if anything) from the following command?

grep -i name /etc/resolv.conf

Hi Deano,

Thanks for the help. This is what I get:

linux-X200:/home/malcolm # ping -c 5 173.194.35.178
PING 173.194.35.178 (173.194.35.178) 56(84) bytes of data.

— 173.194.35.178 ping statistics —
5 packets transmitted, 0 received, 100% packet loss, time 3999ms

AND

linux-X200:/home/malcolm # grep -i name /etc/resolv.conf
nameserver 192.168.0.1

On 2012-08-19 20:56, ahorseahorse wrote:

> Thanks in advance for any and all help. Now for the specifics:
>
> /SBIN/ROUTE:
>



> Code:
> --------------------
>
>   Kernel IP routing table
>   Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
>   default          192.168.0.1     0.0.0.0            UG    0      0        0 eth0
>   loopback        *                   255.0.0.0         U     0      0        0 lo
>   192.168.0.0    *                   255.255.255.0   U     1      0        0 eth0
>   192.168.0.0    *                   255.255.255.0   U     2      0        0 wlan0
>
> --------------------
>
>
>
> OR THIS
>
>
> Code:
> --------------------
>
>   Kernel IP routing table
>   Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
>   default          192.168.0.1     0.0.0.0           UG    0      0        0 wlan0
>   loopback        *                  255.0.0.0         U     0      0        0 lo
>   link-local        *                  255.255.0.0      U     0      0        0 eth0
>   192.168.0.0    *                  255.255.255.0   U     0      0        0 eth0
>   192.168.0.0    *                  255.255.255.0   U     2      0        0 wlan0
>
> --------------------


It is not clear when you have the first table and when the second. I guess that one is with the
cable and another with the wlan - and then the problem is that the routing tables are not pure,
they specify the other interface for somethings.

> PING:
> I can ping my router (gateway) using my ethernet interface, but cannot
> ping google.

By name or by IP? If it is by name, you may have a DNS problem. If it is by IP, then a routing
problem.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

Based on the fact that you cannot ping the outside world by IP address, I think I’d be inclined to restart the router. (I know you said it was providing internet connectivity to your backup machine, but give it a go anyway).

Hi Deano and Carlos,

I can ping both “google.com” and “173.194.35.178” successfully with my wireless connection.

However, I can ping neither of them successfully with my wired connection.

Here is what ping returned on my wired connection before I restarted both my modem and router:

linux-X200:/home/malcolm # ping -c 5 google.com
PING google.com (173.194.43.6) 56(84) bytes of data.

google.com ping statistics —
5 packets transmitted, 0 received, 100% packet loss, time 3999ms

linux-X200:/home/malcolm # ping -c 5 173.194.35.178
PING 173.194.35.178 (173.194.35.178) 56(84) bytes of data.
64 bytes from 173.194.35.178: icmp_seq=4 ttl=49 time=111 ms

— 173.194.35.178 ping statistics —
5 packets transmitted, 1 received, 80% packet loss, time 4001ms
rtt min/avg/max/mdev = 111.714/111.714/111.714/0.000 ms

note one packet made it through when I pinged the google’s ip address directly.

AND, here’s what ping returned after I restarted my modem and router:

linux-X200:/home/malcolm # ping -c 5 173.194.35.178
PING 173.194.35.178 (173.194.35.178) 56(84) bytes of data.

— 173.194.35.178 ping statistics —
5 packets transmitted, 0 received, 100% packet loss, time 3999ms

linux-X200:/home/malcolm # ping -c 5 google.com
PING google.com (173.194.43.1) 56(84) bytes of data.

google.com ping statistics —
5 packets transmitted, 0 received, 100% packet loss, time 4000ms

I don’t know how to generate a pure routing table, Carlos. Would you mind instructing me how to do that?

Best,
Malcolm

Here is what ping returned on my wired connection before I restarted both my modem and router:


linux-X200:/home/malcolm # ping -c 5 173.194.35.178
PING 173.194.35.178 (173.194.35.178) 56(84) bytes of data.
64 bytes from 173.194.35.178: icmp_seq=4 ttl=49 time=111 ms

The packet loss is a concern. Do you have an a negotiation issue perhaps?

Do you have any unusual boot options in your grub config? When you boot up in safe mode, does your wired connection work okay (ping tests)?

I wonder if this bug is related to your issue?

https://bugzilla.novell.com/show_bug.cgi?id=769211

On 2012-08-20 05:46, ahorseahorse wrote:
> I don’t know how to generate a pure routing table, Carlos. Would you
> mind instructing me how to do that?

I don’t know how to explain… network manager should do a good routing table, but I’m not
familiar with that. Maybe you can not use both simultaneously.

With ifup in yast you have to specify which route uses which interface. Perhaps for the gateway
you have to specify “any”.

Having two devices is tricky. Some people remove one completely and then add the other. Other
use “profiles” to keep two configuration sets separate (command scpm).

When I change interface on my laptop I have to fight it. :-}


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

Deano and Carlos,

I’ve chimed in on the Novell bug, and will report back once I hear from those folks.

resolved. i have a second router that i decided to give a try, even though i thought i had ruled out the possibility of this issue being router related. sure enough, second router worked like a charm.

would be interested to hear any thoughts on what could be up with the faulty router, especially given that it worked with my wife’s computer’s cable connection and also with the cable connection of my backup computer–it just didn’t work with the cable connection of my primary computer.

why would a router be so picky about the machine’s it chooses to work with, even among machines running the same os (opensuse 12.1)?

another choice tidbit: my backup router is the same model as my primary router, just a different hardware revision of that model running a different firmware version. and wouldn’t you know that the router that worked–the backup–was the older hardware revision and was running an older firmware version.

here’s to holding onto backup hardware.

thanks deano and carlos.

ahorseahorse wrote:
> another choice tidbit: my backup router is the same model as my primary
> router, just a different hardware revision of that model running a
> different firmware version. and wouldn’t you know that the router that
> worked–the backup–was the older hardware revision and was running an
> older firmware version.

Could be an IPv6 issue.

The older one perhaps doesn’t work with IPv6 at all, the newer one works
well enough to expose some bugs in your ISP’s setup, your own setup, or
a bug in the router itself?