network doesn't work after adding second interface to netplan











up vote
1
down vote

favorite












I have a fresh install of Ubuntu 18.04.1 server. When I configure netplan with just my WAN address it starts up fine and I can ping out right away. However; when I add another address to my netplan file and reboot I have to run "netplan apply" before I get any connection. Does anyone have any ideas?



edit: Just discovered that even though I can not ping out on server after reboot, I can how ever ssh into it...



network:  
version: 2
ethernets:
eno1:
renderer: networkd
dhcp4: no
dhcp6: no
addresses: [WAN.190/24]
gateway4: WAN.1
nameservers:
addresses: [24.224.127.143, 24.224.95.205]
enp4s0:
renderer: networkd
dhcp4: no
dhcp6: no
addresses: [172.16.1.14/20]
gateway4: 172.16.1.14
nameservers:
addresses: [24.224.127.143, 24.224.85.205]









share|improve this question
























  • Sounds like you have some odd configuration headaches going on, mind sharing the config? It sounds like if you're adding a second address to the same port it's failing routing, or attempting to apply it on boot it doesn't like it, but we'd need to know more about what you've set up. (My guess is routing is at play because you can't ping out from it)
    – Thomas Ward
    Nov 27 at 19:10












  • edit it to show conf. Sorry, don't know how to show spaces so had to use dashes.
    – tremors
    Nov 27 at 19:33










  • which of the two interfaces is your Internet connection. You can only have one with a gateway, as that sets the default route. I assume the WAN is the Internet one. Remove the gateway4 line from enp4s0, run sudo netplan apply, and see if it works.
    – Thomas Ward
    Nov 27 at 19:39










  • Well that did that trick.
    – tremors
    Nov 27 at 19:48










  • Glad to hear it. I wrote up an answer to summarize the comments.
    – Thomas Ward
    Nov 27 at 21:09















up vote
1
down vote

favorite












I have a fresh install of Ubuntu 18.04.1 server. When I configure netplan with just my WAN address it starts up fine and I can ping out right away. However; when I add another address to my netplan file and reboot I have to run "netplan apply" before I get any connection. Does anyone have any ideas?



edit: Just discovered that even though I can not ping out on server after reboot, I can how ever ssh into it...



network:  
version: 2
ethernets:
eno1:
renderer: networkd
dhcp4: no
dhcp6: no
addresses: [WAN.190/24]
gateway4: WAN.1
nameservers:
addresses: [24.224.127.143, 24.224.95.205]
enp4s0:
renderer: networkd
dhcp4: no
dhcp6: no
addresses: [172.16.1.14/20]
gateway4: 172.16.1.14
nameservers:
addresses: [24.224.127.143, 24.224.85.205]









share|improve this question
























  • Sounds like you have some odd configuration headaches going on, mind sharing the config? It sounds like if you're adding a second address to the same port it's failing routing, or attempting to apply it on boot it doesn't like it, but we'd need to know more about what you've set up. (My guess is routing is at play because you can't ping out from it)
    – Thomas Ward
    Nov 27 at 19:10












  • edit it to show conf. Sorry, don't know how to show spaces so had to use dashes.
    – tremors
    Nov 27 at 19:33










  • which of the two interfaces is your Internet connection. You can only have one with a gateway, as that sets the default route. I assume the WAN is the Internet one. Remove the gateway4 line from enp4s0, run sudo netplan apply, and see if it works.
    – Thomas Ward
    Nov 27 at 19:39










  • Well that did that trick.
    – tremors
    Nov 27 at 19:48










  • Glad to hear it. I wrote up an answer to summarize the comments.
    – Thomas Ward
    Nov 27 at 21:09













up vote
1
down vote

favorite









up vote
1
down vote

favorite











I have a fresh install of Ubuntu 18.04.1 server. When I configure netplan with just my WAN address it starts up fine and I can ping out right away. However; when I add another address to my netplan file and reboot I have to run "netplan apply" before I get any connection. Does anyone have any ideas?



edit: Just discovered that even though I can not ping out on server after reboot, I can how ever ssh into it...



