network issue after using macchanger. no internet, no ipv4












0















I used macchanger with these commands:



sudo ifconfig eth0 down
sudo macchanger -r eth0
sudo ifconfig eth0 up


I am using it with virtualbox on a local network, I've never had issue with that before, however now once I do that I lose internet.



the issue goes away when I reboot the machine as the MAC address reset to default. tried to reboot the router also, and my Linux works perfectly fine until I reset its MAC address.



ifconfig shows no ipv4 for eth0, restarting network-manager does not help. either.



Troubleshooting done without success :



Tried different hardware: computer, router and fresh install of
virtualbox and Kali.



Tried to use the older version of virtualbox.



service network-manager restart, macchanger -e -r, dhclient eth0.



Changed /etc/network/interfaces for eth0 with dhcp then for oreth0 static.



Tried different network settings on virtualbox.



Checked the firewall disabled local and gateway.



Reinstalled network-manager.



ping 8.8.8.8 return " this site can't be reached".










share|improve this question













migrated from security.stackexchange.com Jan 21 at 6:32


This question came from our site for information security professionals.














  • 1





    Hey Benjy - More info would help. Is this on a local network behind a home router, corporate network or directly connected to a DOCSIS cable modem? Regardless have you restarted the next hop in the network?

    – Joe M
    Jan 20 at 6:56
















0















I used macchanger with these commands:



sudo ifconfig eth0 down
sudo macchanger -r eth0
sudo ifconfig eth0 up


I am using it with virtualbox on a local network, I've never had issue with that before, however now once I do that I lose internet.



the issue goes away when I reboot the machine as the MAC address reset to default. tried to reboot the router also, and my Linux works perfectly fine until I reset its MAC address.



ifconfig shows no ipv4 for eth0, restarting network-manager does not help. either.



Troubleshooting done without success :



Tried different hardware: computer, router and fresh install of
virtualbox and Kali.



Tried to use the older version of virtualbox.



service network-manager restart, macchanger -e -r, dhclient eth0.



Changed /etc/network/interfaces for eth0 with dhcp then for oreth0 static.



Tried different network settings on virtualbox.



Checked the firewall disabled local and gateway.



Reinstalled network-manager.



ping 8.8.8.8 return " this site can't be reached".










share|improve this question













migrated from security.stackexchange.com Jan 21 at 6:32


This question came from our site for information security professionals.














  • 1





    Hey Benjy - More info would help. Is this on a local network behind a home router, corporate network or directly connected to a DOCSIS cable modem? Regardless have you restarted the next hop in the network?

    – Joe M
    Jan 20 at 6:56














0












0








0








I used macchanger with these commands:



sudo ifconfig eth0 down
sudo macchanger -r eth0
sudo ifconfig eth0 up


I am using it with virtualbox on a local network, I've never had issue with that before, however now once I do that I lose internet.



the issue goes away when I reboot the machine as the MAC address reset to default. tried to reboot the router also, and my Linux works perfectly fine until I reset its MAC address.



ifconfig shows no ipv4 for eth0, restarting network-manager does not help. either.



Troubleshooting done without success :



Tried different hardware: computer, router and fresh install of
virtualbox and Kali.



Tried to use the older version of virtualbox.



service network-manager restart, macchanger -e -r, dhclient eth0.



Changed /etc/network/interfaces for eth0 with dhcp then for oreth0 static.



Tried different network settings on virtualbox.



Checked the firewall disabled local and gateway.



Reinstalled network-manager.



ping 8.8.8.8 return " this site can't be reached".










share|improve this question














I used macchanger with these commands:



sudo ifconfig eth0 down
sudo macchanger -r eth0
sudo ifconfig eth0 up


I am using it with virtualbox on a local network, I've never had issue with that before, however now once I do that I lose internet.



the issue goes away when I reboot the machine as the MAC address reset to default. tried to reboot the router also, and my Linux works perfectly fine until I reset its MAC address.



ifconfig shows no ipv4 for eth0, restarting network-manager does not help. either.



Troubleshooting done without success :



Tried different hardware: computer, router and fresh install of
virtualbox and Kali.



Tried to use the older version of virtualbox.



service network-manager restart, macchanger -e -r, dhclient eth0.



Changed /etc/network/interfaces for eth0 with dhcp then for oreth0 static.



Tried different network settings on virtualbox.



Checked the firewall disabled local and gateway.



