On Fri, May 15, 2009 at 6:41 PM, Michael Biebl <bi...@debian.org> wrote: > severity 527857 important > thanks > > Patrick Wiseman wrote: >> Package: network-manager >> Version: 0.7.1-1 >> Severity: normal >> >> The update had seemed to correct the problem, but it recurred this >> evening, this time when connected wirelessly. The syslog, before the >> freeze, looks like this: >> > >> May 12 18:04:19 sage dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 >> port 67 interval 4 >> May 12 18:04:23 sage dhclient: No DHCPOFFERS received. >> May 12 18:04:23 sage dhclient: No working leases in persistent database >> - sleeping. >> May 12 18:04:33 sage wpa_supplicant[3860]: CTRL-EVENT-SCAN-RESULTS >> >> eth0 is my WIRED connection, and it was not connected, and so there's no >> reason to be seeking a DHCP address. So, it seems that when the wired >> connection was on, wlan0 was trying to connect (the earlier bug); and >> when the wireless connection is on, eth0 is trying to connect. Neither >> should be happening. > > > NM will only try to establish a connection, if there is a link (eth) or a > wireless connection in range. > If your eth0 is reporting a link even if it's not connected, it's again a > driver > issue. Please check what "cat /sys/class/net/eth0/carrier" says in such a > case.
It returns '0'. If I plug in the wire, as I just did, NM connects to the wired network, and it returns '1'. When I disconnected the wire, I did not lose my connection - the wireless connection was still up. Patrick -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
