18.04 NIC bonding ethernet + wifi












0














I've the following interfaces file:



# The loopback network interface 
auto lo
iface lo inet loopback

#auto bond0
allow-hotplug bond0
iface bond0 inet static
address 192.168.100.10
gateway 192.168.100.1
netmask 255.255.255.0
dns-nameservers 8.8.8.8 8.8.4.4
bond-mode active-backup
bond-slaves enp3s0 wlp2s0
bond-primary enp3s0
bond-miimon 100

# enp3s0 is manually configured, and slave to the "bond0" bonded NIC
auto enp3s0
iface enp3s0 inet manual
bond-master bond0
bond-primary enp3s0

# wlp2s0 is manually configured, and slave to the "bond0" bonded NIC
allow-hotplug wlp2s0
iface wlp2s0 inet manual
bond-master bond0
bond-give-a-chance 10
wpa-bridge bond0
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf


This works to some extent. The problem is with DNS. For the ethernet nic, dns is working. But if I switch over to wifi, resolv.conf is empty and I have to manually populate it.



Help appreciated!










share|improve this question





























    0














    I've the following interfaces file:



    # The loopback network interface 
    auto lo
    iface lo inet loopback

    #auto bond0
    allow-hotplug bond0
    iface bond0 inet static
    address 192.168.100.10
    gateway 192.168.100.1
    netmask 255.255.255.0
    dns-nameservers 8.8.8.8 8.8.4.4
    bond-mode active-backup
    bond-slaves enp3s0 wlp2s0
    bond-primary enp3s0
    bond-miimon 100

    # enp3s0 is manually configured, and slave to the "bond0" bonded NIC
    auto enp3s0
    iface enp3s0 inet manual
    bond-master bond0
    bond-primary enp3s0

    # wlp2s0 is manually configured, and slave to the "bond0" bonded NIC
    allow-hotplug wlp2s0
    iface wlp2s0 inet manual
    bond-master bond0
    bond-give-a-chance 10
    wpa-bridge bond0
    wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf


    This works to some extent. The problem is with DNS. For the ethernet nic, dns is working. But if I switch over to wifi, resolv.conf is empty and I have to manually populate it.



    Help appreciated!










    share|improve this question



























      0












      0








      0







      I've the following interfaces file:



      # The loopback network interface 
      auto lo
      iface lo inet loopback

      #auto bond0
      allow-hotplug bond0
      iface bond0 inet static
      address 192.168.100.10
      gateway 192.168.100.1
      netmask 255.255.255.0
      dns-nameservers 8.8.8.8 8.8.4.4
      bond-mode active-backup
      bond-slaves enp3s0 wlp2s0
      bond-primary enp3s0
      bond-miimon 100

      # enp3s0 is manually configured, and slave to the "bond0" bonded NIC
      auto enp3s0
      iface enp3s0 inet manual
      bond-master bond0
      bond-primary enp3s0

      # wlp2s0 is manually configured, and slave to the "bond0" bonded NIC
      allow-hotplug wlp2s0
      iface wlp2s0 inet manual
      bond-master bond0
      bond-give-a-chance 10
      wpa-bridge bond0
      wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf


      This works to some extent. The problem is with DNS. For the ethernet nic, dns is working. But if I switch over to wifi, resolv.conf is empty and I have to manually populate it.



      Help appreciated!










      share|improve this question















      I've the following interfaces file:



      # The loopback network interface 
      auto lo
      iface lo inet loopback

      #auto bond0
      allow-hotplug bond0
      iface bond0 inet static
      address 192.168.100.10
      gateway 192.168.100.1
      netmask 255.255.255.0
      dns-nameservers 8.8.8.8 8.8.4.4
      bond-mode active-backup
      bond-slaves enp3s0 wlp2s0
      bond-primary enp3s0
      bond-miimon 100

      # enp3s0 is manually configured, and slave to the "bond0" bonded NIC
      auto enp3s0
      iface enp3s0 inet manual
      bond-master bond0
      bond-primary enp3s0

      # wlp2s0 is manually configured, and slave to the "bond0" bonded NIC
      allow-hotplug wlp2s0
      iface wlp2s0 inet manual
      bond-master bond0
      bond-give-a-chance 10
      wpa-bridge bond0
      wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf


      This works to some extent. The problem is with DNS. For the ethernet nic, dns is working. But if I switch over to wifi, resolv.conf is empty and I have to manually populate it.



      Help appreciated!







      network-bonding






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jun 18 at 10:32

























      asked Jun 15 at 15:41









      YMOZ

      165




      165






















          1 Answer
          1






          active

          oldest

          votes


















          0














          That is the price you pay for tweaking such mundane things especially when you probably do not need it in the first place. However, NIC teaming does provide advantages and some disadvantages). Perhaps you can just write a bash file to save you time when switching to bed mode ;)






          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%2f1046901%2f18-04-nic-bonding-ethernet-wifi%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









            0














            That is the price you pay for tweaking such mundane things especially when you probably do not need it in the first place. However, NIC teaming does provide advantages and some disadvantages). Perhaps you can just write a bash file to save you time when switching to bed mode ;)






            share|improve this answer


























              0














              That is the price you pay for tweaking such mundane things especially when you probably do not need it in the first place. However, NIC teaming does provide advantages and some disadvantages). Perhaps you can just write a bash file to save you time when switching to bed mode ;)






              share|improve this answer
























                0












                0








                0






                That is the price you pay for tweaking such mundane things especially when you probably do not need it in the first place. However, NIC teaming does provide advantages and some disadvantages). Perhaps you can just write a bash file to save you time when switching to bed mode ;)






                share|improve this answer












                That is the price you pay for tweaking such mundane things especially when you probably do not need it in the first place. However, NIC teaming does provide advantages and some disadvantages). Perhaps you can just write a bash file to save you time when switching to bed mode ;)







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Dec 17 at 3:04









                Arrrstin

                92




                92






























                    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%2f1046901%2f18-04-nic-bonding-ethernet-wifi%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