Ubuntu Server 18.04 waiting for Network at startup although the network is ok












3















I have fresh installation of Ubuntu Server 18.04. Until it is all set up and tested, I want it to be connected to both wired and wifi network.



My /etc/netplan directory contains two files:



01-netcfg.yaml



network:
version: 2
renderer: networkd
wifis:
wlp58s0:
dhcp4: yes
dhcp6: yes
access-points:
"MyNetworkName":
password: "MyPassword"


50-cloud-init.yaml:



network:
ethernets:
eno1:
addresses:
dhcp4: true
optional: true
version: 2


When the server boots up, it stays for 2 minutes on this message:



A start job is running for Wait for Network to be Configured.


While this message is displayed, the server can be pinged over the wired IP, but not over the wifi IP. It can be pinged over the wifi IP right after the 2 minutes of waiting have passed and user prompt is displayed on the connected display.



When I log on, ifconfig shows that both interfaces have initialized fine: both have received their IP addresses from the router, the server is reachable over the network at both IPs.



Here's the output of networkctl list command right after boot:



$ networkctl list
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 eno1 ether routable configured
3 wlp58s0 wlan routable configured


The wifi router is about 2 meters close, the signal is very strong. Since I don't plan to restart the server too much, the problem of waiting is bearable. But I am afraid this could be a symptom of some network configuration that should be fixed before things get bad.










share|improve this question

























  • After boot, what does 'networkctl list' show?

    – slangasek
    May 14 '18 at 3:50











  • @slangasek I added 'networkctl list' output to the post.

    – Passiday
    May 14 '18 at 6:56











  • This shows that in the end the network interfaces were both configured via networkd. I think you should file a bug report (ubuntu-bug systemd) about this issue.

    – slangasek
    May 17 '18 at 3:49











  • Is there any way to know what that happened during that waiting time? For some reason, having the wired connection ready was not enough. It had to have both wired and wireless to proceed. And the exact 2 minutes mark feels kind of non-random.

    – Passiday
    May 18 '18 at 19:05











  • I'm seeing a very similar problem, but I only have wifi. It stalls for two minutes and then starts up, but at that point I have to run sudo netplan try manually to get the wifi to connect. Any ideas?

    – TOB
    Jun 26 '18 at 16:10
















3















I have fresh installation of Ubuntu Server 18.04. Until it is all set up and tested, I want it to be connected to both wired and wifi network.



My /etc/netplan directory contains two files:



01-netcfg.yaml



network:
version: 2
renderer: networkd
wifis:
wlp58s0:
dhcp4: yes
dhcp6: yes
access-points:
"MyNetworkName":
password: "MyPassword"


50-cloud-init.yaml:



network:
ethernets:
eno1:
addresses:
dhcp4: true
optional: true
version: 2


When the server boots up, it stays for 2 minutes on this message:



A start job is running for Wait for Network to be Configured.


While this message is displayed, the server can be pinged over the wired IP, but not over the wifi IP. It can be pinged over the wifi IP right after the 2 minutes of waiting have passed and user prompt is displayed on the connected display.



When I log on, ifconfig shows that both interfaces have initialized fine: both have received their IP addresses from the router, the server is reachable over the network at both IPs.



Here's the output of networkctl list command right after boot:



$ networkctl list
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 eno1 ether routable configured
3 wlp58s0 wlan routable configured


The wifi router is about 2 meters close, the signal is very strong. Since I don't plan to restart the server too much, the problem of waiting is bearable. But I am afraid this could be a symptom of some network configuration that should be fixed before things get bad.










share|improve this question

























  • After boot, what does 'networkctl list' show?

    – slangasek
    May 14 '18 at 3:50











  • @slangasek I added 'networkctl list' output to the post.

    – Passiday
    May 14 '18 at 6:56











  • This shows that in the end the network interfaces were both configured via networkd. I think you should file a bug report (ubuntu-bug systemd) about this issue.

    – slangasek
    May 17 '18 at 3:49











  • Is there any way to know what that happened during that waiting time? For some reason, having the wired connection ready was not enough. It had to have both wired and wireless to proceed. And the exact 2 minutes mark feels kind of non-random.

    – Passiday
    May 18 '18 at 19:05











  • I'm seeing a very similar problem, but I only have wifi. It stalls for two minutes and then starts up, but at that point I have to run sudo netplan try manually to get the wifi to connect. Any ideas?

    – TOB
    Jun 26 '18 at 16:10














3












3








3








I have fresh installation of Ubuntu Server 18.04. Until it is all set up and tested, I want it to be connected to both wired and wifi network.



