Won't automatically reconnect wifi on startup (18.10)












0















Started having this problem in 18.04 before I upgraded.



Wifi will not automatically reconnect when I reboot. It requires me to reselect the network and reenter the password each time. Tried removing the connection and remaking it, no dice. All proper checkboxes in NetworkManager are checked. nmcli shows that it's making a NEW connection each time; all the old connections are listed in a merry line. I think this may have started when I tried to bridge my wifi to my wired ethernet connection to get my Vizio Smart TV (which is my primary monitor) to act right. (Spoiler alert: didn't help, but that's Vizio's fault.) The bridge shows up in nmcli and nm-connection-editor. Even if I delete the bridge, it's there again when I restart. Have unplugged the ethernet cable and gone through all the steps again, still the bridge reappears. If I can't get an easy fix with this, can someone at least give me a hand figuring out the proper command line to use with nmcli to pick a named connection (the top wifi connection in nmcli c) and connect it with nmcli d? If necessary I'll just drop that in my startup, but I'd rather get Ubuntu to work the way it's supposed to.



Update: When I try to get nmcli to connect using an older connection (one from any prior reboot) it tells me
Error: Connection activation failed: No suitable device found for this connection.
I looked at the connection files in /etc/NetworkManager/system-connections/ and the difference between them seems to be the uuid and for some reason the MAC address. Isn't the MAC address hardcoded? Hmm...



Added line to NetworkManager.conf to stop randomizing MAC address on connect. Rebooted. No effect.










