Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager (Ubuntu) |
Fix Released
|
High
|
ajay rahul | ||
Zesty |
Won't Fix
|
High
|
Unassigned |
Bug Description
According to
https:/
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:/
Related branches
- Tony Espy: Approve
- Network-manager: Pending requested
-
Diff: 264 lines (+52/-19)7 files modifieddev/null (+0/-11)
snap-common/bin/networkmanager (+9/-0)
snap-common/bin/snap-config.sh (+25/-0)
snap-common/bin/snap-prop.sh (+6/-0)
snap-common/etc/NetworkManager/NetworkManager.conf (+3/-2)
snap/hooks/configure (+9/-0)
snap/snapcraft.yaml (+0/-6)
affects: | ubuntu-gnome → network-manager (Ubuntu) |
description: | updated |
summary: |
- Ubuntu GNOME 17.04 beta: wi-fi not working — mac address keeps changing? + Ubuntu 17.04: wi-fi not working — mac address keeps changing? |
summary: |
- Ubuntu 17.04: wi-fi not working — mac address keeps changing? + Ubuntu 17.04: New privacy feature in NetworkManager stops some USB WiFi + adapters from working (mac address randomization) |
description: | updated |
Changed in network-manager (Ubuntu): | |
importance: | Undecided → High |
summary: |
- Ubuntu 17.04: New privacy feature in NetworkManager stops some WiFi - adapters from working (mac address randomization) + Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi + adapters from working (MAC Address Randomization issue) |
Changed in network-manager (Ubuntu Zesty): | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in network-manager (Ubuntu): | |
assignee: | nobody → ajay rahul (ajayrahulapiswi) |
Miraculously, a user from omgubuntu.co.uk had written a comment in one of their articles announcing the release of 17.04 that fixed this issue. The comment is as follows:
"# wifi and networkmanager
The new NetworkManager release 1.4.0 adds new features to change the current MAC address of your Ethernet or Wi-Fi card (spoofing/cloning). As a debian "sid" user i understand that being on bleeding edge, sometimes new features and configs can be Incompatible with my machine hardware!!! Now being a ubuntu user i can see that ubuntu is losing his "user friendly" name and no more care for desktop users! This was an unacceptable default config on Ubuntu's best days! Ubuntu haters and criticists must be happy now!
# fix it
edit the /etc/NetworkMan ager/NetworkMan ager.conf file
And add:
[device] rand-mac- address= no
wifi.scan-
Restart the networkmanager service and use your wireless connection :)"
I found that applying his fix by opening a Terminal and typing "sudo gedit /etc/NetworkMan ager/NetworkMan ager.conf" , adding the text he described, then rebooting my machine fixed the issue.
That being said, this default behavior is still a major bug and breaks functionality of wi-fi hardware for users, and definitely needs to be looked at. Thanks for your time!