Connect to network before user login












15














As a learning experiment, I'm trying to turn Ubuntu Desktop into a server. I was able to disable X at boot time and now, I am trying to get my computer to connect to my WiFi network at boot time, before any user logs in. That way, I won't have to be physically near my computer every time it reboots. I've set up the WiFi connection using the Network Manager if that can help somehow (would be nice not having to reconfigure it again!).






networking command-line wireless network-manager







share|improve this question





























    15














    As a learning experiment, I'm trying to turn Ubuntu Desktop into a server. I was able to disable X at boot time and now, I am trying to get my computer to connect to my WiFi network at boot time, before any user logs in. That way, I won't have to be physically near my computer every time it reboots. I've set up the WiFi connection using the Network Manager if that can help somehow (would be nice not having to reconfigure it again!).






    networking command-line wireless network-manager







    share|improve this question



























      15












      15








      15


      5





      As a learning experiment, I'm trying to turn Ubuntu Desktop into a server. I was able to disable X at boot time and now, I am trying to get my computer to connect to my WiFi network at boot time, before any user logs in. That way, I won't have to be physically near my computer every time it reboots. I've set up the WiFi connection using the Network Manager if that can help somehow (would be nice not having to reconfigure it again!).






      networking command-line wireless network-manager







      share|improve this question















      As a learning experiment, I'm trying to turn Ubuntu Desktop into a server. I was able to disable X at boot time and now, I am trying to get my computer to connect to my WiFi network at boot time, before any user logs in. That way, I won't have to be physically near my computer every time it reboots. I've set up the WiFi connection using the Network Manager if that can help somehow (would be nice not having to reconfigure it again!).






      networking command-line wireless network-manager




      networking command-line wireless network-manager






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Apr 13 '17 at 12:24









      Community♦

      1




      1










      asked Dec 6 '10 at 3:53









      Olivier Lalonde

      20.6k50111140




      20.6k50111140






















          4 Answers
          4






          active

          oldest

          votes


















          26














          I found out how to do it :) Simply go into Network Manager > Edit Connections. Select your connection, click Edit and check Available to all users.



          You may also need to add a line for each interface that you want to automatically come up at boot time in /etc/network/interfaces:



          auto eth0
          
auto wifi0





          share|improve this answer























          • Is that working?I have already tried that but it's not working.
            – karthick87
            Dec 6 '10 at 4:12










          • Yep it's working here. The connection doesn't use DHCP but I doubt it wouldn't work because of DHCP.
            – Olivier Lalonde
            Dec 6 '10 at 4:17








          • 3




            The interface cards won't always be named "eth0" and "wifi0". You can find the names of the ethernet interfaces with "cat /proc/net/dev " or "ifconfig".
            – Jonathan
            Dec 11 '15 at 11:05






          • 1




            is doesn't work on my fresh install of Ubuntu 16.04. The network connection is made only after a user logs in. This makes working remote extremely difficult.
            – L. D. James
            Jun 15 '16 at 9:54








          • 1




            It won't work with my 16.04 LTS. It requires logging in on the console, then it connects automatically. Yes, it is checked to be available to all users, even thoguh I am the only one. --> And just to be funny, on the login screen it offers the WiFi networks but when I try to pick on it says insufficient privilege. Ha Ha. Whomever is doing their UI QC has a sense of humor.
            – SDsolar
            Jul 16 '17 at 9:29



















          13














          If you are using Ubuntu 16.x, navigate to /etc/NetworkManager/system-connections/. There you will find a file with the same name as your wireless network. This file contains your wifi credentials and settings. Edit it, find the line with permission=, and remove everything after the = sign (or the whole line).



          Restart and you can connect before login.






          share|improve this answer























          • Additionally, psk-flags=1 means the password is stored encrypted in users home dir. it prob won't work before login in that case. It's less secure, but if you need this to work, you can replace pask-flags=1 with psk=MyWifiPassword. More about that thought: lauri.xn--vsandi-pxa.com/cfgmgmt/…
            – dhaupin
            Apr 14 '17 at 20:37










          • There is nothing after the = sign. And it does not connect until I log in at the console. Since WiFi is my only connection I can't do it remotely - this makes me have to travel to the computer to recover from a reboot. It is on a UPS but even that can only last so long.
            – SDsolar
            Jul 16 '17 at 9:48



















          2














          dhaupin's solution solved my problem with minor modifications:



          My /etc/NetworkManager/system-connections/ file did not have a permission= line. But it did have a psk-flags=1 line. Commenting it out and adding a psk="MyWifiPassword" line fixed the Network-Mangler problem.



          Rebooted and it came up online without logging in.






          share|improve this answer























          • I already had the psk=Mypassword" line and it still doesn't do it.
            – SDsolar
            Jul 16 '17 at 9:49



















          1














          Edit the interfaces file /etc/network/interfaces



          sudo -H gedit /etc/network/interfaces


          Add the following,



          auto ra0
          
