18.04 - does it force netplan or can I still use resolved.conf?











up vote
0
down vote

favorite












I kept getting timeout errors on 18.04 Bionic Beaver, until I switched to OpenDNS using these commands



sudo rm -f /etc/resolv.conf 
sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf
sudo nano /etc/systemd/resolved.conf
# with body
nameserver 208.67.222.222


Should I really be doing this OpenDNS configuration with Netplan? I tried the following but it doesn't work.



# Create a netplan file
sudo vi /etc/netplan/50-cloud-init.yaml


.



# Put this in the body
nameservers:
addresses: [208.67.222.222, 208.67.220.220]


I also tried this syntax in the body to no avail, but maybe it because I'm on wifi and I called out 'ethernet'??? wlo1 is my wifi logical name when I sudo lshw -C network.



network:
ethernet:
wlo1:
nameservers:
addresses: [208.67.222.222, 208.67.220.220]









share|improve this question




















  • 1




    You first have to make a decision to use NetworkManager or netplan. If you connect wi-fi to various wireless networks, then NetworkManager is probably the better choice. Netplan is best used in servers, where the configuration doesn't change much. See netplan.io/examples.
    – heynnema
    Dec 3 at 20:52










  • @heynnema is this NetworkManager? Or is it something else? Please see this image linuxconfig.org/images/…
    – stackinator
    Dec 3 at 21:01






  • 1




    That's NetworkManager. netplan has no GUI... only files in /etc/netplan, and the netplan CLI. However, if you're using NetworkManager, there's still one relevant .yaml file in /etc/netplan.
    – heynnema
    Dec 3 at 21:20












  • @heynnema and correct me if I'm wrong but I'll need to enable NetworkManager for 18.04 in my /etc/netplan file like this: network:n [TAB]version: 2 [TAB]renderer: NetworkManager and then I run netplan generate && netplan apply.
    – stackinator
    Dec 3 at 21:55








  • 1




    That's correct. Indentation is important. See my answer, below, or the examples site that I quoted earlier. Use spaces, not tabs.
    – heynnema
    Dec 3 at 22:58















up vote
0
down vote

favorite












I kept getting timeout errors on 18.04 Bionic Beaver, until I switched to OpenDNS using these commands



sudo rm -f /etc/resolv.conf 
sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf
sudo nano /etc/systemd/resolved.conf
# with body
nameserver 208.67.222.222


Should I really be doing this OpenDNS configuration with Netplan? I tried the following but it doesn't work.



# Create a netplan file
sudo vi /etc/netplan/50-cloud-init.yaml


.



# Put this in the body
nameservers:
addresses: [208.67.222.222, 208.67.220.220]


I also tried this syntax in the body to no avail, but maybe it because I'm on wifi and I called out 'ethernet'??? wlo1 is my wifi logical name when I sudo lshw -C network.



network:
ethernet:
wlo1:
nameservers:
addresses: [208.67.222.222, 208.67.220.220]









share|improve this question




















  • 1




    You first have to make a decision to use NetworkManager or netplan. If you connect wi-fi to various wireless networks, then NetworkManager is probably the better choice. Netplan is best used in servers, where the configuration doesn't change much. See netplan.io/examples.
    – heynnema
    Dec 3 at 20:52










  • @heynnema is this NetworkManager? Or is it something else? Please see this image linuxconfig.org/images/…
    – stackinator
    Dec 3 at 21:01






  • 1




    That's NetworkManager. netplan has no GUI... only files in /etc/netplan, and the netplan CLI. However, if you're using NetworkManager, there's still one relevant .yaml file in /etc/netplan.
    – heynnema
    Dec 3 at 21:20












  • @heynnema and correct me if I'm wrong but I'll need to enable NetworkManager for 18.04 in my /etc/netplan file like this: network:n [TAB]version: 2 [TAB]renderer: NetworkManager and then I run netplan generate && netplan apply.
    – stackinator
    Dec 3 at 21:55








  • 1




    That's correct. Indentation is important. See my answer, below, or the examples site that I quoted earlier. Use spaces, not tabs.
    – heynnema
    Dec 3 at 22:58













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I kept getting timeout errors on 18.04 Bionic Beaver, until I switched to OpenDNS using these commands



sudo rm -f /etc/resolv.conf 
sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf
sudo nano /etc/systemd/resolved.conf
# with body
nameserver 208.67.222.222


Should I really be doing this OpenDNS configuration with Netplan? I tried the following but it doesn't work.



