This bug was fixed in the package network-manager - 1.10.6-2ubuntu1
---------------
network-manager (1.10.6-2ubuntu1) bionic; urgency=medium
* Merge with Debian (LP: #1758331). Remaining changes:
- Use systemd-resolved instead of dnsmasq
- debian/control:
+ Depend on isc-dhcp-client instead of recommends
+ Recommend network-manager-pptp
+ Suggest avahi-autoipd for IPv4LL support
- debian/rules, debian/network-manager.postinst:
+ Don't restart NetworkManager on upgrade but recommend restarting
the computer
- debian/rules, debian/network-manager.postinst:
+ Don't install sysvinit scripts or migrate from sysvinit
- debian/network-manager.postinst:
+ Don't add the netdev group.
+ drop in an empty override file for NetworkManager to manage all
devices for upgrade from any version, as long as there is no
netplan configuration yet. (LP: #1676547)
- debian/network-manager.maintscript
+ Remove /etc/dbus-1/system.d/nm-ofono.conf
- debian/default-wifi-powersave-on.conf, debian/rules:
+ Install a config file to enable WiFi powersave
- Enable build tests
- Add autopkgtests
- debian/source_network-manager.py, debian/network-manager.install,
debian/network-manager.links: Add apport hook
- Add network-manager-config-connectivity-ubuntu package
- NetworkManager.conf: disable MAC randomization feature. There is no
easy way for desktop users to disable this feature yet. And there are
reports that it doesn't work well with some systems. (LP: #1681513)
- Update Vcs links to point to Ubuntu branch
- Add patches. See patch descriptions for more details:
+ Provide-access-to-some-of-NM-s-interfaces-to-whoopsie.patch
+ Update-dnsmasq-parameters.patch
+ Disable-general-with-expect.patch
+ libnm-Check-self-still-NMManager-or-not.patch
+ dns-manager-don-t-merge-split-DNS-search-domains.patch
+ Read-system-connections-from-run.patch
+ e91f1a7d2a6b8400b6b331d5b72287dcb5164a39.patch
+ dns-manager-don-t-merge-split-DNS-search-domains.patch (but disabled)
- debian/tests/urfkill-integration - don't stop/start network manager
* Dropped patches applied in new release:
- settings-preserve-agent-owned-secrets-on-connection-updat.patch
network-manager (1.10.6-2) unstable; urgency=medium
* Update Vcs-* to point to https://salsa.debian.org
network-manager (1.10.6-1) unstable; urgency=medium
* New upstream version 1.10.6
* Rebase patches
-- Jeremy Bicha <jbi...@ubuntu.com> Mon, 26 Mar 2018 09:21:12 -0400
** Changed in: network-manager (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1758331
Title:
IPv6 Route to OpenVPN Server is not created
Status in NetworkManager:
Fix Released
Status in network-manager package in Ubuntu:
Fix Released
Bug description:
Hi,
When the OpenVPN server pushes routes that overlaps with the openvpn server
IP, it should add a route to the OpenVPN server.
This seems to get done, but it fails:
NetworkManager[1031]: <debug> [1521794922.6687] platform: signal: route 6
added: 2a00:x:x::3/128 via fe80::230:48ff:fedc:5067 dev 2 metric 100 mss 0
rt-src rt-ra src ::/128 pref-src 2a02:x:x:x:x:x:x:5fc6
NetworkManager[1031]: <debug> [1521794922.6687] device[0x55566c34c4e0]
(enxa44cc890f4c8): queued IP6 config change
NetworkManager[1031]: <warn> [1521794922.6688] platform: route: get IPv6
route for: 2a00:x:x::3 failed with unspecified
2a00:x:x::3 => VPN Server IPv6
Now this seems to be fixed in commit:
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=2d1fad641b950520bec1a87c450d0e3b1439e262
Can we get this cherry-picked in Bionic?
Thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1758331/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
