NetworkManager wrongly releases DHCP IP
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dhcp (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
dhcp3 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
dnsmasq (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
network-manager (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
whereami (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: network-manager
After resuming my laptop from Suspend-to-disk, NetworkManager failed to give me an IP. Usually it gets an IP from DHCP server without problems; but this one time it failed. First dhclient correctly got an IP:
Apr 10 19:32:43 veridian dhclient: bound to 192.168.0.4 -- renewal in 17299 seconds.
A short time later it releases the IP again:
Apr 10 19:34:14 veridian NetworkManager: <information>
Apr 10 19:34:14 veridian dhclient: There is already a pid file /var/run/
Apr 10 19:34:14 veridian dhclient: killed old client process, removed PID file
Apr 10 19:34:14 veridian dhclient: DHCPRELEASE on eth0 to 192.168.0.1 port 67
ifconfig showed this:
eth0 Protokoll:Ethernet Hardware Adresse 00:40:F4:A7:A2:06
inet6 Adresse: fe80::240:
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:42 errors:0 dropped:0 overruns:0 frame:0
TX packets:249 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:4652 (4.5 KiB) TX bytes:18375 (17.9 KiB)
eth0:avah Protokoll:Ethernet Hardware Adresse 00:40:F4:A7:A2:06
inet Adresse:
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
lo Protokoll:Lokale Schleife
inet Adresse:127.0.0.1 Maske:255.0.0.0
inet6 Adresse: ::1/128 Gültigkeitsbere
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4215 errors:0 dropped:0 overruns:0 frame:0
TX packets:4215 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:224601 (219.3 KiB) TX bytes:224601 (219.3 KiB)
After left-clicking on NM icon and selecting Cable Network, it got a correct IP.
Changed in network-manager (Ubuntu): | |
status: | Confirmed → Incomplete |
Syslog output is attached.