share|improve this question





























    0















    Started having this problem in 18.04 before I upgraded.



    Wifi will not automatically reconnect when I reboot. It requires me to reselect the network and reenter the password each time. Tried removing the connection and remaking it, no dice. All proper checkboxes in NetworkManager are checked. nmcli shows that it's making a NEW connection each time; all the old connections are listed in a merry line. I think this may have started when I tried to bridge my wifi to my wired ethernet connection to get my Vizio Smart TV (which is my primary monitor) to act right. (Spoiler alert: didn't help, but that's Vizio's fault.) The bridge shows up in nmcli and nm-connection-editor. Even if I delete the bridge, it's there again when I restart. Have unplugged the ethernet cable and gone through all the steps again, still the bridge reappears. If I can't get an easy fix with this, can someone at least give me a hand figuring out the proper command line to use with nmcli to pick a named connection (the top wifi connection in nmcli c) and connect it with nmcli d? If necessary I'll just drop that in my startup, but I'd rather get Ubuntu to work the way it's supposed to.



    Update: When I try to get nmcli to connect using an older connection (one from any prior reboot) it tells me
    Error: Connection activation failed: No suitable device found for this connection.
    I looked at the connection files in /etc/NetworkManager/system-connections/ and the difference between them seems to be the uuid and for some reason the MAC address. Isn't the MAC address hardcoded? Hmm...



    Added line to NetworkManager.conf to stop randomizing MAC address on connect. Rebooted. No effect.










    share|improve this question



























      0












      0








      0








      Started having this problem in 18.04 before I upgraded.



      Wifi will not automatically reconnect when I reboot. It requires me to reselect the network and reenter the password each time. Tried removing the connection and remaking it, no dice. All proper checkboxes in NetworkManager are checked. nmcli shows that it's making a NEW connection each time; all the old connections are listed in a merry line. I think this may have started when I tried to bridge my wifi to my wired ethernet connection to get my Vizio Smart TV (which is my primary monitor) to act right. (Spoiler alert: didn't help, but that's Vizio's fault.) The bridge shows up in nmcli and nm-connection-editor. Even if I delete the bridge, it's there again when I restart. Have unplugged the ethernet cable and gone through all the steps again, still the bridge reappears. If I can't get an easy fix with this, can someone at least give me a hand figuring out the proper command line to use with nmcli to pick a named connection (the top wifi connection in nmcli c) and connect it with nmcli d? If necessary I'll just drop that in my startup, but I'd rather get Ubuntu to work the way it's supposed to.



      Update: When I try to get nmcli to connect using an older connection (one from any prior reboot) it tells me
      Error: Connection activation failed: No suitable device found for this connection.
      I looked at the connection files in /etc/NetworkManager/system-connections/ and the difference between them seems to be the uuid and for some reason the MAC address. Isn't the MAC address hardcoded? Hmm...



      Added line to NetworkManager.conf to stop randomizing MAC address on connect. Rebooted. No effect.










      share|improve this question
















      Started having this problem in 18.04 before I upgraded.



      Wifi will not automatically reconnect when I reboot. It requires me to reselect the network and reenter the password each time. Tried removing the connection and remaking it, no dice. All proper checkboxes in NetworkManager are checked. nmcli shows that it's making a NEW connection each time; all the old connections are listed in a merry line. I think this may have started when I tried to bridge my wifi to my wired ethernet connection to get my Vizio Smart TV (which is my primary monitor) to act right. (Spoiler alert: didn't help, but that's Vizio's fault.) The bridge shows up in nmcli and nm-connection-editor. Even if I delete the bridge, it's there again when I restart. Have unplugged the ethernet cable and gone through all the steps again, still the bridge reappears. If I can't get an easy fix with this, can someone at least give me a hand figuring out the proper command line to use with nmcli to pick a named connection (the top wifi connection in nmcli c) and connect it with nmcli d? If necessary I'll just drop that in my startup, but I'd rather get Ubuntu to work the way it's supposed to.



      Update: When I try to get nmcli to connect using an older connection (one from any prior reboot) it tells me
      Error: Connection activation failed: No suitable device found for this connection.
      I looked at the connection files in /etc/NetworkManager/system-connections/ and the difference between them seems to be the uuid and for some reason the MAC address. Isn't the MAC address hardcoded? Hmm...



      Added line to NetworkManager.conf to stop randomizing MAC address on connect. Rebooted. No effect.







      networking wireless network-manager network-bridge nmcli






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Feb 19 at 13:46







      Icosahedral

















      asked Feb 19 at 12:56









      IcosahedralIcosahedral

      63




      63






















          2 Answers
          2






          active

          oldest

          votes


















          0














          The NetworkManager connection profiles files are stored if in this directory:



          /etc/NetworkManager/system-connections/


          You may try to clean this up and check folder perms:



          sudo chown -R root:root /etc/NetworkManager/system-connections/
          sudo chmod -R 0755 /etc/NetworkManager/system-connections/
          ## if want it to go hard, delete all profiles
          ## sudo rm /etc/NetworkManager/system-connections/*
          sudo systemctl restart network-manager





          share|improve this answer
























          • Deleted all profiles in /etc/NetworkManager/system-connections/ Restarted network-manager service. Had to manually select network and reenter wifi password. Upon reboot, wifi does not automatically start; must manually select network and enter password. Each time, new profile is created in system-connections. Only difference in each profile is the UUID and the last half of the MAC address.

            – Icosahedral
            Feb 21 at 10:25





















          0














          Edited the connection in Network Manager to disable the automatic connection. Applied. Went back and turned it back on. Applied. Also, (and I'm pretty sure this was the culprit) there was a value in place for the MAC address field. Removed it, then Applied the settings. Checked the profile in system-connections, and the MAC field was blank there, too. Rebooted, and the wifi popped right up.



          I think what happened was that it was trying to look for the specific MAC each time it booted up, but the MAC address kept changing, and the new MAC didn't match any of the old profiles so it decided it needed a new profile. By removing the MAC, it was left to auto-configure, turning the existing profile into a one-size-fits-all.






          share|improve this answer
























          • Can someone mark this as SOLVED now?

            – Icosahedral
            Feb 23 at 22:00











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "89"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1119516%2fwont-automatically-reconnect-wifi-on-startup-18-10%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          2 Answers
          2






          active

          oldest

          votes








          2 Answers
          2






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0














          The NetworkManager connection profiles files are stored if in this directory:



          /etc/NetworkManager/system-connections/


          You may try to clean this up and check folder perms:



          sudo chown -R root:root /etc/NetworkManager/system-connections/
          sudo chmod -R 0755 /etc/NetworkManager/system-connections/
          ## if want it to go hard, delete all profiles
          ## sudo rm /etc/NetworkManager/system-connections/*
          sudo systemctl restart network-manager





          share|improve this answer
























          • Deleted all profiles in /etc/NetworkManager/system-connections/ Restarted network-manager service. Had to manually select network and reenter wifi password. Upon reboot, wifi does not automatically start; must manually select network and enter password. Each time, new profile is created in system-connections. Only difference in each profile is the UUID and the last half of the MAC address.

            – Icosahedral
            Feb 21 at 10:25


















          0














          The NetworkManager connection profiles files are stored if in this directory:



          /etc/NetworkManager/system-connections/


          You may try to clean this up and check folder perms:



          sudo chown -R root:root /etc/NetworkManager/system-connections/
          sudo chmod -R 0755 /etc/NetworkManager/system-connections/
          ## if want it to go hard, delete all profiles
          ## sudo rm /etc/NetworkManager/system-connections/*
          sudo systemctl restart network-manager





          share|improve this answer
























          • Deleted all profiles in /etc/NetworkManager/system-connections/ Restarted network-manager service. Had to manually select network and reenter wifi password. Upon reboot, wifi does not automatically start; must manually select network and enter password. Each time, new profile is created in system-connections. Only difference in each profile is the UUID and the last half of the MAC address.

            – Icosahedral
            Feb 21 at 10:25
















          0












          0








          0







          The NetworkManager connection profiles files are stored if in this directory:



          /etc/NetworkManager/system-connections/


          You may try to clean this up and check folder perms:



          sudo chown -R root:root /etc/NetworkManager/system-connections/
          sudo chmod -R 0755 /etc/NetworkManager/system-connections/
          ## if want it to go hard, delete all profiles
          ## sudo rm /etc/NetworkManager/system-connections/*
          sudo systemctl restart network-manager





          share|improve this answer













          The NetworkManager connection profiles files are stored if in this directory:



          /etc/NetworkManager/system-connections/


          You may try to clean this up and check folder perms:



          sudo chown -R root:root /etc/NetworkManager/system-connections/
          sudo chmod -R 0755 /etc/NetworkManager/system-connections/
          ## if want it to go hard, delete all profiles
          ## sudo rm /etc/NetworkManager/system-connections/*
          sudo systemctl restart network-manager






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Feb 19 at 14:02









          cmak.frcmak.fr

          2,4441121




          2,4441121













          • Deleted all profiles in /etc/NetworkManager/system-connections/ Restarted network-manager service. Had to manually select network and reenter wifi password. Upon reboot, wifi does not automatically start; must manually select network and enter password. Each time, new profile is created in system-connections. Only difference in each profile is the UUID and the last half of the MAC address.

            – Icosahedral
            Feb 21 at 10:25





















          • Deleted all profiles in /etc/NetworkManager/system-connections/ Restarted network-manager service. Had to manually select network and reenter wifi password. Upon reboot, wifi does not automatically start; must manually select network and enter password. Each time, new profile is created in system-connections. Only difference in each profile is the UUID and the last half of the MAC address.

            – Icosahedral
            Feb 21 at 10:25



















          Deleted all profiles in /etc/NetworkManager/system-connections/ Restarted network-manager service. Had to manually select network and reenter wifi password. Upon reboot, wifi does not automatically start; must manually select network and enter password. Each time, new profile is created in system-connections. Only difference in each profile is the UUID and the last half of the MAC address.

          – Icosahedral
          Feb 21 at 10:25







          Deleted all profiles in /etc/NetworkManager/system-connections/ Restarted network-manager service. Had to manually select network and reenter wifi password. Upon reboot, wifi does not automatically start; must manually select network and enter password. Each time, new profile is created in system-connections. Only difference in each profile is the UUID and the last half of the MAC address.

          – Icosahedral
          Feb 21 at 10:25















          0














          Edited the connection in Network Manager to disable the automatic connection. Applied. Went back and turned it back on. Applied. Also, (and I'm pretty sure this was the culprit) there was a value in place for the MAC address field. Removed it, then Applied the settings. Checked the profile in system-connections, and the MAC field was blank there, too. Rebooted, and the wifi popped right up.



          I think what happened was that it was trying to look for the specific MAC each time it booted up, but the MAC address kept changing, and the new MAC didn't match any of the old profiles so it decided it needed a new profile. By removing the MAC, it was left to auto-configure, turning the existing profile into a one-size-fits-all.






          share|improve this answer
























          • Can someone mark this as SOLVED now?

            – Icosahedral
            Feb 23 at 22:00
















          0














          Edited the connection in Network Manager to disable the automatic connection. Applied. Went back and turned it back on. Applied. Also, (and I'm pretty sure this was the culprit) there was a value in place for the MAC address field. Removed it, then Applied the settings. Checked the profile in system-connections, and the MAC field was blank there, too. Rebooted, and the wifi popped right up.



          I think what happened was that it was trying to look for the specific MAC each time it booted up, but the MAC address kept changing, and the new MAC didn't match any of the old profiles so it decided it needed a new profile. By removing the MAC, it was left to auto-configure, turning the existing profile into a one-size-fits-all.






          share|improve this answer
























          • Can someone mark this as SOLVED now?

            – Icosahedral
            Feb 23 at 22:00














          0












          0








          0







          Edited the connection in Network Manager to disable the automatic connection. Applied. Went back and turned it back on. Applied. Also, (and I'm pretty sure this was the culprit) there was a value in place for the MAC address field. Removed it, then Applied the settings. Checked the profile in system-connections, and the MAC field was blank there, too. Rebooted, and the wifi popped right up.



          I think what happened was that it was trying to look for the specific MAC each time it booted up, but the MAC address kept changing, and the new MAC didn't match any of the old profiles so it decided it needed a new profile. By removing the MAC, it was left to auto-configure, turning the existing profile into a one-size-fits-all.






          share|improve this answer













          Edited the connection in Network Manager to disable the automatic connection. Applied. Went back and turned it back on. Applied. Also, (and I'm pretty sure this was the culprit) there was a value in place for the MAC address field. Removed it, then Applied the settings. Checked the profile in system-connections, and the MAC field was blank there, too. Rebooted, and the wifi popped right up.



          I think what happened was that it was trying to look for the specific MAC each time it booted up, but the MAC address kept changing, and the new MAC didn't match any of the old profiles so it decided it needed a new profile. By removing the MAC, it was left to auto-configure, turning the existing profile into a one-size-fits-all.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Feb 21 at 10:52









          IcosahedralIcosahedral

          63




          63













          • Can someone mark this as SOLVED now?

            – Icosahedral
            Feb 23 at 22:00



















          • Can someone mark this as SOLVED now?

            – Icosahedral
            Feb 23 at 22:00

















          Can someone mark this as SOLVED now?

          – Icosahedral
          Feb 23 at 22:00





          Can someone mark this as SOLVED now?

          – Icosahedral
          Feb 23 at 22:00


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Ask Ubuntu!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1119516%2fwont-automatically-reconnect-wifi-on-startup-18-10%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          How to make a Squid Proxy server?

          Is this a new Fibonacci Identity?

          19世紀