On Sun, 11 Jan 2015 10:47:40 -0200 Marco Calistri wrote:
Il 11/01/2015 08:03, Carl Hartung ha scritto:
On Sun, 11 Jan 2015 10:54:24 +0100 jdd jdd wrote:
the simpler is to test a 13.2 live cd
That's a great suggestion, jdd. Thank you! And if it boots and the network 'just works' I can compare the configurations for clues. :-)
Carl
I have had not any networking troubles upgrading from 13.1 to 13.2.
I think a thing which could have changed and not upgraded accordingly into your box is the interface name.
My former *eth0* changed "inexplicably" into *enp5s0* for example.
Then all the suggested checks by other list-members have to be associated to the correct updated interface name:
marco@linux-turion64:~> ip route show
default via 192.168.1.1 dev enp5s0 proto static metric 1024 192.168.1.0/24 dev enp5s0 proto kernel scope link src 192.168.1.3
ifconfig -a
enp5s0 Link encap:Ethernet HWaddr E8:9A:8F:32:F8:54 inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::ea9a:8fff:fe32:f854/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:9542 errors:0 dropped:0 overruns:0 frame:0 TX packets:7526 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:11840573 (11.2 Mb) TX bytes:703824 (687.3 Kb)
Cheers,
Thanks Marco! I'd forgotten about the interface names being changed. It's a clean, 'from scratch' 13.2 installation, so it must be using them. I'll take that into account when I resume my debugging next weekend. (I've restored my 12.3 system in the interim.) regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org