On Tue, 2007-07-10 at 10:08 +0000, yelo_3 wrote: > Hello, this is a bug I have now with nm 0.6.5-0ubuntu6 > > when I load the ethernet card module (tg3) and if the cable is unplugged, > network manager thinks that the cable is plugged and the applet icon changes > into the "acquiring address" and when the dhcp timeout triggers, avahi-autoip > gives me an ip, and creates the interface eth0:avah. Now the icon is changed > to the normal one, as if I'm connected via the cable. Connection information > is showing that everything is 0.0.0.0. > > when I plug the cable I get > Jul 10 10:24:13 yelo3-laptop kernel: [ 1460.812000] tg3: eth0: Link is up at > 100 Mbps, full duplex. > Jul 10 10:24:13 yelo3-laptop kernel: [ 1460.812000] tg3: eth0: Flow control > is off for TX and off for RX. > Jul 10 10:24:13 yelo3-laptop kernel: [ 1460.816000] ADDRCONF(NETDEV_CHANGE): > eth0: link becomes ready > Jul 10 10:24:14 yelo3-laptop avahi-daemon[7003]: Registering new address > record for fe80::211:2fff:feb5:41dd on eth0.*. > > the interface eth0:avah will remain up, until I unplug the cable: > Jul 10 10:25:39 yelo3-laptop NetworkManager: <info> SWITCH: > terminating current connection 'eth0' because it's no longer valid. > Jul 10 10:25:39 yelo3-laptop NetworkManager: <info> Deactivating device eth0. > Jul 10 10:25:39 yelo3-laptop NetworkManager: nm_device_is_802_3_ethernet: > assertion `dev != NULL' failed > Jul 10 10:25:39 yelo3-laptop NetworkManager: nm_device_is_802_11_wireless: > assertion `dev != NULL' failed > Jul 10 10:25:39 yelo3-laptop avahi-daemon[7003]: Withdrawing address record > for 169.254.7.228 on eth0. > Jul 10 10:25:39 yelo3-laptop avahi-daemon[7003]: Leaving mDNS multicast group > on interface eth0.IPv4 with address 169.254.7.228. > Jul 10 10:25:39 yelo3-laptop avahi-daemon[7003]: Interface eth0.IPv4 no > longer relevant for mDNS. > Jul 10 10:25:39 yelo3-laptop avahi-daemon[7003]: Withdrawing address record > for fe80::211:2fff:feb5:41dd on eth0. > > If I plug in the cable again I finally get my normal connection up and running > > I don't know if this bug is only of my distribution, which is ubuntu gutsy, > or if it is a kernel module bug and I would like to know if any of you has it > too.
That is likely be fixed by recent commits to stable branch. But when this happens, can you check the value of /sys/class/net/eth0/carrier? Thanks, Dan _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