My /etc/netplan directory contains two files:



01-netcfg.yaml



network:
version: 2
renderer: networkd
wifis:
wlp58s0:
dhcp4: yes
dhcp6: yes
access-points:
"MyNetworkName":
password: "MyPassword"


50-cloud-init.yaml:



network:
ethernets:
eno1:
addresses:
dhcp4: true
optional: true
version: 2


When the server boots up, it stays for 2 minutes on this message:



A start job is running for Wait for Network to be Configured.


While this message is displayed, the server can be pinged over the wired IP, but not over the wifi IP. It can be pinged over the wifi IP right after the 2 minutes of waiting have passed and user prompt is displayed on the connected display.



When I log on, ifconfig shows that both interfaces have initialized fine: both have received their IP addresses from the router, the server is reachable over the network at both IPs.



Here's the output of networkctl list command right after boot:



$ networkctl list
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 eno1 ether routable configured
3 wlp58s0 wlan routable configured


The wifi router is about 2 meters close, the signal is very strong. Since I don't plan to restart the server too much, the problem of waiting is bearable. But I am afraid this could be a symptom of some network configuration that should be fixed before things get bad.










share|improve this question
















I have fresh installation of Ubuntu Server 18.04. Until it is all set up and tested, I want it to be connected to both wired and wifi network.



My /etc/netplan directory contains two files:



01-netcfg.yaml



network:
version: 2
renderer: networkd
wifis:
wlp58s0:
dhcp4: yes
dhcp6: yes
access-points:
"MyNetworkName":
password: "MyPassword"


50-cloud-init.yaml:



network:
ethernets:
eno1:
addresses:
dhcp4: true
optional: true
version: 2


When the server boots up, it stays for 2 minutes on this message:



A start job is running for Wait for Network to be Configured.


While this message is displayed, the server can be pinged over the wired IP, but not over the wifi IP. It can be pinged over the wifi IP right after the 2 minutes of waiting have passed and user prompt is displayed on the connected display.



When I log on, ifconfig shows that both interfaces have initialized fine: both have received their IP addresses from the router, the server is reachable over the network at both IPs.



Here's the output of networkctl list command right after boot:



$ networkctl list
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 eno1 ether routable configured
3 wlp58s0 wlan routable configured


The wifi router is about 2 meters close, the signal is very strong. Since I don't plan to restart the server too much, the problem of waiting is bearable. But I am afraid this could be a symptom of some network configuration that should be fixed before things get bad.







server wireless netplan






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 14 '18 at 6:55







Passiday

















asked May 13 '18 at 21:49









PassidayPassiday

1437




1437













  • After boot, what does 'networkctl list' show?

    – slangasek
    May 14 '18 at 3:50











  • @slangasek I added 'networkctl list' output to the post.

    – Passiday
    May 14 '18 at 6:56











  • This shows that in the end the network interfaces were both configured via networkd. I think you should file a bug report (ubuntu-bug systemd) about this issue.

    – slangasek
    May 17 '18 at 3:49











  • Is there any way to know what that happened during that waiting time? For some reason, having the wired connection ready was not enough. It had to have both wired and wireless to proceed. And the exact 2 minutes mark feels kind of non-random.

    – Passiday
    May 18 '18 at 19:05











  • I'm seeing a very similar problem, but I only have wifi. It stalls for two minutes and then starts up, but at that point I have to run sudo netplan try manually to get the wifi to connect. Any ideas?

    – TOB
    Jun 26 '18 at 16:10



















  • After boot, what does 'networkctl list' show?

    – slangasek
    May 14 '18 at 3:50











  • @slangasek I added 'networkctl list' output to the post.

    – Passiday
    May 14 '18 at 6:56











  • This shows that in the end the network interfaces were both configured via networkd. I think you should file a bug report (ubuntu-bug systemd) about this issue.

    – slangasek
    May 17 '18 at 3:49











  • Is there any way to know what that happened during that waiting time? For some reason, having the wired connection ready was not enough. It had to have both wired and wireless to proceed. And the exact 2 minutes mark feels kind of non-random.

    – Passiday
    May 18 '18 at 19:05











  • I'm seeing a very similar problem, but I only have wifi. It stalls for two minutes and then starts up, but at that point I have to run sudo netplan try manually to get the wifi to connect. Any ideas?

    – TOB
    Jun 26 '18 at 16:10

















After boot, what does 'networkctl list' show?

– slangasek
May 14 '18 at 3:50





After boot, what does 'networkctl list' show?

– slangasek
May 14 '18 at 3:50













