Kali Virtualbox (on macOS) won't connect to internet over NAT











up vote
0
down vote

favorite












I am currently running Kali as a virtualbox on my Mac. I want to have it set up so that the VM can access the internet, as well as being connected to the host OS (so I can connect over SSH, etc.)



Currently, Adapter 2 is host only, and is working fine. I can SSH into Kali from my host OS. Adapter 1 is set up as a NAT, but it is not working and so I cannot connect to the internet.



When I do ping google.com, I get:



ping: google.com: Name or service not known


On Kali I have the following settings in /etc/network/interfaces:



auto lo
iface lo inet loopback

allow-hotplug eth0
iface eth0 inet static
address 10.0.2.15
netmask 255.255.255.0
gateway 10.0.2.2

allow-hotplug eth1
iface eth1 inet static
address 192.168.100.101
netmask 255.255.255.0


eth1 is the Adapter 2 (Host-Only)



Also, the results of route -n are:



result route -n



Does my issue lie in the addresses I have given eth0? Where have I gone wrong?










share|improve this question




























    up vote
    0
    down vote

    favorite












    I am currently running Kali as a virtualbox on my Mac. I want to have it set up so that the VM can access the internet, as well as being connected to the host OS (so I can connect over SSH, etc.)



    Currently, Adapter 2 is host only, and is working fine. I can SSH into Kali from my host OS. Adapter 1 is set up as a NAT, but it is not working and so I cannot connect to the internet.



    When I do ping google.com, I get:



    ping: google.com: Name or service not known


    On Kali I have the following settings in /etc/network/interfaces:



    auto lo
    iface lo inet loopback

    allow-hotplug eth0
    iface eth0 inet static
    address 10.0.2.15
    netmask 255.255.255.0
    gateway 10.0.2.2

    allow-hotplug eth1
    iface eth1 inet static
    address 192.168.100.101
    netmask 255.255.255.0


    eth1 is the Adapter 2 (Host-Only)



    Also, the results of route -n are:



    result route -n



    Does my issue lie in the addresses I have given eth0? Where have I gone wrong?










    share|improve this question


























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I am currently running Kali as a virtualbox on my Mac. I want to have it set up so that the VM can access the internet, as well as being connected to the host OS (so I can connect over SSH, etc.)



      Currently, Adapter 2 is host only, and is working fine. I can SSH into Kali from my host OS. Adapter 1 is set up as a NAT, but it is not working and so I cannot connect to the internet.



      When I do ping google.com, I get:



      ping: google.com: Name or service not known


      On Kali I have the following settings in /etc/network/interfaces:



      auto lo
      iface lo inet loopback

      allow-hotplug eth0
      iface eth0 inet static
      address 10.0.2.15
      netmask 255.255.255.0
      gateway 10.0.2.2

      allow-hotplug eth1
      iface eth1 inet static
      address 192.168.100.101
      netmask 255.255.255.0


      eth1 is the Adapter 2 (Host-Only)



      Also, the results of route -n are:



      result route -n



      Does my issue lie in the addresses I have given eth0? Where have I gone wrong?










      share|improve this question















      I am currently running Kali as a virtualbox on my Mac. I want to have it set up so that the VM can access the internet, as well as being connected to the host OS (so I can connect over SSH, etc.)



      Currently, Adapter 2 is host only, and is working fine. I can SSH into Kali from my host OS. Adapter 1 is set up as a NAT, but it is not working and so I cannot connect to the internet.



      When I do ping google.com, I get:



      ping: google.com: Name or service not known


      On Kali I have the following settings in /etc/network/interfaces:



      auto lo
      iface lo inet loopback

      allow-hotplug eth0
      iface eth0 inet static
      address 10.0.2.15
      netmask 255.255.255.0
      gateway 10.0.2.2

      allow-hotplug eth1
      iface eth1 inet static
      address 192.168.100.101
      netmask 255.255.255.0


      eth1 is the Adapter 2 (Host-Only)



      Also, the results of route -n are:



      result route -n



      Does my issue lie in the addresses I have given eth0? Where have I gone wrong?







      networking macos virtualbox kali-linux






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Dec 1 '17 at 23:33









      flolilolilo

      1,4281520




      1,4281520










      asked Dec 1 '17 at 23:07









      CJWilliams

      12




      12






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          I found your post while looking for an answer to my own question. I believe you’ll need to install the appropriate firmware to connect via wireless. My install prompted that I required some non-free firmware for networking. Perhaps this will help.






          share|improve this answer








          New contributor




          Alpha1Om3ga is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.














          • 1




            (1) Where does the question say anything about wireless? (It’s talking about interfaces eth0 and eth1.) (2) You believe that firmware is the solution to a problem with a virtual machine?
            – Scott
            Nov 15 at 5:28











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          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%2fsuperuser.com%2fquestions%2f1273560%2fkali-virtualbox-on-macos-wont-connect-to-internet-over-nat%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













          I found your post while looking for an answer to my own question. I believe you’ll need to install the appropriate firmware to connect via wireless. My install prompted that I required some non-free firmware for networking. Perhaps this will help.






          share|improve this answer








          New contributor




          Alpha1Om3ga is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.














          • 1




            (1) Where does the question say anything about wireless? (It’s talking about interfaces eth0 and eth1.) (2) You believe that firmware is the solution to a problem with a virtual machine?
            – Scott
            Nov 15 at 5:28















          up vote
          0
          down vote













          I found your post while looking for an answer to my own question. I believe you’ll need to install the appropriate firmware to connect via wireless. My install prompted that I required some non-free firmware for networking. Perhaps this will help.






          share|improve this answer








          New contributor




          Alpha1Om3ga is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.














          • 1




            (1) Where does the question say anything about wireless? (It’s talking about interfaces eth0 and eth1.) (2) You believe that firmware is the solution to a problem with a virtual machine?
            – Scott
            Nov 15 at 5:28













          up vote
          0
          down vote










          up vote
          0
          down vote









          I found your post while looking for an answer to my own question. I believe you’ll need to install the appropriate firmware to connect via wireless. My install prompted that I required some non-free firmware for networking. Perhaps this will help.






          share|improve this answer








          New contributor




          Alpha1Om3ga is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.









          I found your post while looking for an answer to my own question. I believe you’ll need to install the appropriate firmware to connect via wireless. My install prompted that I required some non-free firmware for networking. Perhaps this will help.







          share|improve this answer








          New contributor




          Alpha1Om3ga is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.









          share|improve this answer



          share|improve this answer






          New contributor




          Alpha1Om3ga is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.









          answered Nov 15 at 5:16









          Alpha1Om3ga

          1




          1




          New contributor




          Alpha1Om3ga is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.





          New contributor





          Alpha1Om3ga is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.






          Alpha1Om3ga is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.








          • 1




            (1) Where does the question say anything about wireless? (It’s talking about interfaces eth0 and eth1.) (2) You believe that firmware is the solution to a problem with a virtual machine?
            – Scott
            Nov 15 at 5:28














          • 1




            (1) Where does the question say anything about wireless? (It’s talking about interfaces eth0 and eth1.) (2) You believe that firmware is the solution to a problem with a virtual machine?
            – Scott
            Nov 15 at 5:28








          1




          1




          (1) Where does the question say anything about wireless? (It’s talking about interfaces eth0 and eth1.) (2) You believe that firmware is the solution to a problem with a virtual machine?
          – Scott
          Nov 15 at 5:28




          (1) Where does the question say anything about wireless? (It’s talking about interfaces eth0 and eth1.) (2) You believe that firmware is the solution to a problem with a virtual machine?
          – Scott
          Nov 15 at 5:28


















           

          draft saved


          draft discarded



















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1273560%2fkali-virtualbox-on-macos-wont-connect-to-internet-over-nat%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

          Plaza Victoria

          Puebla de Zaragoza

          Musa