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.

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

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

  • July 7, 2017 at 3:38 AM
    Permalink

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

    Reply
    • July 7, 2017 at 7:25 AM
      Permalink

      Thanks ! Glad it worked for you

      Reply
    • July 9, 2017 at 2:53 PM
      Permalink

      Hi Miguel , Glad it worked for you

      Reply
  • August 14, 2017 at 2:37 PM
    Permalink

    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!

    Reply
    • August 14, 2017 at 9:07 PM
      Permalink

      Hey JJ , I am Glad it worked for you 🙂

      Reply
  • November 1, 2017 at 1:47 AM
    Permalink

    Thanks! It worked 😀

    Reply
    • November 4, 2017 at 6:18 PM
      Permalink

      Glad to know that it worked for you 🙂

      Reply
  • November 10, 2017 at 10:27 AM
    Permalink

    system ct1 command not working —
    displaying command not found

    Reply
    • November 10, 2017 at 10:09 PM
      Permalink

      Hi hardik,

      Its systemctl , You typed numeric one instead of L

      Reply
    • November 14, 2017 at 9:00 AM
      Permalink

      you’re welcome

      Reply
  • November 16, 2017 at 5:08 PM
    Permalink

    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? 🙂

    Reply
    • November 16, 2017 at 10:33 PM
      Permalink

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

      Reply
  • November 17, 2017 at 12:07 AM
    Permalink

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

    Reply
    • November 18, 2017 at 10:18 AM
      Permalink

      you’re welcome 🙂

      Reply
  • December 16, 2017 at 3:38 AM
    Permalink

    This solution worked 🙂

    Reply
  • December 20, 2017 at 6:27 AM
    Permalink

    Thank you for the quick fix

    Reply
  • January 1, 2018 at 10:12 PM
    Permalink

    Awesome fix sir! Thank you!

    Reply
  • January 14, 2018 at 4:18 PM
    Permalink

    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.

    Reply
    • January 14, 2018 at 5:47 PM
      Permalink

      Thank you so much for the info 🙂

      Reply
    • January 22, 2018 at 10:22 AM
      Permalink

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

      Reply
      • January 22, 2018 at 10:22 AM
        Permalink

        I mean the comment about systemd

        Reply
  • January 22, 2018 at 5:25 PM
    Permalink

    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.

    Reply
  • January 30, 2018 at 6:10 PM
    Permalink

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

    Reply
  • February 6, 2018 at 2:23 PM
    Permalink

    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.

    Reply
  • March 21, 2018 at 4:18 AM
    Permalink

    fixed for me . Thanks!

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

    Reply

Leave a Reply

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

%d bloggers like this: