networking down (MAC, dnet-common, ?)

[fourreux]

I upgraded my wheezy today. Along came dnet-common. After a reboot the network wasn't reachable any more.

So I figured out, it had something to do with that dnet-common and the MAC address being changed ...

What I did so far is:

Code: Select all

apt-get --purge remove dnet-common libdnet


There's no more:

Code: Select all

/etc/default/decnet

And I let the following file be newly generated by removing the old one:

Code: Select all

/etc/udev/rules.d/70-persistent-net.rules

Checking the difference afterwards: There was no difference! Old and new had the same MAC.

There's this bug report from september 2011: bug report
And some discussion on a mailing list: debian-users mailing list

The thing is I don't even have a loopback interface running. After a reboot the ifconfig output is empty. If I try a

Code: Select all

ifconfig eth0 up


I get the interface with the mac address specified in the udev rules, but no ip address and a ping says:

Code: Select all

# ping 192.168.0.1
connect: Network is unreachable


Just figured out that a

Code: Select all

ifconfig lo up

gives me a working loopback interface and I can reach my apache2 server and it's doing fine ...

I don't really know where to go from there. Is it the MAC adress issue? Or some other networking thingy that is broken as well ...?

Thanks for any help

[nadir]

Not really an idea what might be wrong.
One thing:
ifconfig eth0 up
doesn't give an IP, i think. You will have to
dhclient eth0

Also have a look at /etc/network/interfaces
or post it here (a missing lo is what i never have heard of nor run into. Sounds strange).
Or do you use a network-manager of any kind? If yes, which one?.

[fourreux]

Thanks. With dhclient I get a working eth0 interface.

My /etc/network/interfaces is

Code: Select all

# The loopback network interface
auto lo
iface lo inet loopback

# The primary static network interface
auto eth0
iface eth0 inet static
    address 192.168.0.100
    gateway 192.168.0.1
    netmask 255.255.255.0
    broadcast 192.168.0.255


Here's some installed packages:

Code: Select all

# dpkg -l | grep network
ii  firmware-realtek                     0.35                               Binary firmware for Realtek wired and wireless network adapters
ii  glib-networking:i386                 2.32.1-1                           network-related giomodules for GLib
ii  glib-networking-common               2.32.1-1                           network-related giomodules for GLib - data files
ii  glib-networking-services             2.32.1-1                           network-related giomodules for GLib - D-Bus services
rc  ifupdown                             0.7~alpha5+really0.6.16            high level tools to configure network interfaces
ii  iproute                              20120319-1                         networking and traffic control tools
ii  iputils-ping                         3:20101006-1+b1                    Tools to test the reachability of network hosts
ii  libgnuinet-java                      1.1.2-2                            extension library to provide extra network protocol support
ii  libqt4-network:i386                  4:4.8.1-1                          Qt 4 network module
ii  net-tools                            1.60-24.1                          The NET-3 networking toolkit
ii  netbase                              5.0                                Basic TCP/IP networking system
ii  traceroute                           1:2.0.18-1                         Traces the route taken by packets over an IPv4/IPv6 network
rc  wicd-daemon                          1.7.0+ds1-5                        wired and wireless network manager - daemon
rc  wicd-gtk                             1.7.0+ds1-5                        wired and wireless network manager - GTK+ client
ii  xfce4-netload-plugin                 1.1.0-1                            network load monitor plugin for the Xfce4 panel


So no, there are currently no installed noetwork-managers ...
With these settings it was working before ...

I'll try again with static and dhcp setup in /etc/networking/interfaces

edit
it didn't work with the following interfaces:

Code: Select all

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
allow-hotplug eth0
iface eth0 inet dhcp


It's as if this file would be ignored ...

[debil]

I could be wrong but this smells like the known ifupdown/netbase issue. I'm running mainly testing as well and didn't full-upgrade this morning because ifupdown would have been removed in the process (as you seem to be missing the package). If it were me, I'd install the newer version from unstable.

[fourreux]

And you were right! Thanks a lot!

For now I did a:

Code: Select all

# dpkg -i /var/cache/apt/archives/netbase_4.47_all.deb
# apt-get install ifupdown


Reboot and everything's fine again ...

I guess I'll look into aptitude as it seems to informe more carefully about such things. Had I known that it's about ifupdown and netbase I would probably have found that thread myself (I hope that last sentence makes sence grammatically).

Thanks again to both of You! Cheers!

[debil]

Glad you got it sorted out. Cheers!

[CiaW]

And glad I saw this thread before I updated today! Losing internet through an update just isn't supposed to happen (imo).

[cynwulf]

And glad I saw this thread before I updated today! Losing internet through an update just isn't supposed to happen (imo).

It is when you're running testing or unstable.

[huggybear]

And glad I saw this thread before I updated today! Losing internet through an update just isn't supposed to happen (imo).

It is when you're running testing or unstable.

Unstable or experimental -- yes. But for Testing, I'd personally expect such big bugs not to happen, even though I've witnessed them much too often. Be that as it may, the get resolved till the Stable release, which is all I care about.