network:  
version: 2
ethernets:
eno1:
renderer: networkd
dhcp4: no
dhcp6: no
addresses: [WAN.190/24]
gateway4: WAN.1
nameservers:
addresses: [24.224.127.143, 24.224.95.205]
enp4s0:
renderer: networkd
dhcp4: no
dhcp6: no
addresses: [172.16.1.14/20]
gateway4: 172.16.1.14
nameservers:
addresses: [24.224.127.143, 24.224.85.205]









share|improve this question















I have a fresh install of Ubuntu 18.04.1 server. When I configure netplan with just my WAN address it starts up fine and I can ping out right away. However; when I add another address to my netplan file and reboot I have to run "netplan apply" before I get any connection. Does anyone have any ideas?



edit: Just discovered that even though I can not ping out on server after reboot, I can how ever ssh into it...



network:  
version: 2
ethernets:
eno1:
renderer: networkd
dhcp4: no
dhcp6: no
addresses: [WAN.190/24]
gateway4: WAN.1
nameservers:
addresses: [24.224.127.143, 24.224.95.205]
enp4s0:
renderer: networkd
dhcp4: no
dhcp6: no
addresses: [172.16.1.14/20]
gateway4: 172.16.1.14
nameservers:
addresses: [24.224.127.143, 24.224.85.205]






networking server netplan






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 5 at 8:57









slangasek

2,37811418




2,37811418










asked Nov 27 at 19:01









tremors

62




62












  • Sounds like you have some odd configuration headaches going on, mind sharing the config? It sounds like if you're adding a second address to the same port it's failing routing, or attempting to apply it on boot it doesn't like it, but we'd need to know more about what you've set up. (My guess is routing is at play because you can't ping out from it)
    – Thomas Ward
    Nov 27 at 19:10












  • edit it to show conf. Sorry, don't know how to show spaces so had to use dashes.
    – tremors
    Nov 27 at 19:33










  • which of the two interfaces is your Internet connection. You can only have one with a gateway, as that sets the default route. I assume the WAN is the Internet one. Remove the gateway4 line from enp4s0, run sudo netplan apply, and see if it works.
    – Thomas Ward
    Nov 27 at 19:39










  • Well that did that trick.
    – tremors
    Nov 27 at 19:48










  • Glad to hear it. I wrote up an answer to summarize the comments.
    – Thomas Ward
    Nov 27 at 21:09


















  • Sounds like you have some odd configuration headaches going on, mind sharing the config? It sounds like if you're adding a second address to the same port it's failing routing, or attempting to apply it on boot it doesn't like it, but we'd need to know more about what you've set up. (My guess is routing is at play because you can't ping out from it)
    – Thomas Ward
    Nov 27 at 19:10












  • edit it to show conf. Sorry, don't know how to show spaces so had to use dashes.
    – tremors
    Nov 27 at 19:33










  • which of the two interfaces is your Internet connection. You can only have one with a gateway, as that sets the default route. I assume the WAN is the Internet one. Remove the gateway4 line from enp4s0, run sudo netplan apply, and see if it works.
    – Thomas Ward
    Nov 27 at 19:39










  • Well that did that trick.
    – tremors
    Nov 27 at 19:48










  • Glad to hear it. I wrote up an answer to summarize the comments.
    – Thomas Ward
    Nov 27 at 21:09
















Sounds like you have some odd configuration headaches going on, mind sharing the config? It sounds like if you're adding a second address to the same port it's failing routing, or attempting to apply it on boot it doesn't like it, but we'd need to know more about what you've set up. (My guess is routing is at play because you can't ping out from it)
– Thomas Ward
Nov 27 at 19:10






Sounds like you have some odd configuration headaches going on, mind sharing the config? It sounds like if you're adding a second address to the same port it's failing routing, or attempting to apply it on boot it doesn't like it, but we'd need to know more about what you've set up. (My guess is routing is at play because you can't ping out from it)
– Thomas Ward
Nov 27 at 19:10














edit it to show conf. Sorry, don't know how to show spaces so had to use dashes.
– tremors
Nov 27 at 19:33