iface ra0 inet dhcp
          
wpa-conf /etc/wpa_supplicant.conf





          share|improve this answer























          • Is there a technical difference between the way I did it (see my answer) and yours?
            – Olivier Lalonde
            Dec 6 '10 at 4:07










          • Olivier, I think your solution is more up-to-date, depending as it does on a relatively new feature of NetworkManager. Kathick's solution, on the other hand, circumvents NetworkManager altogether. Your solution might be more robust as NetworkManager keeps track of the connection and reconncects if it is lost temporarily (although the interfaces way might do that too in some cases).
            – loevborg
            Dec 6 '10 at 15:15










          • I hate to mess with that file, plus this computer is alreayd entered into the hosts file of all the other computers as a static IP. wpa_supplicant is fine. And yet it still doesn't do it.
            – SDsolar
            Jul 16 '17 at 9:50













          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%2f16376%2fconnect-to-network-before-user-login%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          4 Answers
          4






          active

          oldest

          votes








          4 Answers
          4






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          26














          I found out how to do it :) Simply go into Network Manager > Edit Connections. Select your connection, click Edit and check Available to all users.



          You may also need to add a line for each interface that you want to automatically come up at boot time in /etc/network/interfaces:



          auto eth0
          
auto wifi0





          share|improve this answer























          • Is that working?I have already tried that but it's not working.
            – karthick87
            Dec 6 '10 at 4:12










          • Yep it's working here. The connection doesn't use DHCP but I doubt it wouldn't work because of DHCP.
            – Olivier Lalonde
            Dec 6 '10 at 4:17








          • 3




            The interface cards won't always be named "eth0" and "wifi0". You can find the names of the ethernet interfaces with "cat /proc/net/dev " or "ifconfig".
            – Jonathan
            Dec 11 '15 at 11:05






          • 1




            is doesn't work on my fresh install of Ubuntu 16.04. The network connection is made only after a user logs in. This makes working remote extremely difficult.
            – L. D. James
            Jun 15 '16 at 9:54








          • 1




            It won't work with my 16.04 LTS. It requires logging in on the console, then it connects automatically. Yes, it is checked to be available to all users, even thoguh I am the only one. --> And just to be funny, on the login screen it offers the WiFi networks but when I try to pick on it says insufficient privilege. Ha Ha. Whomever is doing their UI QC has a sense of humor.
            – SDsolar
            Jul 16 '17 at 9:29
















          26














          I found out how to do it :) Simply go into Network Manager > Edit Connections. Select your connection, click Edit and check Available to all users.



          You may also need to add a line for each interface that you want to automatically come up at boot time in /etc/network/interfaces:



          auto eth0
          
auto wifi0





          share|improve this answer























          • Is that working?I have already tried that but it's not working.
            – karthick87
            Dec 6 '10 at 4:12










          • Yep it's working here. The connection doesn't use DHCP but I doubt it wouldn't work because of DHCP.
            – Olivier Lalonde
            Dec 6 '10 at 4:17








          • 3




            The interface cards won't always be named "eth0" and "wifi0". You can find the names of the ethernet interfaces with "cat /proc/net/dev " or "ifconfig".
            – Jonathan
            Dec 11 '15 at 11:05






          • 1




            is doesn't work on my fresh install of Ubuntu 16.04. The network connection is made only after a user logs in. This makes working remote extremely difficult.
            – L. D. James
            Jun 15 '16 at 9:54








          • 1




            It won't work with my 16.04 LTS. It requires logging in on the console, then it connects automatically. Yes, it is checked to be available to all users, even thoguh I am the only one. --> And just to be funny, on the login screen it offers the WiFi networks but when I try to pick on it says insufficient privilege. Ha Ha. Whomever is doing their UI QC has a sense of humor.
            – SDsolar
            Jul 16 '17 at 9:29














          26












          26








          26






          I found out how to do it :) Simply go into Network Manager > Edit Connections. Select your connection, click Edit and check Available to all users.



          You may also need to add a line for each interface that you want to automatically come up at boot time in /etc/network/interfaces:



          auto eth0
          