# Create a netplan file
sudo vi /etc/netplan/50-cloud-init.yaml


.



# Put this in the body
nameservers:
addresses: [208.67.222.222, 208.67.220.220]


I also tried this syntax in the body to no avail, but maybe it because I'm on wifi and I called out 'ethernet'??? wlo1 is my wifi logical name when I sudo lshw -C network.



network:
ethernet:
wlo1:
nameservers:
addresses: [208.67.222.222, 208.67.220.220]









share|improve this question















I kept getting timeout errors on 18.04 Bionic Beaver, until I switched to OpenDNS using these commands



sudo rm -f /etc/resolv.conf 
sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf
sudo nano /etc/systemd/resolved.conf
# with body
nameserver 208.67.222.222


Should I really be doing this OpenDNS configuration with Netplan? I tried the following but it doesn't work.



# Create a netplan file
sudo vi /etc/netplan/50-cloud-init.yaml


.



# Put this in the body
nameservers:
addresses: [208.67.222.222, 208.67.220.220]


I also tried this syntax in the body to no avail, but maybe it because I'm on wifi and I called out 'ethernet'??? wlo1 is my wifi logical name when I sudo lshw -C network.



network:
ethernet:
wlo1:
nameservers:
addresses: [208.67.222.222, 208.67.220.220]






networking 18.04 network-manager dns netplan






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 3 at 16:02

























asked Dec 3 at 3:09









stackinator

469214




469214








  • 1




    You first have to make a decision to use NetworkManager or netplan. If you connect wi-fi to various wireless networks, then NetworkManager is probably the better choice. Netplan is best used in servers, where the configuration doesn't change much. See netplan.io/examples.
    – heynnema
    Dec 3 at 20:52










  • @heynnema is this NetworkManager? Or is it something else? Please see this image linuxconfig.org/images/…
    – stackinator
    Dec 3 at 21:01






  • 1




    That's NetworkManager. netplan has no GUI... only files in /etc/netplan, and the netplan CLI. However, if you're using NetworkManager, there's still one relevant .yaml file in /etc/netplan.
    – heynnema
    Dec 3 at 21:20












  • @heynnema and correct me if I'm wrong but I'll need to enable NetworkManager for 18.04 in my /etc/netplan file like this: network:n [TAB]version: 2 [TAB]renderer: NetworkManager and then I run netplan generate && netplan apply.
    – stackinator
    Dec 3 at 21:55








  • 1




    That's correct. Indentation is important. See my answer, below, or the examples site that I quoted earlier. Use spaces, not tabs.
    – heynnema
    Dec 3 at 22:58














  • 1




    You first have to make a decision to use NetworkManager or netplan. If you connect wi-fi to various wireless networks, then NetworkManager is probably the better choice. Netplan is best used in servers, where the configuration doesn't change much. See netplan.io/examples.
    – heynnema
    Dec 3 at 20:52










  • @heynnema is this NetworkManager? Or is it something else? Please see this image linuxconfig.org/images/…
    – stackinator
    Dec 3 at 21:01






  • 1




    That's NetworkManager. netplan has no GUI... only files in /etc/netplan, and the netplan CLI. However, if you're using NetworkManager, there's still one relevant .yaml file in /etc/netplan.
    – heynnema
    Dec 3 at 21:20












  • @heynnema and correct me if I'm wrong but I'll need to enable NetworkManager for 18.04 in my /etc/netplan file like this: network:n [TAB]version: 2 [TAB]renderer: NetworkManager and then I run netplan generate && netplan apply.
    – stackinator
    Dec 3 at 21:55








  • 1




    That's correct. Indentation is important. See my answer, below, or the examples site that I quoted earlier. Use spaces, not tabs.
    – heynnema
    Dec 3 at 22:58








1




1




You first have to make a decision to use NetworkManager or netplan. If you connect wi-fi to various wireless networks, then NetworkManager is probably the better choice. Netplan is best used in servers, where the configuration doesn't change much. See netplan.io/examples.
– heynnema
Dec 3 at 20:52




You first have to make a decision to use NetworkManager or netplan. If you connect wi-fi to various wireless networks, then NetworkManager is probably the better choice. Netplan is best used in servers, where the configuration doesn't change much. See netplan.io/examples.
– heynnema
Dec 3 at 20:52












@heynnema is this NetworkManager? Or is it something else? Please see this image linuxconfig.org/images/…
– stackinator
Dec 3 at 21:01




@heynnema is this NetworkManager? Or is it something else? Please see this image linuxconfig.org/images/…
– stackinator
Dec 3 at 21:01