edit it to show conf. Sorry, don't know how to show spaces so had to use dashes.
– tremors
Nov 27 at 19:33












which of the two interfaces is your Internet connection. You can only have one with a gateway, as that sets the default route. I assume the WAN is the Internet one. Remove the gateway4 line from enp4s0, run sudo netplan apply, and see if it works.
– Thomas Ward
Nov 27 at 19:39




which of the two interfaces is your Internet connection. You can only have one with a gateway, as that sets the default route. I assume the WAN is the Internet one. Remove the gateway4 line from enp4s0, run sudo netplan apply, and see if it works.
– Thomas Ward
Nov 27 at 19:39












Well that did that trick.
– tremors
Nov 27 at 19:48




Well that did that trick.
– tremors
Nov 27 at 19:48












Glad to hear it. I wrote up an answer to summarize the comments.
– Thomas Ward
Nov 27 at 21:09




Glad to hear it. I wrote up an answer to summarize the comments.
– Thomas Ward
Nov 27 at 21:09










1 Answer
1






active

oldest

votes

















up vote
0
down vote













The problem is because both your networks have gateways defined, and as such the netplan configuration is a little 'confusing' and will break your default routes to the Internet.



In netplan configurations, doing this will have conflicting 'default' route rules for your Internet traffic.



For network traffic headed out for a specific interface (to/from the Internet, in this case eno1), set the gateway4 field. For all other network adapters, do not define gateway4 (in this case, enp4s0). Then, either sudo netplan apply or reboot the system.



This will solve the routing headaches that you've observed.






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',
    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%2f1096580%2fnetwork-doesnt-work-after-adding-second-interface-to-netplan%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








    up vote
    0
    down vote













    The problem is because both your networks have gateways defined, and as such the netplan configuration is a little 'confusing' and will break your default routes to the Internet.



    In netplan configurations, doing this will have conflicting 'default' route rules for your Internet traffic.



    For network traffic headed out for a specific interface (to/from the Internet, in this case eno1), set the gateway4 field. For all other network adapters, do not define gateway4 (in this case, enp4s0). Then, either sudo netplan apply or reboot the system.



    This will solve the routing headaches that you've observed.






    share|improve this answer

























      up vote
      0
      down vote













      The problem is because both your networks have gateways defined, and as such the netplan configuration is a little 'confusing' and will break your default routes to the Internet.



      In netplan configurations, doing this will have conflicting 'default' route rules for your Internet traffic.



      For network traffic headed out for a specific interface (to/from the Internet, in this case eno1), set the gateway4 field. For all other network adapters, do not define gateway4 (in this case, enp4s0). Then, either sudo netplan apply or reboot the system.



      This will solve the routing headaches that you've observed.






      share|improve this answer























        up vote
        0
        down vote










        up vote
        0
        down vote









        The problem is because both your networks have gateways defined, and as such the netplan configuration is a little 'confusing' and will break your default routes to the Internet.



        In netplan configurations, doing this will have conflicting 'default' route rules for your Internet traffic.



        For network traffic headed out for a specific interface (to/from the Internet, in this case eno1), set the gateway4 field. For all other network adapters, do not define gateway4 (in this case, enp4s0). Then, either sudo netplan apply or reboot the system.



        This will solve the routing headaches that you've observed.






        share|improve this answer












        The problem is because both your networks have gateways defined, and as such the netplan configuration is a little 'confusing' and will break your default routes to the Internet.



        In netplan configurations, doing this will have conflicting 'default' route rules for your Internet traffic.



        For network traffic headed out for a specific interface (to/from the Internet, in this case eno1), set the gateway4 field. For all other network adapters, do not define gateway4 (in this case, enp4s0). Then, either sudo netplan apply or reboot the system.



        This will solve the routing headaches that you've observed.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 27 at 20:10









        Thomas Ward

        43.1k23120170




        43.1k23120170






























            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%2f1096580%2fnetwork-doesnt-work-after-adding-second-interface-to-netplan%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

            flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

            Mangá

            Eduardo VII do Reino Unido