auto wifi0





          share|improve this answer














          I found out how to do it :) Simply go into Network Manager > Edit Connections. Select your connection, click Edit and check Available to all users.



          You may also need to add a line for each interface that you want to automatically come up at boot time in /etc/network/interfaces:



          auto eth0
          
auto wifi0






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Dec 24 at 15:36









          Zanna

          50k13131238




          50k13131238










          answered Dec 6 '10 at 4:06









          Olivier Lalonde

          20.6k50111140




          20.6k50111140












          • Is that working?I have already tried that but it's not working.
            – karthick87
            Dec 6 '10 at 4:12










          • Yep it's working here. The connection doesn't use DHCP but I doubt it wouldn't work because of DHCP.
            – Olivier Lalonde
            Dec 6 '10 at 4:17








          • 3




            The interface cards won't always be named "eth0" and "wifi0". You can find the names of the ethernet interfaces with "cat /proc/net/dev " or "ifconfig".
            – Jonathan
            Dec 11 '15 at 11:05






          • 1




            is doesn't work on my fresh install of Ubuntu 16.04. The network connection is made only after a user logs in. This makes working remote extremely difficult.
            – L. D. James
            Jun 15 '16 at 9:54








          • 1




            It won't work with my 16.04 LTS. It requires logging in on the console, then it connects automatically. Yes, it is checked to be available to all users, even thoguh I am the only one. --> And just to be funny, on the login screen it offers the WiFi networks but when I try to pick on it says insufficient privilege. Ha Ha. Whomever is doing their UI QC has a sense of humor.
            – SDsolar
            Jul 16 '17 at 9:29


















          • Is that working?I have already tried that but it's not working.
            – karthick87
            Dec 6 '10 at 4:12










          • Yep it's working here. The connection doesn't use DHCP but I doubt it wouldn't work because of DHCP.
            – Olivier Lalonde
            Dec 6 '10 at 4:17








          • 3




            The interface cards won't always be named "eth0" and "wifi0". You can find the names of the ethernet interfaces with "cat /proc/net/dev " or "ifconfig".
            – Jonathan
            Dec 11 '15 at 11:05






          • 1




            is doesn't work on my fresh install of Ubuntu 16.04. The network connection is made only after a user logs in. This makes working remote extremely difficult.
            – L. D. James
            Jun 15 '16 at 9:54








          • 1




            It won't work with my 16.04 LTS. It requires logging in on the console, then it connects automatically. Yes, it is checked to be available to all users, even thoguh I am the only one. --> And just to be funny, on the login screen it offers the WiFi networks but when I try to pick on it says insufficient privilege. Ha Ha. Whomever is doing their UI QC has a sense of humor.
            – SDsolar
            Jul 16 '17 at 9:29
















          Is that working?I have already tried that but it's not working.
          – karthick87
          Dec 6 '10 at 4:12




          Is that working?I have already tried that but it's not working.
          – karthick87
          Dec 6 '10 at 4:12












          Yep it's working here. The connection doesn't use DHCP but I doubt it wouldn't work because of DHCP.
          – Olivier Lalonde
          Dec 6 '10 at 4:17






          Yep it's working here. The connection doesn't use DHCP but I doubt it wouldn't work because of DHCP.
          – Olivier Lalonde
          Dec 6 '10 at 4:17






          3




          3




          The interface cards won't always be named "eth0" and "wifi0". You can find the names of the ethernet interfaces with "cat /proc/net/dev " or "ifconfig".
          – Jonathan
          Dec 11 '15 at 11:05




          The interface cards won't always be named "eth0" and "wifi0". You can find the names of the ethernet interfaces with "cat /proc/net/dev " or "ifconfig".
          – Jonathan
          Dec 11 '15 at 11:05




          1




          1




          is doesn't work on my fresh install of Ubuntu 16.04. The network connection is made only after a user logs in. This makes working remote extremely difficult.
          – L. D. James
          Jun 15 '16 at 9:54






          is doesn't work on my fresh install of Ubuntu 16.04. The network connection is made only after a user logs in. This makes working remote extremely difficult.
          – L. D. James
          Jun 15 '16 at 9:54






          1




          1




          It won't work with my 16.04 LTS. It requires logging in on the console, then it connects automatically. Yes, it is checked to be available to all users, even thoguh I am the only one. --> And just to be funny, on the login screen it offers the WiFi networks but when I try to pick on it says insufficient privilege. Ha Ha. Whomever is doing their UI QC has a sense of humor.
          – SDsolar
          Jul 16 '17 at 9:29




          It won't work with my 16.04 LTS. It requires logging in on the console, then it connects automatically. Yes, it is checked to be available to all users, even thoguh I am the only one. --> And just to be funny, on the login screen it offers the WiFi networks but when I try to pick on it says insufficient privilege. Ha Ha. Whomever is doing their UI QC has a sense of humor.
          – SDsolar
          Jul 16 '17 at 9:29













          13














          If you are using Ubuntu 16.x, navigate to /etc/NetworkManager/system-connections/. There you will find a file with the same name as your wireless network. This file contains your wifi credentials and settings. Edit it, find the line with permission=, and remove everything after the = sign (or the whole line).



          Restart and you can connect before login.






          share|improve this answer























          • Additionally, psk-flags=1 means the password is stored encrypted in users home dir. it prob won't work before login in that case. It's less secure, but if you need this to work, you can replace pask-flags=1 with psk=MyWifiPassword. More about that thought: lauri.xn--vsandi-pxa.com/cfgmgmt/…
            – dhaupin
            Apr 14 '17 at 20:37










          • There is nothing after the = sign. And it does not connect until I log in at the console. Since WiFi is my only connection I can't do it remotely - this makes me have to travel to the computer to recover from a reboot. It is on a UPS but even that can only last so long.
            – SDsolar
            Jul 16 '17 at 9:48
















          13














          If you are using Ubuntu 16.x, navigate to /etc/NetworkManager/system-connections/. There you will find a file with the same name as your wireless network. This file contains your wifi credentials and settings. Edit it, find the line with permission=, and remove everything after the = sign (or the whole line).



          Restart and you can connect before login.






          share|improve this answer























          • Additionally, psk-flags=1 means the password is stored encrypted in users home dir. it prob won't work before login in that case. It's less secure, but if you need this to work, you can replace pask-flags=1 with psk=MyWifiPassword. More about that thought: lauri.xn--vsandi-pxa.com/cfgmgmt/…
            – dhaupin
            Apr 14 '17 at 20:37










          • There is nothing after the = sign. And it does not connect until I log in at the console. Since WiFi is my only connection I can't do it remotely - this makes me have to travel to the computer to recover from a reboot. It is on a UPS but even that can only last so long.
            – SDsolar
            Jul 16 '17 at 9:48














          13












          13








          13






          If you are using Ubuntu 16.x, navigate to /etc/NetworkManager/system-connections/. There you will find a file with the same name as your wireless network. This file contains your wifi credentials and settings. Edit it, find the line with permission=, and remove everything after the = sign (or the whole line).



          Restart and you can connect before login.






          share|improve this answer














          If you are using Ubuntu 16.x, navigate to /etc/NetworkManager/system-connections/. There you will find a file with the same name as your wireless network. This file contains your wifi credentials and settings. Edit it, find the line with permission=, and remove everything after the = sign (or the whole line).



          Restart and you can connect before login.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Apr 14 '17 at 20:47









          dhaupin

          1055




          1055










          answered Jul 10 '16 at 10:45









          Александр Лавриненко

          13112




          13112












          • Additionally, psk-flags=1 means the password is stored encrypted in users home dir. it prob won't work before login in that case. It's less secure, but if you need this to work, you can replace pask-flags=1 with psk=MyWifiPassword. More about that thought: lauri.xn--vsandi-pxa.com/cfgmgmt/…
            – dhaupin
            Apr 14 '17 at 20:37










          • There is nothing after the = sign. And it does not connect until I log in at the console. Since WiFi is my only connection I can't do it remotely - this makes me have to travel to the computer to recover from a reboot. It is on a UPS but even that can only last so long.
            – SDsolar
            Jul 16 '17 at 9:48


















          • Additionally, psk-flags=1 means the password is stored encrypted in users home dir. it prob won't work before login in that case. It's less secure, but if you need this to work, you can replace pask-flags=1 with psk=MyWifiPassword. More about that thought: lauri.xn--vsandi-pxa.com/cfgmgmt/…
            – dhaupin
            Apr 14 '17 at 20:37










          • There is nothing after the = sign. And it does not connect until I log in at the console. Since WiFi is my only connection I can't do it remotely - this makes me have to travel to the computer to recover from a reboot. It is on a UPS but even that can only last so long.
            – SDsolar
            Jul 16 '17 at 9:48
















          Additionally, psk-flags=1 means the password is stored encrypted in users home dir. it prob won't work before login in that case. It's less secure, but if you need this to work, you can replace pask-flags=1 with psk=MyWifiPassword. More about that thought: lauri.xn--vsandi-pxa.com/cfgmgmt/…
          – dhaupin
          Apr 14 '17 at 20:37




          Additionally, psk-flags=1 means the password is stored encrypted in users home dir. it prob won't work before login in that case. It's less secure, but if you need this to work, you can replace pask-flags=1 with psk=MyWifiPassword. More about that thought: lauri.xn--vsandi-pxa.com/cfgmgmt/…
          – dhaupin
          Apr 14 '17 at 20:37












          There is nothing after the = sign. And it does not connect until I log in at the console. Since WiFi is my only connection I can't do it remotely - this makes me have to travel to the computer to recover from a reboot. It is on a UPS but even that can only last so long.
          – SDsolar
          Jul 16 '17 at 9:48




          There is nothing after the = sign. And it does not connect until I log in at the console. Since WiFi is my only connection I can't do it remotely - this makes me have to travel to the computer to recover from a reboot. It is on a UPS but even that can only last so long.
          – SDsolar
          Jul 16 '17 at 9:48











          2














          dhaupin's solution solved my problem with minor modifications:



          My /etc/NetworkManager/system-connections/ file did not have a permission= line. But it did have a psk-flags=1 line. Commenting it out and adding a psk="MyWifiPassword" line fixed the Network-Mangler problem.



          Rebooted and it came up online without logging in.






          share|improve this answer























          • I already had the psk=Mypassword" line and it still doesn't do it.
            – SDsolar
            Jul 16 '17 at 9:49
















          2














          dhaupin's solution solved my problem with minor modifications:



          My /etc/NetworkManager/system-connections/ file did not have a permission= line. But it did have a psk-flags=1 line. Commenting it out and adding a psk="MyWifiPassword" line fixed the Network-Mangler problem.



          Rebooted and it came up online without logging in.






          share|improve this answer























          • I already had the psk=Mypassword" line and it still doesn't do it.
            – SDsolar
            Jul 16 '17 at 9:49














          2












          2








          2






          dhaupin's solution solved my problem with minor modifications:



          My /etc/NetworkManager/system-connections/ file did not have a permission= line. But it did have a psk-flags=1 line. Commenting it out and adding a psk="MyWifiPassword" line fixed the Network-Mangler problem.



          Rebooted and it came up online without logging in.






          share|improve this answer














          dhaupin's solution solved my problem with minor modifications:



          My /etc/NetworkManager/system-connections/ file did not have a permission= line. But it did have a psk-flags=1 line. Commenting it out and adding a psk="MyWifiPassword" line fixed the Network-Mangler problem.



          Rebooted and it came up online without logging in.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jun 13 '17 at 5:14









          Zanna

          50k13131238




          50k13131238










          answered Jun 13 '17 at 3:08









          another anon user

          211




          211












          • I already had the psk=Mypassword" line and it still doesn't do it.
            – SDsolar
            Jul 16 '17 at 9:49


















          • I already had the psk=Mypassword" line and it still doesn't do it.
            – SDsolar
            Jul 16 '17 at 9:49
















          I already had the psk=Mypassword" line and it still doesn't do it.
          – SDsolar
          Jul 16 '17 at 9:49




          I already had the psk=Mypassword" line and it still doesn't do it.
          – SDsolar
          Jul 16 '17 at 9:49











          1














          Edit the interfaces file /etc/network/interfaces



          sudo -H gedit /etc/network/interfaces


          Add the following,



          auto ra0
          
