[Touch-packages] [Bug 2026235] Re: Merge a5e6c8498ca, corrupted resolfconf results in inability to talk to link local DNS servers
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2026235 Title: Merge a5e6c8498ca, corrupted resolfconf results in inability to talk to link local DNS servers Status in systemd package in Ubuntu: New Bug description: Package: systemd 249.11-0ubuntu3.9 https://packages.ubuntu.com/jammy/systemd Description: Ubuntu 22.04.2 LTS Release: 22.04 Please merge https://github.com/systemd/systemd/commit/a5e6c8498ca for the Ubuntu LTS release. It's a one-line fix that sets an uninitialized variable to zero. Until this fix is implemented, resolveconf generates incorrect DNS configuration for link-local IPv6 addresses discovered from Router Advertisements (RA). It retrieves the correct address, but then appends a random interface index. So, instead of fe80:::, the DNS server reads fe80:::%NNN This results in the client no longer being able to reach the locally configured DNS server. This bug can be reproduced by installing a DNS server and radvd (Router Advertisement demon) in an LXC container that shares a network bridge with another container running Ubuntu Jammy. If Jammy is configured to accept RDNSS information from RA, it will set the wrong server address. I believe this only works if radvd advertises a link-local addresses as part of the RDNSS information. If instead, it advertises a globally routable address (e.g. 2001:::) there is no issue. While uninitialized memory is always scary, I don't believe this is worse than maybe a denial-of-service attack? So, not quite sure whether this is an exploitable security issue. But that probably depends on exactly how the network topology looks like and whether an attacker can gain (limited) control over manipulating RA packets. It is possible that some clusters and/or containers would suffer security issues because of this problem. Also, this is technically a way to leak memory from within a systemd- related process. But I don't see an obvious way how to exploit this very limited data leak. Out of an abundance of precaution, I am marking this as a security issue. Please feel free to unflag, if you think that assessment isn't warranted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2026235/+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 1663918] Re: Network Manager fails to reconnect to wifi after resuming from suspend
*** This bug is a duplicate of bug 1676810 *** https://bugs.launchpad.net/bugs/1676810 ** This bug has been marked a duplicate of bug 1676810 Network Manager needs restarting from sleep -- 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/1663918 Title: Network Manager fails to reconnect to wifi after resuming from suspend Status in network-manager package in Ubuntu: Confirmed Bug description: After resuming from suspend on my laptop, I have wifi enabled, but Network Manager does not automatically reconnect, and it's list of available wifi networks is blank. If I run `sudo service network-manager restart`, then this fixes everything and it automatically detects and connects to my wifi hotspot, but this shouldn't be necessary. This problem seems specific to 16.04. Under 14.04, NM worked perfectly. After I upgraded my 14.04 install to 16.04 it started happening, however, I assumed this was likely due to some broken config file leftover from the upgrade. However, I recently did a fresh install to the same laptop on a blank hard drive, and the problem still exists. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Feb 11 13:25:56 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-01-21 (20 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.122 metric 600 192.168.121.0/24 dev virbr1 proto kernel scope link src 192.168.121.1 linkdown 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1663918/+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 1676810] Re: Network Manager needs restarting from sleep
Please note that bug 1666318 has relevant information. It appears that editing /etc/NetworkManager/NetworkManager.conf and removing "dns=dnsmasq" makes the problem go away. So, this could be a bug in either network manager or in dnsmasq -- 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/1676810 Title: Network Manager needs restarting from sleep Status in network-manager package in Ubuntu: Confirmed Bug description: Each time my laptop is suspended and resumed, Network Manager seems unable to bring up Wifi. Calling... sudo service network-manager restart ...resolves the problem. I therefore placed the attached file at... /lib/systemd/system-sleep/network-manager ...which provides a workaround for the problem. However, there must be some kind of underlying bug in network-manager which requires it to be restarted after every suspend/resume cycle. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: LXDE Date: Tue Mar 28 10:21:35 2017 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp1s0 proto static metric 600 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.203 metric 600 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/1 docker0 ac7e4d66-b979-41de-b4b2-6f7c5dffc232 /org/freedesktop/NetworkManager/ActiveConnection/0 wlp1s0 wifi connected /org/freedesktop/NetworkManager/Devices/0 Kitchen 2 937ae07a-fb47-46ac-91a4-0fe200203a95 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676810/+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 1666318] Re: Disconnecting and reconnecting docking station breaks DNS
*** This bug is a duplicate of bug 1676810 *** https://bugs.launchpad.net/bugs/1676810 ** This bug has been marked a duplicate of bug 1676810 Network Manager needs restarting from sleep -- 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/1666318 Title: Disconnecting and reconnecting docking station breaks DNS Status in network-manager package in Ubuntu: New Bug description: I'm not sure which package this bug should be submitted to as service troubleshooting in the latest few Ubuntu releases is a jumbled mess. Anyway, here's how to repro the problem: - Lenovo Carbon X1 2016 (4th gen), OneLink+ docking station - Ethernet connected to docking station - Disconnect docking station - Reconnect docking station From this point on all DNS requests fail. Workarounds I found so far: - reboot the machine (not really a solution) - sudo system network-manager restart (requires sudo access) - usually in older releases I'd just poke around with the resolver config files, but anything I do seems to be ignored now so I gave up and posted a bug instead. Here's the journalctl log for NetworkManager, followed by an example of the problem: nico@nico-lenovo-ubuntu:~$ journalctl -u NetworkManager -f -- Logs begin at Sun 2017-02-19 00:10:56 GMT. -- Feb 20 20:22:41 nico-lenovo-ubuntu NetworkManager[6715]: [1487622161.9976] dns-mgr: Writing DNS information to /sbin/resolvconf Feb 20 20:22:42 nico-lenovo-ubuntu dnsmasq[6728]: setting upstream servers from DBus Feb 20 20:22:42 nico-lenovo-ubuntu dnsmasq[6728]: using nameserver 194.168.4.100#53(via lan1) Feb 20 20:22:42 nico-lenovo-ubuntu dnsmasq[6728]: using nameserver 194.168.8.100#53(via lan1) Feb 20 20:22:42 nico-lenovo-ubuntu dnsmasq[6728]: using nameserver 194.168.4.100#53(via wifi0) Feb 20 20:22:42 nico-lenovo-ubuntu dnsmasq[6728]: using nameserver 194.168.8.100#53(via wifi0) Feb 20 20:22:42 nico-lenovo-ubuntu NetworkManager[6715]: [1487622162.0156] device (wifi0): Activation: successful, device activated. Feb 20 20:22:42 nico-lenovo-ubuntu NetworkManager[6715]: [1487622162.0169] manager: startup complete Feb 20 20:22:43 nico-lenovo-ubuntu NetworkManager[6715]: [1487622163.1408] manager: WiFi hardware radio set enabled Feb 20 20:22:43 nico-lenovo-ubuntu NetworkManager[6715]: [1487622163.1409] manager: WWAN hardware radio set disabled Feb 20 20:27:40 nico-lenovo-ubuntu dhclient[6736]: receive_packet failed on lan1: Network is down Feb 20 20:27:40 nico-lenovo-ubuntu NetworkManager[6715]: [1487622460.1588] manager: NetworkManager state is now CONNECTED_LOCAL Feb 20 20:27:40 nico-lenovo-ubuntu NetworkManager[6715]: [1487622460.1589] manager: NetworkManager state is now CONNECTED_GLOBAL Feb 20 20:27:40 nico-lenovo-ubuntu NetworkManager[6715]: [1487622460.1590] policy: set 'Auto ITADINANTA' (wifi0) as default for IPv4 routing and DNS Feb 20 20:27:40 nico-lenovo-ubuntu NetworkManager[6715]: [1487622460.1590] device (lan1): state change: activated -> unmanaged (reason 'removed') [100 10 36] Feb 20 20:27:40 nico-lenovo-ubuntu NetworkManager[6715]: [1487622460.1594] dhcp4 (lan1): canceled DHCP transaction, DHCP client pid 6736 Feb 20 20:27:40 nico-lenovo-ubuntu NetworkManager[6715]: [1487622460.1595] dhcp4 (lan1): state changed bound -> done Feb 20 20:27:40 nico-lenovo-ubuntu NetworkManager[6715]: [1487622460.1618] dns-mgr: Writing DNS information to /sbin/resolvconf Feb 20 20:27:40 nico-lenovo-ubuntu dnsmasq[6728]: setting upstream servers from DBus Feb 20 20:27:40 nico-lenovo-ubuntu dnsmasq[6728]: using nameserver 194.168.4.100#53(via wifi0) Feb 20 20:27:40 nico-lenovo-ubuntu dnsmasq[6728]: using nameserver 194.168.8.100#53(via wifi0) Feb 20 20:27:40 nico-lenovo-ubuntu NetworkManager[6715]: [1487622460.1799] platform-linux: do-change-link[5]: failure changing link: failure 19 (No such device) Feb 20 20:27:40 nico-lenovo-ubuntu NetworkManager[6715]: [1487622460.1800] device (lan1): failed to disable userspace IPv6LL address handling Feb 20 20:27:40 nico-lenovo-ubuntu NetworkManager[6715]: [1487622460.1803] devices removed (path: /sys/devices/pci:00/:00:14.0/usb2/2-4/2-4.1/2-4.1.3/2-4.1.3:2.0/net/lan1, iface: lan1) Feb 20 20:27:56 nico-lenovo-ubuntu NetworkManager[6715]: [1487622476.6972] device (eth0): failed to find device 6 'eth0' with udev Feb 20 20:27:56 nico-lenovo-ubuntu NetworkManager[6715]: [1487622476.6990] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/4) Feb 20 20:27:56 nico-lenovo-ubuntu NetworkManager[6715]: [1487622476.7679] device (eth0): interface index 6 renamed iface from 'eth0' to 'lan1' Feb 20 20:27:56 nico-lenovo-ubuntu NetworkManager[6715]: [1487622476.7742] devices added (path: /sys/devices/pci:00/:00:14.0/usb2/2-4
[Touch-packages] [Bug 1667247] Re: NetworkManager stops working until re-run
*** This bug is a duplicate of bug 1676810 *** https://bugs.launchpad.net/bugs/1676810 ** This bug has been marked a duplicate of bug 1676810 Network Manager needs restarting from sleep -- 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/1667247 Title: NetworkManager stops working until re-run Status in network-manager package in Ubuntu: New Bug description: after awake from sleep(open my lenovo laptop lid) network manager shows - it is connected to one of wi-fi's networks (not mine) - switching on\off wifi, networking service doesn't help. Here is workaround: ps -Af | grep -i networkmanager (write down the pid) sudo kill pid sudo /usr/sbin/NetworkManager --no-daemon It happens time to time when awake after sleep ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 Uname: Linux 4.4.23-040423-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 23 11:57:58 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-12-17 (433 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.65 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-08-17 (189 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected/org/freedesktop/NetworkManager/Devices/0 beeline-198 242d5038-e875-4c07-b0ec-ba6fc4470e24 /org/freedesktop/NetworkManager/ActiveConnection/0 eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1667247/+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 1676081] Re: No wifi connection after suspend with a MacBook Pro
*** This bug is a duplicate of bug 1676810 *** https://bugs.launchpad.net/bugs/1676810 ** This bug has been marked a duplicate of bug 1676810 Network Manager needs restarting from sleep -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1676081 Title: No wifi connection after suspend with a MacBook Pro Status in network-manager package in Ubuntu: Confirmed Status in wpa package in Ubuntu: Confirmed Bug description: I installed Ubuntu 16.10 on a MacBook Pro and, even though the bug should have been fixed in Xenial (see bug 1422143), I lose my wifi connection each time I get back from suspend (when opening the lid). # Expected behavior: Not losing the wifi connection. # Actual behavior: Wifi connection is lost all the time. # Workaround: The workaround explained in the comment 50 of the previous bug worked for me: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143/comments/50 Side effect: it closes the VPN connection if there was one. # Note: I've been advised to create a new bug for this (see https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143/comments/63) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676081/+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