Reinstalled network-manager.



ping 8.8.8.8 return " this site can't be reached".







networking ip mac-address dhcp






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 20 at 6:12







Benji











migrated from security.stackexchange.com Jan 21 at 6:32


This question came from our site for information security professionals.









migrated from security.stackexchange.com Jan 21 at 6:32


This question came from our site for information security professionals.










  • 1





    Hey Benjy - More info would help. Is this on a local network behind a home router, corporate network or directly connected to a DOCSIS cable modem? Regardless have you restarted the next hop in the network?

    – Joe M
    Jan 20 at 6:56














  • 1





    Hey Benjy - More info would help. Is this on a local network behind a home router, corporate network or directly connected to a DOCSIS cable modem? Regardless have you restarted the next hop in the network?

    – Joe M
    Jan 20 at 6:56








1




1





Hey Benjy - More info would help. Is this on a local network behind a home router, corporate network or directly connected to a DOCSIS cable modem? Regardless have you restarted the next hop in the network?

– Joe M
Jan 20 at 6:56





Hey Benjy - More info would help. Is this on a local network behind a home router, corporate network or directly connected to a DOCSIS cable modem? Regardless have you restarted the next hop in the network?

– Joe M
Jan 20 at 6:56










3 Answers
3






active

oldest

votes


















1














Try to edit directly on network-manager:

Right click on




Network-Manager -> Edit Connections -> Choose the adapter "wifi or wired" -> ...




...then edit the MAC ADDRESS of the adapter selected.

If it worked, please feedback to us.






