Ubuntu 18.04 has reached it's end of standard support, hence marking
won't fix.
** Changed in: network-manager (Ubuntu Bionic)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
** Tags added: patch
** Changed in: network-manager (Ubuntu Bionic)
Status: Incomplete => Triaged
--
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/1969901
Title:
I have tested the new version of the debdiff including the fix and the
fix of the fix.
Using it daily on my laptop and also tested it in the test setup described in
the description.
No issues seen so far.
--
You received this bug notification because you are a member of Desktop
Packages, which
Updated patch also including d017022dfc7e531c23caddeac7b3a8b03b1aa5d0
we will test this further.
** Patch added: "updated patch including
d017022dfc7e531c23caddeac7b3a8b03b1aa5d0"
Agreed, commit d017022 seems to be missing.
I will cherry-pick it locally and retest.
I did some more comparing of the file nm-device.c where the changes was
made.
I think d017022 is the only relevant follow up change.
I compared the commit with the original fix with on the 1.10 track with
The test plan looks good - thanks!
On reviewing the patch itself, it looks quite complex. We took a look
upstream to see if there were any further fixes on the commit being
cherry-picked, and found at least one. See
** Changed in: network-manager (Ubuntu Bionic)
Status: Incomplete => In Progress
--
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/1969901
Title:
network-manager fails to
It seems like https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1533631 is the same bug as this one.
--
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/1969901
Title:
** Description changed:
[Impact]
* This affects Ubuntu 18.04 where Network Manager version 1.10.6 is
used.
* Network manager might kill dhclient(6) and fail to start it again
causing the IPv6 address to be lost on a network that uses mixed
IPv4/IPV6.
The network
Ubuntu 20.04 includes a later version of network manager that already
contains the fix.
The suggested fix for 18.04 is a backport/cherry-pick of the fix to the
older version of network manager included in 18.04.
--
You received this bug notification because you are a member of Desktop
Packages,
The status says "Fix Released", was it released for 20.04 and later but
not for 18.04 ?
--
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/1969901
Title:
network-manager fails to
Any comments on the proposed test plan?
It worked fine in during the described steps.
--
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/1969901
Title:
network-manager fails to
Proposal for test plan:
Setup of environment
1. Install two identical computers (A,B) with Ubuntu 18.04 with the same
configuration
2. On computer B installed the patched version of network manager
3. Try to make the network conditions the same on both computers by connecting
the computers two
Thank you for the comments. These seem like good ideas, but need details
before they are actionable.
I think this update is still blocked on having a specific, step-by-step
test plan please.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
>> The exact conditions for reproducing this bug on mixed IPv4/IPv6 networks
>> are not known
>
>Looking at the upstream commit description, isn't it just that a DHCPv6 lease
>expires and the >server NAKs a request for the same IP again? Or is that not
>sufficient to trigger the problem.
>
Yes,
> The exact conditions for reproducing this bug on mixed IPv4/IPv6
networks are not known
Looking at the upstream commit description, isn't it just that a DHCPv6
lease expires and the server NAKs a request for the same IP again? Or is
that not sufficient to trigger the problem.
In any case, I
Thanks, the issue is fixed in newer series and I've sponsored your
bionic SRU now and updated the description to be a bit more specific
about the impact and what to verify
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Low
** Changed in: network-manager (Ubuntu)
Was able to reproduce, my workaround was a systemd timer to clear the
dhcp lease files and restart networkmanager... which is rather violent.
Confirmed client side problem, Win7,Win10,MacOS Montemery and Android 11
have no problems and do not lose their ipv6 on the same network.
--
You received
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.
** Description changed:
- We have experienced this issue on mixed ipv6/ipv4 corporate network on Ubuntu
18.04.
- Unfortunately next LTS release is not yet an option for us.
+ [Impact]
- This is same as https://bugzilla.gnome.org/show_bug.cgi?id=783391
- This was fixed in 1.12.0.
+ * Network
UPDATE, network-manager team applied this to the 1.10-trunk as well and it was
included in:
1.10.8 (first tag)
See:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7fbbe7ebee99785e38d39c37e515a64a28edef0f
Unfortunately Ubuntu 18.04 includes a version that is slightly too
21 matches
Mail list logo