1




1




That's NetworkManager. netplan has no GUI... only files in /etc/netplan, and the netplan CLI. However, if you're using NetworkManager, there's still one relevant .yaml file in /etc/netplan.
– heynnema
Dec 3 at 21:20






That's NetworkManager. netplan has no GUI... only files in /etc/netplan, and the netplan CLI. However, if you're using NetworkManager, there's still one relevant .yaml file in /etc/netplan.
– heynnema
Dec 3 at 21:20














@heynnema and correct me if I'm wrong but I'll need to enable NetworkManager for 18.04 in my /etc/netplan file like this: network:n [TAB]version: 2 [TAB]renderer: NetworkManager and then I run netplan generate && netplan apply.
– stackinator
Dec 3 at 21:55






@heynnema and correct me if I'm wrong but I'll need to enable NetworkManager for 18.04 in my /etc/netplan file like this: network:n [TAB]version: 2 [TAB]renderer: NetworkManager and then I run netplan generate && netplan apply.
– stackinator
Dec 3 at 21:55






1




1




That's correct. Indentation is important. See my answer, below, or the examples site that I quoted earlier. Use spaces, not tabs.
– heynnema
Dec 3 at 22:58




That's correct. Indentation is important. See my answer, below, or the examples site that I quoted earlier. Use spaces, not tabs.
– heynnema
Dec 3 at 22:58










1 Answer
1






active

oldest

votes

















up vote
1
down vote



accepted










You first have to make a decision to use NetworkManager or netplan. If you connect wi-fi to various wireless networks, then NetworkManager is probably the better choice. Netplan is best used in servers, where the configuration doesn't change much. See https://netplan.io/examples.



/etc/netplan .yaml example to enable NetworkManager...





network:
version: 2
renderer: NetworkManager




In terminal...



sudo netplan -debug generate # generate config files



sudo netplan apply # apply the new config



reboot # reboot to confirm network operation






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%2f1098052%2f18-04-does-it-force-netplan-or-can-i-still-use-resolved-conf%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
    1
    down vote



    accepted










    You first have to make a decision to use NetworkManager or netplan. If you connect wi-fi to various wireless networks, then NetworkManager is probably the better choice. Netplan is best used in servers, where the configuration doesn't change much. See https://netplan.io/examples.



    /etc/netplan .yaml example to enable NetworkManager...





    network:
    version: 2
    renderer: NetworkManager




    In terminal...



    sudo netplan -debug generate # generate config files



    sudo netplan apply # apply the new config



    reboot # reboot to confirm network operation






    share|improve this answer



























      up vote
      1
      down vote



      accepted










      You first have to make a decision to use NetworkManager or netplan. If you connect wi-fi to various wireless networks, then NetworkManager is probably the better choice. Netplan is best used in servers, where the configuration doesn't change much. See https://netplan.io/examples.



      /etc/netplan .yaml example to enable NetworkManager...





      network:
      version: 2
      renderer: NetworkManager




      In terminal...



      sudo netplan -debug generate # generate config files



      sudo netplan apply # apply the new config



      reboot # reboot to confirm network operation






      share|improve this answer

























        up vote
        1
        down vote



        accepted







        up vote
        1
        down vote



        accepted






        You first have to make a decision to use NetworkManager or netplan. If you connect wi-fi to various wireless networks, then NetworkManager is probably the better choice. Netplan is best used in servers, where the configuration doesn't change much. See https://netplan.io/examples.



        /etc/netplan .yaml example to enable NetworkManager...





        network:
        version: 2
        renderer: NetworkManager




        In terminal...



        sudo netplan -debug generate # generate config files



        sudo netplan apply # apply the new config



        reboot # reboot to confirm network operation






        share|improve this answer














        You first have to make a decision to use NetworkManager or netplan. If you connect wi-fi to various wireless networks, then NetworkManager is probably the better choice. Netplan is best used in servers, where the configuration doesn't change much. See https://netplan.io/examples.



        /etc/netplan .yaml example to enable NetworkManager...





        network:
        version: 2
        renderer: NetworkManager




        In terminal...



        sudo netplan -debug generate # generate config files



        sudo netplan apply # apply the new config



        reboot # reboot to confirm network operation







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Dec 4 at 14:36

























        answered Dec 3 at 22:53









        heynnema

        17.6k22053




        17.6k22053






























            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%2f1098052%2f18-04-does-it-force-netplan-or-can-i-still-use-resolved-conf%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á

             ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