@slangasek I added 'networkctl list' output to the post.

– Passiday
May 14 '18 at 6:56





@slangasek I added 'networkctl list' output to the post.

– Passiday
May 14 '18 at 6:56













This shows that in the end the network interfaces were both configured via networkd. I think you should file a bug report (ubuntu-bug systemd) about this issue.

– slangasek
May 17 '18 at 3:49





This shows that in the end the network interfaces were both configured via networkd. I think you should file a bug report (ubuntu-bug systemd) about this issue.

– slangasek
May 17 '18 at 3:49













Is there any way to know what that happened during that waiting time? For some reason, having the wired connection ready was not enough. It had to have both wired and wireless to proceed. And the exact 2 minutes mark feels kind of non-random.

– Passiday
May 18 '18 at 19:05





Is there any way to know what that happened during that waiting time? For some reason, having the wired connection ready was not enough. It had to have both wired and wireless to proceed. And the exact 2 minutes mark feels kind of non-random.

– Passiday
May 18 '18 at 19:05













I'm seeing a very similar problem, but I only have wifi. It stalls for two minutes and then starts up, but at that point I have to run sudo netplan try manually to get the wifi to connect. Any ideas?

– TOB
Jun 26 '18 at 16:10





I'm seeing a very similar problem, but I only have wifi. It stalls for two minutes and then starts up, but at that point I have to run sudo netplan try manually to get the wifi to connect. Any ideas?

– TOB
Jun 26 '18 at 16:10










1 Answer
1






active

oldest

votes


















1














What if you add



  optional: yes


to your wifis/wlp58s0 configuration? I had a similar problem, but only when I booted without wired ethernet. The content of my /etc/netplan/01-netcfg.yaml (my only file in that dir) was



# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
enp0s25:
dhcp4: yes


When I appended



      optional: yes


the problem went away. The man 5 netplan page states that an optional device is not required for booting, and that the default is false.






share|improve this answer























    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%2f1035867%2fubuntu-server-18-04-waiting-for-network-at-startup-although-the-network-is-ok%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    What if you add



      optional: yes


    to your wifis/wlp58s0 configuration? I had a similar problem, but only when I booted without wired ethernet. The content of my /etc/netplan/01-netcfg.yaml (my only file in that dir) was



    # This file describes the network interfaces available on your system
    # For more information, see netplan(5).
    network:
    version: 2
    renderer: networkd
    ethernets:
    enp0s25:
    dhcp4: yes


    When I appended



          optional: yes


    the problem went away. The man 5 netplan page states that an optional device is not required for booting, and that the default is false.






    share|improve this answer




























      1














      What if you add



        optional: yes


      to your wifis/wlp58s0 configuration? I had a similar problem, but only when I booted without wired ethernet. The content of my /etc/netplan/01-netcfg.yaml (my only file in that dir) was



      # This file describes the network interfaces available on your system
      # For more information, see netplan(5).
      network:
      version: 2
      renderer: networkd
      ethernets:
      enp0s25:
      dhcp4: yes


      When I appended



            optional: yes


      the problem went away. The man 5 netplan page states that an optional device is not required for booting, and that the default is false.






      share|improve this answer


























        1












        1








        1







        What if you add



          optional: yes


        to your wifis/wlp58s0 configuration? I had a similar problem, but only when I booted without wired ethernet. The content of my /etc/netplan/01-netcfg.yaml (my only file in that dir) was



        # This file describes the network interfaces available on your system
        # For more information, see netplan(5).
        network:
        version: 2
        renderer: networkd
        ethernets:
        enp0s25:
        dhcp4: yes


        When I appended



              optional: yes


        the problem went away. The man 5 netplan page states that an optional device is not required for booting, and that the default is false.






        share|improve this answer













        What if you add



          optional: yes


        to your wifis/wlp58s0 configuration? I had a similar problem, but only when I booted without wired ethernet. The content of my /etc/netplan/01-netcfg.yaml (my only file in that dir) was



        # This file describes the network interfaces available on your system
        # For more information, see netplan(5).
        network:
        version: 2
        renderer: networkd
        ethernets:
        enp0s25:
        dhcp4: yes


        When I appended



              optional: yes


        the problem went away. The man 5 netplan page states that an optional device is not required for booting, and that the default is false.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Aug 19 '18 at 21:05









        Niclas BörlinNiclas Börlin

        9461716




        9461716






























            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%2f1035867%2fubuntu-server-18-04-waiting-for-network-at-startup-although-the-network-is-ok%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

            數位音樂下載

            When can things happen in Etherscan, such as the picture below?

            格利澤436b