14.04 wifi disconnect reason 2












0















Ubuntu 14.04
HW: rt2860 (I'm sure since is my eeepc 1000he) BUT seen from ubuntu as rt2890



lspci:



01:00.0 Network controller: Ralink corp. RT2790 Wireless 802.11n 1T/2R PCIe


module: rt28000pci



It's a wep connection, it connect just for a couple of minutes, then disconnect with reason 2, here just a few lines from dmesg.



[  238.999880] wlan0: authenticate with e0:91:53:25:0b:f1
[ 239.012788] wlan0: send auth to e0:91:53:25:0b:f1 (try 1/3)
[ 239.019096] wlan0: authenticated
[ 239.019814] rt2800pci 0000:01:00.0 wlan0: disabling HT/VHT due to WEP/TKIP use
[ 239.019836] rt2800pci 0000:01:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
[ 239.019850] rt2800pci 0000:01:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
[ 239.020176] wlan0: associate with e0:91:53:25:0b:f1 (try 1/3)
[ 239.022206] wlan0: RX AssocResp from e0:91:53:25:0b:f1 (capab=0x431 status=0 aid=17)
[ 239.023239] wlan0: associated
[ 239.023345] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 239.063810] wlan0: deauthenticated from e0:91:53:25:0b:f1 (Reason: 2)
[ 240.025701] wlan0: authenticate with e0:91:53:25:0b:f1
[ 240.028223] wlan0: send auth to e0:91:53:25:0b:f1 (try 1/3)
[ 240.032416] wlan0: authenticated


With open networks it works without problems, I'll check with WPA as soon as I can.
Any idea?










share|improve this question














bumped to the homepage by Community 10 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Reason 2 means Previous authentication no longer valid i.e., Client has associated but is not authorised

    – Raphael
    Jun 21 '14 at 18:06











  • @Raphael, great, how can I see what's is going bad? With archlinux it worked, same essid, same wep key (and it's working right now with android)

    – Elwood
    Jun 21 '14 at 18:25











  • Can you see the properties of your WEP wifi connection like is it WEP 128/40 bit OR 128bit?

    – Raphael
    Jun 21 '14 at 18:30













  • Sure, on network-manager profiles is WEP 128/40 on the router is Security : 128 bit WEP

    – Elwood
    Jun 21 '14 at 18:35













  • Then delete all the existing wi-fi connections and create a new one from Network Connections.

    – Raphael
    Jun 21 '14 at 18:37
















0















Ubuntu 14.04
HW: rt2860 (I'm sure since is my eeepc 1000he) BUT seen from ubuntu as rt2890



lspci:



01:00.0 Network controller: Ralink corp. RT2790 Wireless 802.11n 1T/2R PCIe


module: rt28000pci



It's a wep connection, it connect just for a couple of minutes, then disconnect with reason 2, here just a few lines from dmesg.



[  238.999880] wlan0: authenticate with e0:91:53:25:0b:f1
[ 239.012788] wlan0: send auth to e0:91:53:25:0b:f1 (try 1/3)
[ 239.019096] wlan0: authenticated
[ 239.019814] rt2800pci 0000:01:00.0 wlan0: disabling HT/VHT due to WEP/TKIP use
[ 239.019836] rt2800pci 0000:01:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
[ 239.019850] rt2800pci 0000:01:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
[ 239.020176] wlan0: associate with e0:91:53:25:0b:f1 (try 1/3)
[ 239.022206] wlan0: RX AssocResp from e0:91:53:25:0b:f1 (capab=0x431 status=0 aid=17)
[ 239.023239] wlan0: associated
[ 239.023345] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 239.063810] wlan0: deauthenticated from e0:91:53:25:0b:f1 (Reason: 2)
[ 240.025701] wlan0: authenticate with e0:91:53:25:0b:f1
[ 240.028223] wlan0: send auth to e0:91:53:25:0b:f1 (try 1/3)
[ 240.032416] wlan0: authenticated


With open networks it works without problems, I'll check with WPA as soon as I can.
Any idea?










share|improve this question














bumped to the homepage by Community 10 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Reason 2 means Previous authentication no longer valid i.e., Client has associated but is not authorised

    – Raphael
    Jun 21 '14 at 18:06











  • @Raphael, great, how can I see what's is going bad? With archlinux it worked, same essid, same wep key (and it's working right now with android)

    – Elwood
    Jun 21 '14 at 18:25











  • Can you see the properties of your WEP wifi connection like is it WEP 128/40 bit OR 128bit?

    – Raphael
    Jun 21 '14 at 18:30













  • Sure, on network-manager profiles is WEP 128/40 on the router is Security : 128 bit WEP

    – Elwood
    Jun 21 '14 at 18:35













  • Then delete all the existing wi-fi connections and create a new one from Network Connections.

    – Raphael
    Jun 21 '14 at 18:37














0












0








0








Ubuntu 14.04
HW: rt2860 (I'm sure since is my eeepc 1000he) BUT seen from ubuntu as rt2890



lspci:



01:00.0 Network controller: Ralink corp. RT2790 Wireless 802.11n 1T/2R PCIe


module: rt28000pci



It's a wep connection, it connect just for a couple of minutes, then disconnect with reason 2, here just a few lines from dmesg.



[  238.999880] wlan0: authenticate with e0:91:53:25:0b:f1
[ 239.012788] wlan0: send auth to e0:91:53:25:0b:f1 (try 1/3)
[ 239.019096] wlan0: authenticated
[ 239.019814] rt2800pci 0000:01:00.0 wlan0: disabling HT/VHT due to WEP/TKIP use
[ 239.019836] rt2800pci 0000:01:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
[ 239.019850] rt2800pci 0000:01:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
[ 239.020176] wlan0: associate with e0:91:53:25:0b:f1 (try 1/3)
[ 239.022206] wlan0: RX AssocResp from e0:91:53:25:0b:f1 (capab=0x431 status=0 aid=17)
[ 239.023239] wlan0: associated
[ 239.023345] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 239.063810] wlan0: deauthenticated from e0:91:53:25:0b:f1 (Reason: 2)
[ 240.025701] wlan0: authenticate with e0:91:53:25:0b:f1
[ 240.028223] wlan0: send auth to e0:91:53:25:0b:f1 (try 1/3)
[ 240.032416] wlan0: authenticated


With open networks it works without problems, I'll check with WPA as soon as I can.
Any idea?










share|improve this question














Ubuntu 14.04
HW: rt2860 (I'm sure since is my eeepc 1000he) BUT seen from ubuntu as rt2890



lspci:



01:00.0 Network controller: Ralink corp. RT2790 Wireless 802.11n 1T/2R PCIe


module: rt28000pci



It's a wep connection, it connect just for a couple of minutes, then disconnect with reason 2, here just a few lines from dmesg.



[  238.999880] wlan0: authenticate with e0:91:53:25:0b:f1
[ 239.012788] wlan0: send auth to e0:91:53:25:0b:f1 (try 1/3)
[ 239.019096] wlan0: authenticated
[ 239.019814] rt2800pci 0000:01:00.0 wlan0: disabling HT/VHT due to WEP/TKIP use
[ 239.019836] rt2800pci 0000:01:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
[ 239.019850] rt2800pci 0000:01:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
[ 239.020176] wlan0: associate with e0:91:53:25:0b:f1 (try 1/3)
[ 239.022206] wlan0: RX AssocResp from e0:91:53:25:0b:f1 (capab=0x431 status=0 aid=17)
[ 239.023239] wlan0: associated
[ 239.023345] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 239.063810] wlan0: deauthenticated from e0:91:53:25:0b:f1 (Reason: 2)
[ 240.025701] wlan0: authenticate with e0:91:53:25:0b:f1
[ 240.028223] wlan0: send auth to e0:91:53:25:0b:f1 (try 1/3)
[ 240.032416] wlan0: authenticated


With open networks it works without problems, I'll check with WPA as soon as I can.
Any idea?







wireless drivers 14.04 disconnect






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jun 21 '14 at 18:01









ElwoodElwood

611




611





bumped to the homepage by Community 10 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 10 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Reason 2 means Previous authentication no longer valid i.e., Client has associated but is not authorised

    – Raphael
    Jun 21 '14 at 18:06











  • @Raphael, great, how can I see what's is going bad? With archlinux it worked, same essid, same wep key (and it's working right now with android)

    – Elwood
    Jun 21 '14 at 18:25











  • Can you see the properties of your WEP wifi connection like is it WEP 128/40 bit OR 128bit?

    – Raphael
    Jun 21 '14 at 18:30













  • Sure, on network-manager profiles is WEP 128/40 on the router is Security : 128 bit WEP

    – Elwood
    Jun 21 '14 at 18:35













  • Then delete all the existing wi-fi connections and create a new one from Network Connections.

    – Raphael
    Jun 21 '14 at 18:37



















  • Reason 2 means Previous authentication no longer valid i.e., Client has associated but is not authorised

    – Raphael
    Jun 21 '14 at 18:06











  • @Raphael, great, how can I see what's is going bad? With archlinux it worked, same essid, same wep key (and it's working right now with android)

    – Elwood
    Jun 21 '14 at 18:25











  • Can you see the properties of your WEP wifi connection like is it WEP 128/40 bit OR 128bit?

    – Raphael
    Jun 21 '14 at 18:30













  • Sure, on network-manager profiles is WEP 128/40 on the router is Security : 128 bit WEP

    – Elwood
    Jun 21 '14 at 18:35













  • Then delete all the existing wi-fi connections and create a new one from Network Connections.

    – Raphael
    Jun 21 '14 at 18:37

















Reason 2 means Previous authentication no longer valid i.e., Client has associated but is not authorised

– Raphael
Jun 21 '14 at 18:06





Reason 2 means Previous authentication no longer valid i.e., Client has associated but is not authorised

– Raphael
Jun 21 '14 at 18:06













@Raphael, great, how can I see what's is going bad? With archlinux it worked, same essid, same wep key (and it's working right now with android)

– Elwood
Jun 21 '14 at 18:25





@Raphael, great, how can I see what's is going bad? With archlinux it worked, same essid, same wep key (and it's working right now with android)

– Elwood
Jun 21 '14 at 18:25













Can you see the properties of your WEP wifi connection like is it WEP 128/40 bit OR 128bit?

– Raphael
Jun 21 '14 at 18:30







Can you see the properties of your WEP wifi connection like is it WEP 128/40 bit OR 128bit?

– Raphael
Jun 21 '14 at 18:30















Sure, on network-manager profiles is WEP 128/40 on the router is Security : 128 bit WEP

– Elwood
Jun 21 '14 at 18:35







Sure, on network-manager profiles is WEP 128/40 on the router is Security : 128 bit WEP

– Elwood
Jun 21 '14 at 18:35















Then delete all the existing wi-fi connections and create a new one from Network Connections.

– Raphael
Jun 21 '14 at 18:37





Then delete all the existing wi-fi connections and create a new one from Network Connections.

– Raphael
Jun 21 '14 at 18:37










1 Answer
1






active

oldest

votes


















0














Please run the following commands one line at a time and just copy and paste for accuracy:



echo "options rt2800pci nohwcrypt=1" | sudo tee /etc/modprobe.d/rt2800pci.conf
sudo modprobe -rfv rt2800pci
sudo modprobe -v rt2800pci


This command changes encryption from hardware to software and in many cases corrects the issue you are having.



Wep is not very secure and ubuntu will connect to wpa2 (AES) (CCMP) better then any other settings, not mixed mode or especially (TKIP).






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%2f486442%2f14-04-wifi-disconnect-reason-2%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














    Please run the following commands one line at a time and just copy and paste for accuracy:



    echo "options rt2800pci nohwcrypt=1" | sudo tee /etc/modprobe.d/rt2800pci.conf
    sudo modprobe -rfv rt2800pci
    sudo modprobe -v rt2800pci


    This command changes encryption from hardware to software and in many cases corrects the issue you are having.



    Wep is not very secure and ubuntu will connect to wpa2 (AES) (CCMP) better then any other settings, not mixed mode or especially (TKIP).






    share|improve this answer




























      0














      Please run the following commands one line at a time and just copy and paste for accuracy:



      echo "options rt2800pci nohwcrypt=1" | sudo tee /etc/modprobe.d/rt2800pci.conf
      sudo modprobe -rfv rt2800pci
      sudo modprobe -v rt2800pci


      This command changes encryption from hardware to software and in many cases corrects the issue you are having.



      Wep is not very secure and ubuntu will connect to wpa2 (AES) (CCMP) better then any other settings, not mixed mode or especially (TKIP).






      share|improve this answer


























        0












        0








        0







        Please run the following commands one line at a time and just copy and paste for accuracy:



        echo "options rt2800pci nohwcrypt=1" | sudo tee /etc/modprobe.d/rt2800pci.conf
        sudo modprobe -rfv rt2800pci
        sudo modprobe -v rt2800pci


        This command changes encryption from hardware to software and in many cases corrects the issue you are having.



        Wep is not very secure and ubuntu will connect to wpa2 (AES) (CCMP) better then any other settings, not mixed mode or especially (TKIP).






        share|improve this answer













        Please run the following commands one line at a time and just copy and paste for accuracy:



        echo "options rt2800pci nohwcrypt=1" | sudo tee /etc/modprobe.d/rt2800pci.conf
        sudo modprobe -rfv rt2800pci
        sudo modprobe -v rt2800pci


        This command changes encryption from hardware to software and in many cases corrects the issue you are having.



        Wep is not very secure and ubuntu will connect to wpa2 (AES) (CCMP) better then any other settings, not mixed mode or especially (TKIP).







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jun 21 '14 at 21:00









        Wild ManWild Man

        6,55232640




        6,55232640






























            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f486442%2f14-04-wifi-disconnect-reason-2%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

            GameSpot

            connect to host localhost port 22: Connection refused

            Getting a Wifi WPA2 wifi connection