Can’t connect to WiFi in debian 9 and Ubuntu 17.04/17.10 [FIXED]

Published by shyam jos on

Recently I installed Debian 9 xfce on my home desktop, I was able to connect to the wi-fi network at the time of installation but after logging into desktop I am not able to connect to any wi-fi network using network manager.

After some searching I have found that this issue is due to the new privacy feature (MAC address randomization) in the new version of NetworkManager causing some wi-fi adaptors to stop working.

Both Debian 9 and Ubuntu 17.04/17.10 are badly affected with this bug, You can read more about this bug in Debian 9 here and Ubuntu 17.04/17.10 here .

Follow below steps to fix this issue in Debian 9 and Ubuntu 17.04/17.10
Edit NetworkManager config file
 sudo nano /etc/NetworkManager/NetworkManager.conf

Now add below lines to the file


[device]
wifi.scan-rand-mac-address=no

 

Restart NetworkManager service
 sudo systemctl restart NetworkManager 

Now you will be able connect to wi-fi network.

Categories: Tutorials

shyam jos

My name is Shyam Jos, I am a passionate Linux system administrator from Kochi, India. I am a strong advocate of using Linux and Open-Source software.

37 Comments

Tom Mendoza · July 7, 2017 at 3:38 AM

wow! fixed the issue in deb 9
thank you for your help

    shyam jos · July 7, 2017 at 7:25 AM

    Thanks ! Glad it worked for you

Miguel · July 9, 2017 at 10:38 AM

thank you!

    shyam jos · July 9, 2017 at 2:53 PM

    Hi Miguel , Glad it worked for you

JJ · August 14, 2017 at 2:37 PM

You made my day. I was going crazy because my USB wireless adapter would connect and work as it should on Mint and other distros and just would not connect on Debian 9. Thanks to you my WiFi now works!

    shyam jos · August 14, 2017 at 9:07 PM

    Hey JJ , I am Glad it worked for you 🙂

Dude · November 1, 2017 at 1:47 AM

Thanks! It worked 😀

    shyam jos · November 4, 2017 at 6:18 PM

    Glad to know that it worked for you 🙂

kofran · November 1, 2017 at 6:56 PM

Thanks! works at first strike!

Hardik Chugh · November 10, 2017 at 10:27 AM

system ct1 command not working —
displaying command not found

    shyam jos · November 10, 2017 at 10:09 PM

    Hi hardik,

    Its systemctl , You typed numeric one instead of L

lucas · November 14, 2017 at 6:28 AM

thanks so much!!!

    shyam jos · November 14, 2017 at 9:00 AM

    you’re welcome

Prav · November 16, 2017 at 5:08 PM

Hi,

Please can you assist me, I have been trying for 3 days now on Ubuntu 17.10 and 16.04 and when I start browsing the net my wifi suddenly drops and even after a restart it does not work, does anyone have suggestions please? 🙂

    shyam jos · November 16, 2017 at 10:33 PM

    Which Browser you’re using ?, I have seen similar bug in chromium browser.

Israel · November 17, 2017 at 12:07 AM

I really appreciate your help, it fixs my problem with debian 9. Thanks a lot!!!!

    shyam jos · November 18, 2017 at 10:18 AM

    you’re welcome 🙂

Mateusz · December 16, 2017 at 3:38 AM

This solution worked 🙂

Doug · December 19, 2017 at 9:59 AM

Awesome! Thanks. That worked pefectly.

Andrew Tarr · December 20, 2017 at 6:27 AM

Thank you for the quick fix

Dave · January 1, 2018 at 10:12 PM

Awesome fix sir! Thank you!

cc · January 14, 2018 at 4:18 PM

Thank you for your advice, sir, but the problem most probably isn’t the hardware address randomization itself (it’s been in NetworkManager since 1.2), but systemd not abiding driver limitations while renaming interfaces.
Disabling the systemd renaming “service” (ln -s /dev/null /etc/systemd/network/99-default.link or net.ifnames=0 argument) should reenable the kernel-given names and fix the crash while keeping the MAC address randomization.
You can also set your own custom names as explained here: https://www.freedesktop.org/software/systemd/man/systemd.link.html, preferable if using multiple interfaces and extensive firewall rules.

    shyam jos · January 14, 2018 at 5:47 PM

    Thank you so much for the info 🙂

    what · January 22, 2018 at 10:22 AM

    Could someone please do an easy tutorial of this, I didn’t understand

      what · January 22, 2018 at 10:22 AM

      I mean the comment about systemd

Evildead · January 22, 2018 at 5:25 PM

Hi,

Thanks a lot, this bug has been driving me crazy for the past weeks, sometimes I was not able to connect to some Wi-Fi networks that were working perfectly fine a few minutes before. Now everything seems to be working just fine.

Francisco · January 30, 2018 at 6:10 PM

I don’t believe this will work but magically works as well without renaming network adapter. Thank you very much.

Owen · February 6, 2018 at 2:23 PM

You are a lifesaver man thank you. Stuff like this always makes me shake my head. People always say Linux is a bit of a steep learning curve. Nah, it’s not, just a lot of shit is broken out of the box. Let’s just be honest.

Danilo · March 21, 2018 at 4:18 AM

fixed for me . Thanks!

root@iluvatar:/home# uname -r
4.9.0-6-amd64

man · April 2, 2018 at 9:45 PM

Thanks!

Mat · April 25, 2018 at 12:04 AM

Three simple things to do and it works. Thank you very much. I searched solution few times few hours, Now I know how to solved that problem.

Muh · May 3, 2018 at 4:40 AM

Thank you man you save my a**

Nepa · May 21, 2018 at 11:38 PM

I really appriacite your help! You are a master! Thanks a lot!

Wanderley Brandao · June 2, 2018 at 4:58 AM

Worked like a charm !
Thank you !

Jason · August 11, 2018 at 11:00 PM

Thanks! I just installed BunsenLabs Helium and could not get the wifi adapter working. This did the trick!

someone · September 21, 2018 at 1:26 AM

thanks for the post I’ve been tinkering with a new install for about an hour until I stumbled upon your post

Mengatasi Wifi tidak bisa connect di Debian/Blankon XI Uluwatu dan turunannya | Artemtech · May 14, 2018 at 11:19 AM

[…] sumber: linuxsuperuser […]

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.