** Changed in: network-manager
Status: Unknown => Confirmed
** Changed in: network-manager
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs
** Description changed:
- After fixing IPv6 address assignment (#1469346), IPv6 works fine until
- sleep. On wake up ubuntu fails to renew its IPv6 lease:
+ Network Manager summarily kills the IPv6 dhclient process when the
+ DHCPv6 lease contained in the dhclient6-${UUID}.lease file is out-of
+ d
** Bug watch added: GNOME Bug Tracker #748268
https://bugzilla.gnome.org/show_bug.cgi?id=748268
** Also affects: network-manager via
https://bugzilla.gnome.org/show_bug.cgi?id=748268
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a membe
** Changed in: isc-dhcp (Ubuntu)
Importance: High => Low
** Changed in: isc-dhcp (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/153
The debug log contains:
Mar 31 01:34:59 hephaestion NetworkManager[9095]: [1459384499.752259]
[dhcp-manager/nm-dhcp-client.c:222] reason_to_state(): (wlp3s0): unmapped DHCP
state 'DEPREF6'
Mar 31 01:34:59 hephaestion NetworkManager[9095]: [1459384499.758516]
[dhcp-manager/nm-dhcp-client.c:757
Attaching a Network Manager TRACE log_level from syslog generated using:
/etc/NetworkManager/conf.d/logging.conf:
---
[logging]
level=TRACE
---
I've removed any extraneous messages from processes other than NM and
dhclient. I've also removed IPv4 related messages to make it easier to
follow.
**
Here's some notes from my digging into the code paths being followed.
Using the messages logged by NM to syslog I've been able to reconstruct
the call heirarchy. In summary, when the state transitions from "expire"
to "done":
nm_dhcp_client_set_state () fires a NM_DHCP_STATE_EXPIRE signal
dhcp6_
Further debugging indicates that when the IPv6 lease file contains an
expired lease as its last entry dhclient 'depreferences' it (gives it
up) but doesn't go on to attempt to gain a replacement lease because NM
cancels (kills) the dhclient process as a result of the 'expires'
message.
NM starts "
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
** Also affects: isc-dhcp (Ubuntu)
Importance: Undecided
Status: New
** Changed in: isc-dhcp (Ubuntu)
Importance: Undecided => High
** Changed in: isc-dhcp (Ubuntu)
Status: New => Triaged
--
You receiv
After deleting the dhcp6${UUID}-${IF}.lease file and reconnecting the
interface the "starts" timestamp is now up to date. Not sure if this is
relevant to the internals of dhclient though.
$ cat dhclient6-0775a2a6-a4a1-40bf-bd85-9c3068582dbc-wlp3s0.lease
default-duid "\000\001\000\001\036z\001X\00
Looking at the files related to dhclient managed by Network Manager
under /var/lib/NetworkManager/ I noticed that although the new lease
file seems to contain the correct (in the future) timestamps the
"timestamps" file entry for that same lease UUID is still set to the
time the original lease expi
Yes, seeing this too on 15.10 since around the first week of March, as
best I can tell, but irrespective of Suspend.
It looks like dhclient thinks/is told the new lease is 'depreferred' and
therefore quits, and the dhclient process is terminated, but the address
remains on the interface until the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchp
13 matches
Mail list logo
