[Touch-packages] [Bug 1683836] Re: WIFI stoped working when updating 16.10 -> 17.04
Possible dub of bug #1681513 -- 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/1683836 Title: WIFI stoped working when updating 16.10 -> 17.04 Status in network-manager package in Ubuntu: Confirmed Bug description: Network manager detects 'Bus 001 Device 004: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter'. It detects WIFI network, but fails to connect. I booted with older kernel vmlinuz-4.8.0-46-generic: same result. I installed ubuntu 16.10 to same computer and WIFI does work. Password is OK. Authentication seems to fail in Ubuntu 17.04: Apr 18 17:13:01 k10 NetworkManager[727]: [1492524781.2784] policy: auto-activating connection 'ZyXELbb3a' [1492524781.2798] device (wlxc83a35cde1eb): Activation: starting connection 'ZyXELbb3a' (5362ba4d-c40e-40a3-8e17-4e3deaab48ae) [1492524781.2801] device (wlxc83a35cde1eb): state change: disconnected -> prepare (reason 'none') [30 40 0] [1492524781.6699] device (wlxc83a35cde1eb): set-hw-addr: set-cloned MAC address to C8:3A:35:CD:E1:EB (permanent) [1492524781.9391] device (wlxc83a35cde1eb): state change: prepare -> config (reason 'none') [40 50 0] [1492524781.9394] device (wlxc83a35cde1eb): Activation: (wifi) access point 'ZyXELbb3a' has security, but secrets are required. [1492524781.9395] device (wlxc83a35cde1eb): state change: config -> need-auth (reason 'none') [50 60 0] [1492524781.9748] device (wlxc83a35cde1eb): state change: need-auth -> prepare (reason 'none') [60 40 0] [1492524781.9782] device (wlxc83a35cde1eb): state change: prepare -> config (reason 'none') [40 50 0] [1492524781.9792] device (wlxc83a35cde1eb): Activation: (wifi) connection 'ZyXELbb3a' has security, and secrets exist. No new secrets needed. [1492524781.9796] Config: added 'ssid' value 'ZyXELbb3a' [1492524781.9800] Config: added 'scan_ssid' value '1' [1492524781.9803] Config: added 'key_mgmt' value 'WPA-PSK' [1492524781.9806] Config: added 'auth_alg' value 'OPEN' [1492524781.9808] Config: added 'psk' value '' [1492524781.9821] sup-iface[0x55d34390d2d0,wlxc83a35cde1eb]: config: set interface ap_scan to 1 [1492524782.0010] device (wlxc83a35cde1eb): supplicant interface state: inactive -> scanning [1492524783.3941] device (wlxc83a35cde1eb): supplicant interface state: scanning -> authenticating [1492524783.5787] device (wlxc83a35cde1eb): supplicant interface state: authenticating -> disconnected [1492524793.5868] device (wlxc83a35cde1eb): supplicant interface state: disconnected -> scanning [1492524794.9891] device (wlxc83a35cde1eb): supplicant interface state: scanning -> authenticating [1492524795.1145] device (wlxc83a35cde1eb): supplicant interface state: authenticating -> disconnected Ubuntu 16.10 is same to authentication: Apr 18 13:46:10 k15 NetworkManager[714]: [1492512370.3874] policy: auto-activating connection 'ZyXELbb3a' [1492512370.3884] device (wlxc83a35cde1eb): Activation: starting connection 'ZyXELbb3a' (fd199068-2375-4268-bb74-d60484d1fadb) [1492512370.3886] device (wlxc83a35cde1eb): state change: disconnected -> prepare (reason 'none') [30 40 0] [1492512370.3887] manager: NetworkManager state is now CONNECTING [1492512370.3895] device (wlxc83a35cde1eb): state change: prepare -> config (reason 'none') [40 50 0] [1492512370.3897] device (wlxc83a35cde1eb): Activation: (wifi) access point 'ZyXELbb3a' has security, but secrets are required. [1492512370.3898] device (wlxc83a35cde1eb): state change: config -> need-auth (reason 'none') [50 60 0] [1492512370.3936] device (wlxc83a35cde1eb): state change: need-auth -> prepare (reason 'none') [60 40 0] [1492512370.3940] device (wlxc83a35cde1eb): state change: prepare -> config (reason 'none') [40 50 0] [1492512370.3943] device (wlxc83a35cde1eb): Activation: (wifi) connection 'ZyXELbb3a' has security, and secrets exist. No new secrets needed. [1492512370.3943] Config: added 'ssid' value 'ZyXELbb3a' [1492512370.3944] Config: added 'scan_ssid' value '1' [1492512370.3944] Config: added 'key_mgmt' value 'WPA-PSK' [1492512370.3944] Config: added 'auth_alg' value 'OPEN' [1492512370.3944] Config: added 'psk' value '' [1492512370.3949] sup-iface[0x55da7c3f2210,wlxc83a35cde1eb]: config: set interface ap_scan to 1 [1492512371.8005] device (wlxc83a35cde1eb): supplicant interface state: inactive -> authenticating [1492512371.8071] device (wlxc83a35cde1eb): supplicant interface state: authenticating -> associating [1492512371.8216] device (wlxc83a35cde1eb): supplicant interface state: associating -> 4-way handshake [1492512371.8482] device (wlxc83a35cde1eb): supplicant interface state: 4-way handshake -> completed [1492512371.8482] device (wlxc83a35cde1eb): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'ZyXELbb3a'.
[Touch-packages] [Bug 1681513] Re: Ubuntu 17.04: New privacy feature in NetworkManager stops some USB WiFi adapters from working (mac address randomization)
I have this problem too. Adding wifi.scan-rand-mac-address=no to NetworkManager.conf does resolve it. A relevant question: Why does this only affect usb wifi dongles? My internal iwl3945 chip was/is not affected. How does Network Manager treat pci and usb devices differently? -- 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/1681513 Title: Ubuntu 17.04: New privacy feature in NetworkManager stops some USB WiFi adapters from working (mac address randomization) Status in network-manager package in Ubuntu: Confirmed Bug description: According to https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/ there is a new privacy feature in the new version of NetworkManager. This privacy feature can cause some USB WiFi adapters to stop working while they used to work with older versions of NetworkManager (Ubuntu 16.10 or older). The purpose of this privacy feature is to get your computer to report a new random MAC address whenever you connect to a WiFi network. This privacy feature is especially useful when you connect to public WiFi networks, so that the operators cannot identify you when you connect multiple times. The downside of this privacy feature is that some USB WiFi adapters misbehave when NetworkManager tries to change their MAC address repeatedly. The result is that those USB WiFi adapters cannot connect anymore to the WiFi network. Original report follows: My Panda USB wi-fi adapter works just fine on 16.10, but when I try to connect to my wi-fi router in 17.04, GNOME network manager reports "Connection failed." I did some tinkering, and noticed that my MAC address for my wifi adapter, according to GNOME, is DIFFERENT every time I make it forget my wifi settings and try to reconnect. Weird, right? Any leads on a possible fix or work-around? I'm running the latest beta of Ubuntu GNOME 17.04, kernel 4.10.0-19-generic, GNOME 3.24.0. https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in- networkmanager-1-4-0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+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 1668593] Re: Wireless adapter causes hard crash
The two adapters you've listed are both using the rtl8192cu driver that is bug #1666421 , this is a possible duplicate. -- 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/1668593 Title: Wireless adapter causes hard crash Status in network-manager package in Ubuntu: Confirmed Bug description: When I try to connect to a wifi using a USB wifi adapter, the system crashes/freezes immediately. There is nothing in the syslog or anywhere else. This can be reproduced on Ubuntu 14.04 and 16.04. Enabling the adapter works, but the freeze occurs as soon as I try to log into the network. This used to work, but has been broken for a few weeks I assume. It happens with all USB adapters I tested, on all machines. Adapter 1: description: Wireless interface physical id: 1 bus info: usb@2:1.1.1 logical name: wlx74da388dc809 serial: [redacted] capabilities: ethernet physical wireless configuration: broadcast=yes driver=rtl8192cu driverversion=4.4.0-64-generic firmware=N/A link=no multicast=yes wireless=IEEE 802.11bgn Adapter 2: description: Wireless interface physical id: 1 bus info: usb@2:1.1.1 logical name: wlx24050f75f9a2 serial: [redacted] capabilities: ethernet physical wireless configuration: broadcast=yes driver=rtl8192cu driverversion=4.4.0-64-generic firmware=N/A link=no multicast=yes wireless=IEEE 802.11bgn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1668593/+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 1671611] Re: USB wi-fi dongles not working with latest updates
So with that rtl8192 dongle, it crashes/freezes/locks up? See bug #1666421 , this is a possible duplicate. -- 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/1671611 Title: USB wi-fi dongles not working with latest updates Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Same laptop - two different network dongles (ASUS USB-N13 + Edimax cheap commonly used with RaspPis). Confirmed issue with xenial-updates and xenial-security versions. Going to try to force a downgrade to original xenial to see if it still happens. ASUS dongle -> $ inxi -Fxxrzc0 | pastebin https://gist.github.com/d926d05c2bd23226a9f4b4a593b9de65 Edimax dongle -> $ inxi -Fxxrzc0 | pastebin https://gist.github.com/f76284151c225ae43af82de8439efe02 They work fine w/ the 18.1 Installer/Live Boot.. They worked fine after the install.. when I did the latest update they broke. uname -a -> Linux thinkpad 4.8.0-41-generic #44~16.04.1-Ubuntu SMP Fri Mar 3 17:11:16 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description: Linux Mint 18.1 Serena Release: 18.1 kern.log paste: Mar 9 12:11:17 thinkpad kernel: [ 244.854264] usb 1-2: USB disconnect, device number 4 Mar 9 12:11:17 thinkpad kernel: [ 244.864634] wlx2c4d5406c9c1: deauthenticating from 58:6d:8f:8e:02:5d by local choice (Reason: 3=DEAUTH_LEAVING) Mar 9 12:11:17 thinkpad kernel: [ 244.864846] rtl_usb: reg 0x102, usbctrl_vendorreq TimeOut! status:0xffed value=0xf00069ce Mar 9 12:11:17 thinkpad kernel: [ 244.864858] rtl_usb: reg 0x422, usbctrl_vendorreq TimeOut! status:0xffed value=0x69543424 Mar 9 12:11:17 thinkpad kernel: [ 244.864866] rtl_usb: reg 0x542, usbctrl_vendorreq TimeOut! status:0xffed value=0x69543424 Mar 9 12:11:17 thinkpad kernel: [ 244.864879] rtl_usb: reg 0x1cc, usbctrl_vendorreq TimeOut! status:0xffed value=0x1950812 Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3310] sup-iface[0xa2d380,wlx2c4d5406c9c1]: connection disconnected (reason -3) Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3318] device (wlx2c4d5406c9c1): state change: activated -> unmanaged (reason 'removed') [100 10 36] Mar 9 12:11:17 thinkpad kernel: [ 244.899266] cfg80211: World regulatory domain updated: Mar 9 12:11:17 thinkpad kernel: [ 244.899273] cfg80211: DFS Master region: unset Mar 9 12:11:17 thinkpad kernel: [ 244.899275] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Mar 9 12:11:17 thinkpad kernel: [ 244.899280] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Mar 9 12:11:17 thinkpad kernel: [ 244.899283] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Mar 9 12:11:17 thinkpad kernel: [ 244.899286] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) Mar 9 12:11:17 thinkpad kernel: [ 244.899290] cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) Mar 9 12:11:17 thinkpad kernel: [ 244.899295] cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s) Mar 9 12:11:17 thinkpad kernel: [ 244.899298] cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) Mar 9 12:11:17 thinkpad kernel: [ 244.899301] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) Mar 9 12:11:17 thinkpad kernel: [ 244.899304] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3642] dhcp4 (wlx2c4d5406c9c1): canceled DHCP transaction, DHCP client pid 2225 Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3643] dhcp4 (wlx2c4d5406c9c1): state changed bound -> done Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3703] platform-linux: do-change-link[2]: failure changing link: failure 19 (No such device) Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3705] platform-linux: do-change-link[2]: failure changing link: failure 19 (No such device) Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3708] dns-mgr: Writing DNS information to /sbin/resolvconf Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3879] platform-linux: do-change-link[2]: failure changing link: failure 19 (No such device) Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3879] device (wlx2c4d5406c9c1): failed to disable userspace IPv6LL address handling Mar 9 12:11:17 thinkpad NetworkManager[989]: [1489083077.3880] radio killswitch /sys/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/ieee80211/phy0/rfkill0 disappeared Mar 9 12:11:17 thinkpad NetworkManager[989]:
