IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready












1















I am trying to go live in Kali Linux 2018.3 but whenever I try to do so, it gets stuck at



IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready 
IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready


although in console,



ifconfig 


detects wlan0 with no issues.
Earlier I used 2016.2 and didn't have the problem Please help.



NIC -



Intel(R) Dual Band Wireless-AC 8260









share|improve this question

























  • What exactly have you tried? Your question implies you can't boot, but then you say you have Kali console access. I believe 2018.4 has been released, you could try loading that iso on your USB and try it, or take a look at: kali.training/downloads/Kali-Linux-Revealed-1st-edition.pdf, this guide is for beginners to experts. I would suggest taking the time to make your own customized Kali images, it's slightly harder to get going initially, but well worth it. (You can also ensure compatibility for the devices you personally own)

    – Tim_Stewart
    Feb 10 at 18:06











  • What I am trying to say is that booting gets stuck and these lines show up. Now when I press ALT+F2, it gives me the console. And yes, I tried the 2018.4. Had no luck

    – DeshBhakt
    Feb 11 at 19:40











  • Please answer my question.

    – DeshBhakt
    Feb 16 at 18:04











  • unix.stackexchange.com/questions/399626/…

    – Tim_Stewart
    Feb 16 at 19:20











  • I was helping you get enough info in your question to not have it closed. And hopefully enough info for someone to be able to adequately answer your question. Read the PDF guy, it's worth it.

    – Tim_Stewart
    Feb 16 at 19:22
















1















I am trying to go live in Kali Linux 2018.3 but whenever I try to do so, it gets stuck at



IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready 
IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready


although in console,



ifconfig 


detects wlan0 with no issues.
Earlier I used 2016.2 and didn't have the problem Please help.



NIC -



Intel(R) Dual Band Wireless-AC 8260









share|improve this question

























  • What exactly have you tried? Your question implies you can't boot, but then you say you have Kali console access. I believe 2018.4 has been released, you could try loading that iso on your USB and try it, or take a look at: kali.training/downloads/Kali-Linux-Revealed-1st-edition.pdf, this guide is for beginners to experts. I would suggest taking the time to make your own customized Kali images, it's slightly harder to get going initially, but well worth it. (You can also ensure compatibility for the devices you personally own)

    – Tim_Stewart
    Feb 10 at 18:06











  • What I am trying to say is that booting gets stuck and these lines show up. Now when I press ALT+F2, it gives me the console. And yes, I tried the 2018.4. Had no luck

    – DeshBhakt
    Feb 11 at 19:40











  • Please answer my question.

    – DeshBhakt
    Feb 16 at 18:04











  • unix.stackexchange.com/questions/399626/…

    – Tim_Stewart
    Feb 16 at 19:20











  • I was helping you get enough info in your question to not have it closed. And hopefully enough info for someone to be able to adequately answer your question. Read the PDF guy, it's worth it.

    – Tim_Stewart
    Feb 16 at 19:22














1












1








1








I am trying to go live in Kali Linux 2018.3 but whenever I try to do so, it gets stuck at



IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready 
IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready


although in console,



ifconfig 


detects wlan0 with no issues.
Earlier I used 2016.2 and didn't have the problem Please help.



NIC -



Intel(R) Dual Band Wireless-AC 8260









share|improve this question
















I am trying to go live in Kali Linux 2018.3 but whenever I try to do so, it gets stuck at



IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready 
IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready


although in console,



ifconfig 


detects wlan0 with no issues.
Earlier I used 2016.2 and didn't have the problem Please help.



NIC -



Intel(R) Dual Band Wireless-AC 8260






linux wireless-networking kali-linux






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 2 at 4:07









jww

4,4182479147




4,4182479147










asked Feb 9 at 16:31









DeshBhaktDeshBhakt

18117




18117













  • What exactly have you tried? Your question implies you can't boot, but then you say you have Kali console access. I believe 2018.4 has been released, you could try loading that iso on your USB and try it, or take a look at: kali.training/downloads/Kali-Linux-Revealed-1st-edition.pdf, this guide is for beginners to experts. I would suggest taking the time to make your own customized Kali images, it's slightly harder to get going initially, but well worth it. (You can also ensure compatibility for the devices you personally own)

    – Tim_Stewart
    Feb 10 at 18:06











  • What I am trying to say is that booting gets stuck and these lines show up. Now when I press ALT+F2, it gives me the console. And yes, I tried the 2018.4. Had no luck

    – DeshBhakt
    Feb 11 at 19:40











  • Please answer my question.

    – DeshBhakt
    Feb 16 at 18:04











  • unix.stackexchange.com/questions/399626/…

    – Tim_Stewart
    Feb 16 at 19:20











  • I was helping you get enough info in your question to not have it closed. And hopefully enough info for someone to be able to adequately answer your question. Read the PDF guy, it's worth it.

    – Tim_Stewart
    Feb 16 at 19:22



















  • What exactly have you tried? Your question implies you can't boot, but then you say you have Kali console access. I believe 2018.4 has been released, you could try loading that iso on your USB and try it, or take a look at: kali.training/downloads/Kali-Linux-Revealed-1st-edition.pdf, this guide is for beginners to experts. I would suggest taking the time to make your own customized Kali images, it's slightly harder to get going initially, but well worth it. (You can also ensure compatibility for the devices you personally own)

    – Tim_Stewart
    Feb 10 at 18:06











  • What I am trying to say is that booting gets stuck and these lines show up. Now when I press ALT+F2, it gives me the console. And yes, I tried the 2018.4. Had no luck

    – DeshBhakt
    Feb 11 at 19:40











  • Please answer my question.

    – DeshBhakt
    Feb 16 at 18:04











  • unix.stackexchange.com/questions/399626/…

    – Tim_Stewart
    Feb 16 at 19:20











  • I was helping you get enough info in your question to not have it closed. And hopefully enough info for someone to be able to adequately answer your question. Read the PDF guy, it's worth it.

    – Tim_Stewart
    Feb 16 at 19:22

















What exactly have you tried? Your question implies you can't boot, but then you say you have Kali console access. I believe 2018.4 has been released, you could try loading that iso on your USB and try it, or take a look at: kali.training/downloads/Kali-Linux-Revealed-1st-edition.pdf, this guide is for beginners to experts. I would suggest taking the time to make your own customized Kali images, it's slightly harder to get going initially, but well worth it. (You can also ensure compatibility for the devices you personally own)

– Tim_Stewart
Feb 10 at 18:06





What exactly have you tried? Your question implies you can't boot, but then you say you have Kali console access. I believe 2018.4 has been released, you could try loading that iso on your USB and try it, or take a look at: kali.training/downloads/Kali-Linux-Revealed-1st-edition.pdf, this guide is for beginners to experts. I would suggest taking the time to make your own customized Kali images, it's slightly harder to get going initially, but well worth it. (You can also ensure compatibility for the devices you personally own)

– Tim_Stewart
Feb 10 at 18:06













What I am trying to say is that booting gets stuck and these lines show up. Now when I press ALT+F2, it gives me the console. And yes, I tried the 2018.4. Had no luck

– DeshBhakt
Feb 11 at 19:40





What I am trying to say is that booting gets stuck and these lines show up. Now when I press ALT+F2, it gives me the console. And yes, I tried the 2018.4. Had no luck

– DeshBhakt
Feb 11 at 19:40













Please answer my question.

– DeshBhakt
Feb 16 at 18:04





Please answer my question.

– DeshBhakt
Feb 16 at 18:04













unix.stackexchange.com/questions/399626/…

– Tim_Stewart
Feb 16 at 19:20





unix.stackexchange.com/questions/399626/…

– Tim_Stewart
Feb 16 at 19:20













I was helping you get enough info in your question to not have it closed. And hopefully enough info for someone to be able to adequately answer your question. Read the PDF guy, it's worth it.

– Tim_Stewart
Feb 16 at 19:22





I was helping you get enough info in your question to not have it closed. And hopefully enough info for someone to be able to adequately answer your question. Read the PDF guy, it's worth it.

– Tim_Stewart
Feb 16 at 19:22










1 Answer
1






active

oldest

votes


















0















... it gets stuck at:



IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

...




You can shutdown the radio with nmcli. nmcli is the network manager command line interface.



nmcli radio wifi off


I use IPv4 wired LAN connection, and I do nothing with Wifi or IPv6. The kicker for me was, an unused radio was killing my LAN connection every half hour. Every half hour I was getting a new IPv4 address, which killed my SSH connection.



We think we tracked it down to RFC 3041, Privacy Extensions for Stateless Address Autoconfiguration in IPv6. I have no idea why Wireless IPv6 was interfering with my Wired IPv4 addresses. But killing the radio solved the problem.



I miss the old days when things just worked.






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%2f1403912%2fipv6-addrconfnetdev-up-wlan0-link-is-not-ready%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















    ... it gets stuck at:



    IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

    IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

    ...




    You can shutdown the radio with nmcli. nmcli is the network manager command line interface.



    nmcli radio wifi off


    I use IPv4 wired LAN connection, and I do nothing with Wifi or IPv6. The kicker for me was, an unused radio was killing my LAN connection every half hour. Every half hour I was getting a new IPv4 address, which killed my SSH connection.



    We think we tracked it down to RFC 3041, Privacy Extensions for Stateless Address Autoconfiguration in IPv6. I have no idea why Wireless IPv6 was interfering with my Wired IPv4 addresses. But killing the radio solved the problem.



    I miss the old days when things just worked.






    share|improve this answer




























      0















      ... it gets stuck at:



      IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

      IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

      ...




      You can shutdown the radio with nmcli. nmcli is the network manager command line interface.



      nmcli radio wifi off


      I use IPv4 wired LAN connection, and I do nothing with Wifi or IPv6. The kicker for me was, an unused radio was killing my LAN connection every half hour. Every half hour I was getting a new IPv4 address, which killed my SSH connection.



      We think we tracked it down to RFC 3041, Privacy Extensions for Stateless Address Autoconfiguration in IPv6. I have no idea why Wireless IPv6 was interfering with my Wired IPv4 addresses. But killing the radio solved the problem.



      I miss the old days when things just worked.






      share|improve this answer


























        0












        0








        0








        ... it gets stuck at:



        IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

        IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

        ...




        You can shutdown the radio with nmcli. nmcli is the network manager command line interface.



        nmcli radio wifi off


        I use IPv4 wired LAN connection, and I do nothing with Wifi or IPv6. The kicker for me was, an unused radio was killing my LAN connection every half hour. Every half hour I was getting a new IPv4 address, which killed my SSH connection.



        We think we tracked it down to RFC 3041, Privacy Extensions for Stateless Address Autoconfiguration in IPv6. I have no idea why Wireless IPv6 was interfering with my Wired IPv4 addresses. But killing the radio solved the problem.



        I miss the old days when things just worked.






        share|improve this answer














        ... it gets stuck at:



        IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

        IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

        ...




        You can shutdown the radio with nmcli. nmcli is the network manager command line interface.



        nmcli radio wifi off


        I use IPv4 wired LAN connection, and I do nothing with Wifi or IPv6. The kicker for me was, an unused radio was killing my LAN connection every half hour. Every half hour I was getting a new IPv4 address, which killed my SSH connection.



        We think we tracked it down to RFC 3041, Privacy Extensions for Stateless Address Autoconfiguration in IPv6. I have no idea why Wireless IPv6 was interfering with my Wired IPv4 addresses. But killing the radio solved the problem.



        I miss the old days when things just worked.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 2 at 4:09









        jwwjww

        4,4182479147




        4,4182479147






























            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%2f1403912%2fipv6-addrconfnetdev-up-wlan0-link-is-not-ready%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 to reconfigure Docker Trusted Registry 2.x.x to use CEPH FS mount instead of NFS and other traditional...

            is 'sed' thread safe

            How to make a Squid Proxy server?