share|improve this answer

































    0














    Ideas:




    • If you're fresh install is actually clean from the distro, then it makes me think your wifi password is bad (if on wlan) or you have a wiring/switch/gateway issue.

    • If you're chaining your mac, it makes me think you're on a VM with a virtual switch to your host. Confirm from your host that you have connectivity to the wan. ping 8.8.8.8 or ping 4.2.2.1 to see if you can reach out.

    • Sounds like there may be a layer 2 access control at the gateway/switch. Login if you have creds and confirm that there isn't a mac whitelist in place.

    • Check your local/network firewall. Try disabling the local and/or gateway firewall for a quick second to see if the problem goes away.

    • There could be a packet MTU setting issue, but that is not very likely. Steps to troubleshoot that would be a bit advanced.

    • If you also control the gateway/switch, try resetting them as well. You're clearly willing to blow away your box to fix this, so maybe you'd be willing to reset them as well.

    • Look into which services your flavor of *nix needs for networking. Example: https://theos.in/desktop-linux/tip-that-matters/how-do-i-restart-linux-network-service/. It could be that one of these services was disabled, and needs to be enabled.






    share|improve this answer
























    • Changing the MAC address for purposes of spoofing another user's MAC to bypass certain access controls might be one reason

      – waymobetta
      Jan 20 at 7:28











    • Hence the assumption on line 4...

      – primohacker
      Jan 20 at 7:35











    • OP does not have an IP - that makes half of your suggestions unworkable

      – schroeder
      Jan 20 at 13:56



















    0














    It seems you can't address your NIC through eth0 because of the MAC address is 00:00:00:00:00:00 isn't it ?
    You can't save any configuration for your nic, you can't use it, that's why you have the same problem using a different Linux distribution.
    It's a hardware problem i'm afraid, not software






    share|improve this answer























      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',
      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%2fsuperuser.com%2fquestions%2f1396482%2fnetwork-issue-after-using-macchanger-no-internet-no-ipv4%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown
























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      1














      Try to edit directly on network-manager:

      Right click on




      Network-Manager -> Edit Connections -> Choose the adapter "wifi or wired" -> ...




      ...then edit the MAC ADDRESS of the adapter selected.

      If it worked, please feedback to us.






      share|improve this answer






























        1














        Try to edit directly on network-manager:

        Right click on




        Network-Manager -> Edit Connections -> Choose the adapter "wifi or wired" -> ...




        ...then edit the MAC ADDRESS of the adapter selected.

        If it worked, please feedback to us.






        share|improve this answer




























          1












          1








          1







          Try to edit directly on network-manager:

          Right click on




          Network-Manager -> Edit Connections -> Choose the adapter "wifi or wired" -> ...




          ...then edit the MAC ADDRESS of the adapter selected.

          If it worked, please feedback to us.






          share|improve this answer















          Try to edit directly on network-manager:

          Right click on




          Network-Manager -> Edit Connections -> Choose the adapter "wifi or wired" -> ...




          ...then edit the MAC ADDRESS of the adapter selected.

          If it worked, please feedback to us.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jan 22 at 22:37









          zx485

          943813




          943813










          answered Jan 22 at 16:46









          Mahanb HamanandaMahanb Hamananda

          112




          112

























              0














              Ideas:




              • If you're fresh install is actually clean from the distro, then it makes me think your wifi password is bad (if on wlan) or you have a wiring/switch/gateway issue.

              • If you're chaining your mac, it makes me think you're on a VM with a virtual switch to your host. Confirm from your host that you have connectivity to the wan. ping 8.8.8.8 or ping 4.2.2.1 to see if you can reach out.

              • Sounds like there may be a layer 2 access control at the gateway/switch. Login if you have creds and confirm that there isn't a mac whitelist in place.

              • Check your local/network firewall. Try disabling the local and/or gateway firewall for a quick second to see if the problem goes away.

              • There could be a packet MTU setting issue, but that is not very likely. Steps to troubleshoot that would be a bit advanced.

              • If you also control the gateway/switch, try resetting them as well. You're clearly willing to blow away your box to fix this, so maybe you'd be willing to reset them as well.

              • Look into which services your flavor of *nix needs for networking. Example: https://theos.in/desktop-linux/tip-that-matters/how-do-i-restart-linux-network-service/. It could be that one of these services was disabled, and needs to be enabled.






              share|improve this answer
























              • Changing the MAC address for purposes of spoofing another user's MAC to bypass certain access controls might be one reason

                – waymobetta
                Jan 20 at 7:28











              • Hence the assumption on line 4...

                – primohacker
                Jan 20 at 7:35











              • OP does not have an IP - that makes half of your suggestions unworkable

                – schroeder
                Jan 20 at 13:56
















              0














              Ideas:




              • If you're fresh install is actually clean from the distro, then it makes me think your wifi password is bad (if on wlan) or you have a wiring/switch/gateway issue.

              • If you're chaining your mac, it makes me think you're on a VM with a virtual switch to your host. Confirm from your host that you have connectivity to the wan. ping 8.8.8.8 or ping 4.2.2.1 to see if you can reach out.

              • Sounds like there may be a layer 2 access control at the gateway/switch. Login if you have creds and confirm that there isn't a mac whitelist in place.

              • Check your local/network firewall. Try disabling the local and/or gateway firewall for a quick second to see if the problem goes away.

              • There could be a packet MTU setting issue, but that is not very likely. Steps to troubleshoot that would be a bit advanced.

              • If you also control the gateway/switch, try resetting them as well. You're clearly willing to blow away your box to fix this, so maybe you'd be willing to reset them as well.

              • Look into which services your flavor of *nix needs for networking. Example: https://theos.in/desktop-linux/tip-that-matters/how-do-i-restart-linux-network-service/. It could be that one of these services was disabled, and needs to be enabled.






              share|improve this answer
























              • Changing the MAC address for purposes of spoofing another user's MAC to bypass certain access controls might be one reason

                – waymobetta
                Jan 20 at 7:28











              • Hence the assumption on line 4...

                – primohacker
                Jan 20 at 7:35











              • OP does not have an IP - that makes half of your suggestions unworkable

                – schroeder
                Jan 20 at 13:56














              0












              0








              0







              Ideas:




              • If you're fresh install is actually clean from the distro, then it makes me think your wifi password is bad (if on wlan) or you have a wiring/switch/gateway issue.

              • If you're chaining your mac, it makes me think you're on a VM with a virtual switch to your host. Confirm from your host that you have connectivity to the wan. ping 8.8.8.8 or ping 4.2.2.1 to see if you can reach out.

              • Sounds like there may be a layer 2 access control at the gateway/switch. Login if you have creds and confirm that there isn't a mac whitelist in place.

              • Check your local/network firewall. Try disabling the local and/or gateway firewall for a quick second to see if the problem goes away.

              • There could be a packet MTU setting issue, but that is not very likely. Steps to troubleshoot that would be a bit advanced.

              • If you also control the gateway/switch, try resetting them as well. You're clearly willing to blow away your box to fix this, so maybe you'd be willing to reset them as well.

              • Look into which services your flavor of *nix needs for networking. Example: https://theos.in/desktop-linux/tip-that-matters/how-do-i-restart-linux-network-service/. It could be that one of these services was disabled, and needs to be enabled.






              share|improve this answer













              Ideas:




              • If you're fresh install is actually clean from the distro, then it makes me think your wifi password is bad (if on wlan) or you have a wiring/switch/gateway issue.

              • If you're chaining your mac, it makes me think you're on a VM with a virtual switch to your host. Confirm from your host that you have connectivity to the wan. ping 8.8.8.8 or ping 4.2.2.1 to see if you can reach out.

              • Sounds like there may be a layer 2 access control at the gateway/switch. Login if you have creds and confirm that there isn't a mac whitelist in place.

              • Check your local/network firewall. Try disabling the local and/or gateway firewall for a quick second to see if the problem goes away.

              • There could be a packet MTU setting issue, but that is not very likely. Steps to troubleshoot that would be a bit advanced.

              • If you also control the gateway/switch, try resetting them as well. You're clearly willing to blow away your box to fix this, so maybe you'd be willing to reset them as well.

              • Look into which services your flavor of *nix needs for networking. Example: https://theos.in/desktop-linux/tip-that-matters/how-do-i-restart-linux-network-service/. It could be that one of these services was disabled, and needs to be enabled.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Jan 20 at 7:07









              primohackerprimohacker

              7619




              7619













              • Changing the MAC address for purposes of spoofing another user's MAC to bypass certain access controls might be one reason

                – waymobetta
                Jan 20 at 7:28











              • Hence the assumption on line 4...

                – primohacker
                Jan 20 at 7:35











              • OP does not have an IP - that makes half of your suggestions unworkable

                – schroeder
                Jan 20 at 13:56



















              • Changing the MAC address for purposes of spoofing another user's MAC to bypass certain access controls might be one reason

                – waymobetta
                Jan 20 at 7:28











              • Hence the assumption on line 4...

                – primohacker
                Jan 20 at 7:35











              • OP does not have an IP - that makes half of your suggestions unworkable

                – schroeder
                Jan 20 at 13:56

















              Changing the MAC address for purposes of spoofing another user's MAC to bypass certain access controls might be one reason

              – waymobetta
              Jan 20 at 7:28





              Changing the MAC address for purposes of spoofing another user's MAC to bypass certain access controls might be one reason

              – waymobetta
              Jan 20 at 7:28













              Hence the assumption on line 4...

              – primohacker
              Jan 20 at 7:35





              Hence the assumption on line 4...

              – primohacker
              Jan 20 at 7:35













              OP does not have an IP - that makes half of your suggestions unworkable

              – schroeder
              Jan 20 at 13:56





              OP does not have an IP - that makes half of your suggestions unworkable

              – schroeder
              Jan 20 at 13:56











              0














              It seems you can't address your NIC through eth0 because of the MAC address is 00:00:00:00:00:00 isn't it ?
              You can't save any configuration for your nic, you can't use it, that's why you have the same problem using a different Linux distribution.
              It's a hardware problem i'm afraid, not software






              share|improve this answer




























                0














                It seems you can't address your NIC through eth0 because of the MAC address is 00:00:00:00:00:00 isn't it ?
                You can't save any configuration for your nic, you can't use it, that's why you have the same problem using a different Linux distribution.
                It's a hardware problem i'm afraid, not software






                share|improve this answer


























                  0












                  0








                  0







                  It seems you can't address your NIC through eth0 because of the MAC address is 00:00:00:00:00:00 isn't it ?
                  You can't save any configuration for your nic, you can't use it, that's why you have the same problem using a different Linux distribution.
                  It's a hardware problem i'm afraid, not software






                  share|improve this answer













                  It seems you can't address your NIC through eth0 because of the MAC address is 00:00:00:00:00:00 isn't it ?
                  You can't save any configuration for your nic, you can't use it, that's why you have the same problem using a different Linux distribution.
                  It's a hardware problem i'm afraid, not software







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Jan 20 at 17:26







                  LoryOne





































                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Super User!


                      • 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%2fsuperuser.com%2fquestions%2f1396482%2fnetwork-issue-after-using-macchanger-no-internet-no-ipv4%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

                      How do I know what Microsoft account the skydrive app is syncing to?

                      When does type information flow backwards in C++?

                      Grease: Live!