[Touch-packages] [Bug 1858092] Re: Network Manager not saving OpenVPN password
Can confirm that, after updating from the official repositories (Kubuntu 19.10), saving passwords "for this user only" works as intended again. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: Fix Released Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1858092] Re: Network Manager not saving OpenVPN password
Is there an estimation when this will go from proposed to release? I'm working around it by looking up the connections' UID in the Network- Manager configuration and manually adding the corresponding entries in KWallet as of now.. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Can confirm: #82 does the trick. Thanks Nicholas, you're awesome! Let's hope this goes into 17.04 release or at least in zesty-updates. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Confirmed Status in network-manager source package in Zesty: Confirmed Status in network-manager source package in Artful: Confirmed Bug description: [Impact] * NetworkManager incorrectly handles dns-priority of the VPN-like connections, which leads to leaking DNS queries outside of the VPN into the general internet. * Upstream has resolved this issue in master and 1.8 to correctly configure any dns backends with negative dns-priority settings. [Test Case] #FIXME# * detailed instructions how to reproduce the bug * these should allow someone who is not familiar with the affected package to reproduce the bug and verify that the updated package fixes the problem. #FIXME# [Regression Potential] * If this issue is changed DNS resolution will change, for certain queries, to go via VPN rather than general internet. And therefore, one may get new/different results or even loose access to resolve/access certain parts of the interent depending on what the DNS server on VPN chooses to respond to. [Other Info] * Original bug report I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1624317/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
Can confirm: Still present in Kubuntu 17.04. Excerpt from /var/log/syslog: May 9 10:52:20 edbook NetworkManager[938]: [1494319940.4289] vpn-connection[0x561ae8e38690,34bc52ee-321f-42eb-af39-9dfc33ee2c5c,"WorkVPN",7:(tun0)]: Data: Internal DNS: 10.42.10.2 May 9 10:52:20 edbook NetworkManager[938]: [1494319940.4289] vpn-connection[0x561ae8e38690,34bc52ee-321f-42eb-af39-9dfc33ee2c5c,"WorkVPN",7:(tun0)]: Data: DNS Domain: '[localdomain_propagated_by_vpn]' ico@edbook:~$ nmcli device show tun0 GENERAL.DEVICE: tun0 GENERAL.TYPE: tun GENERAL.HWADDR: GENERAL.MTU:1500 GENERAL.STATE: 100 (connected) GENERAL.CONNECTION: tun0 GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/10 IP4.ADDRESS[1]: 10.52.0.2/24 IP4.GATEWAY: IP4.ROUTE[1]: dst = 10.42.0.0/18, nh = 10.52.0.1, mt = 50 IP4.ROUTE[2]: dst = 10.42.90.0/24, nh = 10.52.0.1, mt = 50 IP4.ROUTE[3]: dst = 10.42.80.0/24, nh = 10.52.0.1, mt = 50 IP6.ADDRESS[1]: fe80::e9e3:17e7:f72:e672/64 IP6.GATEWAY: Also, since dnsmasq appears not to be used anymore in favor of systemd-resolved, the "old" workaround of commenting out the dns=dnsmasq line in NetworkManager.conf isn't applicable anymore. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Expired Status in openvpn package in Ubuntu: Expired Bug description: [Triage Notes] This bug can no longer make progress. Please see comment 50 for details and further instructions. [Original Description] When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354924] Re: Networkmanager does not autoconnect to wireless network
Same problem here on Kubuntu 14.10 on a Dell Latitude E6410 (Intel 5 Series Chipset). Everything worked flawlessly before the upgrade from 14.04 to 14.10. I also tried the supposed fix from #51, but that didn't help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1354924 Title: Networkmanager does not autoconnect to wireless network Status in network-manager package in Ubuntu: Confirmed Bug description: When adding a net wireless network and enable connect automatically' networkmanager does not automatically connect to the network wenever possible. I'm running kubuntu 14.10 daily. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu23 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Aug 10 21:30:03 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-07-11 (29 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140710) IpRoute: default via 192.168.0.2 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.213 metric 9 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