iface ra0 inet dhcp
          
wpa-conf /etc/wpa_supplicant.conf





          share|improve this answer























          • Is there a technical difference between the way I did it (see my answer) and yours?
            – Olivier Lalonde
            Dec 6 '10 at 4:07










          • Olivier, I think your solution is more up-to-date, depending as it does on a relatively new feature of NetworkManager. Kathick's solution, on the other hand, circumvents NetworkManager altogether. Your solution might be more robust as NetworkManager keeps track of the connection and reconncects if it is lost temporarily (although the interfaces way might do that too in some cases).
            – loevborg
            Dec 6 '10 at 15:15










          • I hate to mess with that file, plus this computer is alreayd entered into the hosts file of all the other computers as a static IP. wpa_supplicant is fine. And yet it still doesn't do it.
            – SDsolar
            Jul 16 '17 at 9:50


















          1














          Edit the interfaces file /etc/network/interfaces



          sudo -H gedit /etc/network/interfaces


          Add the following,



          auto ra0
          
iface ra0 inet dhcp
          
wpa-conf /etc/wpa_supplicant.conf





          share|improve this answer























          • Is there a technical difference between the way I did it (see my answer) and yours?
            – Olivier Lalonde
            Dec 6 '10 at 4:07










          • Olivier, I think your solution is more up-to-date, depending as it does on a relatively new feature of NetworkManager. Kathick's solution, on the other hand, circumvents NetworkManager altogether. Your solution might be more robust as NetworkManager keeps track of the connection and reconncects if it is lost temporarily (although the interfaces way might do that too in some cases).
            – loevborg
            Dec 6 '10 at 15:15










          • I hate to mess with that file, plus this computer is alreayd entered into the hosts file of all the other computers as a static IP. wpa_supplicant is fine. And yet it still doesn't do it.
            – SDsolar
            Jul 16 '17 at 9:50
















          1












          1








          1






          Edit the interfaces file /etc/network/interfaces



          sudo -H gedit /etc/network/interfaces


          Add the following,



          auto ra0
          
iface ra0 inet dhcp
          
wpa-conf /etc/wpa_supplicant.conf





          share|improve this answer














          Edit the interfaces file /etc/network/interfaces



          sudo -H gedit /etc/network/interfaces


          Add the following,



          auto ra0
          
iface ra0 inet dhcp
          
wpa-conf /etc/wpa_supplicant.conf






          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Dec 24 at 15:37









          Zanna

          50k13131238




          50k13131238










          answered Dec 6 '10 at 4:05









          karthick87

          47.5k53166217




          47.5k53166217












          • Is there a technical difference between the way I did it (see my answer) and yours?
            – Olivier Lalonde
            Dec 6 '10 at 4:07










          • Olivier, I think your solution is more up-to-date, depending as it does on a relatively new feature of NetworkManager. Kathick's solution, on the other hand, circumvents NetworkManager altogether. Your solution might be more robust as NetworkManager keeps track of the connection and reconncects if it is lost temporarily (although the interfaces way might do that too in some cases).
            – loevborg
            Dec 6 '10 at 15:15










          • I hate to mess with that file, plus this computer is alreayd entered into the hosts file of all the other computers as a static IP. wpa_supplicant is fine. And yet it still doesn't do it.
            – SDsolar
            Jul 16 '17 at 9:50




















          • Is there a technical difference between the way I did it (see my answer) and yours?
            – Olivier Lalonde
            Dec 6 '10 at 4:07










          • Olivier, I think your solution is more up-to-date, depending as it does on a relatively new feature of NetworkManager. Kathick's solution, on the other hand, circumvents NetworkManager altogether. Your solution might be more robust as NetworkManager keeps track of the connection and reconncects if it is lost temporarily (although the interfaces way might do that too in some cases).
            – loevborg
            Dec 6 '10 at 15:15










          • I hate to mess with that file, plus this computer is alreayd entered into the hosts file of all the other computers as a static IP. wpa_supplicant is fine. And yet it still doesn't do it.
            – SDsolar
            Jul 16 '17 at 9:50


















          Is there a technical difference between the way I did it (see my answer) and yours?
          – Olivier Lalonde
          Dec 6 '10 at 4:07




          Is there a technical difference between the way I did it (see my answer) and yours?
          – Olivier Lalonde
          Dec 6 '10 at 4:07












          Olivier, I think your solution is more up-to-date, depending as it does on a relatively new feature of NetworkManager. Kathick's solution, on the other hand, circumvents NetworkManager altogether. Your solution might be more robust as NetworkManager keeps track of the connection and reconncects if it is lost temporarily (although the interfaces way might do that too in some cases).
          – loevborg
          Dec 6 '10 at 15:15




          Olivier, I think your solution is more up-to-date, depending as it does on a relatively new feature of NetworkManager. Kathick's solution, on the other hand, circumvents NetworkManager altogether. Your solution might be more robust as NetworkManager keeps track of the connection and reconncects if it is lost temporarily (although the interfaces way might do that too in some cases).
          – loevborg
          Dec 6 '10 at 15:15












          I hate to mess with that file, plus this computer is alreayd entered into the hosts file of all the other computers as a static IP. wpa_supplicant is fine. And yet it still doesn't do it.
          – SDsolar
          Jul 16 '17 at 9:50






          I hate to mess with that file, plus this computer is alreayd entered into the hosts file of all the other computers as a static IP. wpa_supplicant is fine. And yet it still doesn't do it.
          – SDsolar
          Jul 16 '17 at 9:50




















          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.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • 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%2f16376%2fconnect-to-network-before-user-login%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

          Category:香港粉麵

          更多信息，请参阅 香港粉麵 。 此分類包括香港常見的麵條類食品，粉麵類型請放於Category:面条分類 This page is only for reference, If you need detailed information, please check here
          Read more

          List *all* the tuples!

          Image
          27 4 $begingroup$ Write a program, given an input n , will generate all possible n-tuples using natural numbers. n=1 (1),(2),(3),(4),(5),(6)... n=2 (1,1),(1,2),(2,1),(2,2),(1,3),(3,1),(2,3),(3,2),(3,3)... n=6 (1,1,1,1,1,1) (1,1,1,1,2,1) (1,1,1,2,1,1)... The output may be in any order that does not break any other rules. The program must be written to run forever and list all applicable tuples exactly once, in theory. In reality, your program will reach your integer type's limit and crash. This is acceptable as long the program would run infinitely long if only your integer type was unlimited. Each valid tuple must be listed within finite time, if only the program were allowed to run that long. The output may, at your option, include zeroes in addition to the natural numbers. You may choos...
          Read more

          Channel [V]

          Image
            本文介紹的是國際性音樂電視頻道Channel [V]的主條目。關於在臺灣地區前稱Channel [V]的子電視頻道，請見「 FOX (台灣頻道) 」。 body.skin-minerva .mw-parser-output table.infobox caption{text-align:center} Channel [V] Channel [V] 所有者 星空傳媒 福斯傳媒集團 星空華文傳媒（中国大陆频道） 开播日期 1991年9月15日 口号 全球最強華語音樂頻道；亞洲第一音樂頻道 播出地区 亞洲各地 旧称 衛視音樂台 取代者 [V] by FOX (東南亞和中東國家版本) 姊妹频道 星空衛視 收看方法 有线电视   澳門澳門有線電視 [V]國際頻道：73頻道 [V]中國頻道：74頻道   中国深圳天威视讯 [V]中國頻道：尚未定頻   中国南京数字电视 [V]中國頻道：91頻道   中国中国大陸数字电视 [V]中國頻道：随地区而变 宽带电视   香港now寬頻電視 [V]國際頻道：534頻道 臺灣中華電信MOD [V]國際娛樂頻道HD：151頻道   新加坡Mio TV [V]國際娛樂頻道HD：352頻道 [V]中國頻道：547頻道 Channel [V] 是一個國際性的音樂電視頻道，隸屬於星空傳媒，在東亞、東南亞、南亞、中東地區等地多個國家播放。該頻道主要播放英文主流音樂和一些區域性語言的歌曲，其中在台灣與中國大陸主要播放華語流行音樂。2010年8月星空傳媒把中国大陆頻道控股權易手予上海市人民政府牽頭成立的華人文化產業投資基金 [1] 。 目录 1 V的含義 2 Channel [V]國際頻道 3 Channel [V]臺灣頻道 4 Channel [V]中國頻道 5 其它的Channel [V]頻道 6 参见 7 參考資料 8 外部链接 V的含義 官方並無提供字母 V 的確切含義，以下是流傳的說法： 最廣泛的說法是V代表胜利（victory）...
          Read more