Problems with aircrack-ng











up vote
1
down vote

favorite












I'm trying to crack an wifi, but when i type sudo airmon-ng start wlan0 it shows this:



Found 4 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!

PID Name
463 avahi-daemon
475 avahi-daemon
683 NetworkManager
756 wpa_supplicant

Interface Chipset Driver

wlan0 Broadcom wl - [phy0]mon0: ERROR while getting interface flags: No such device

(monitor mode enabled on mon0)


Then, when I type sudo airodump-ng mon0 for the list with available BSSID it shows this:



sudo airodump-ng mon0
Interface mon0:
ioctl(SIOCGIFINDEX) failed: No such device


What can cause this?



This is my wconfig:



wlan0     IEEE 802.11abg  ESSID:off/any  
Mode:Managed Access Point: Not-Associated
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off

ppp0 no wireless extensions.

lo no wireless extensions.


My OS is 14.10. My Laptop is Aspire 5745G.










share|improve this question
























  • solve this by any chance? i am having the same issue and i kept coming across a blocker of some sort with the options presented in the answer below
    – greenhouse
    Jun 13 '15 at 4:45















up vote
1
down vote

favorite












I'm trying to crack an wifi, but when i type sudo airmon-ng start wlan0 it shows this:



Found 4 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!

PID Name
463 avahi-daemon
475 avahi-daemon
683 NetworkManager
756 wpa_supplicant

Interface Chipset Driver

wlan0 Broadcom wl - [phy0]mon0: ERROR while getting interface flags: No such device

(monitor mode enabled on mon0)


Then, when I type sudo airodump-ng mon0 for the list with available BSSID it shows this:



sudo airodump-ng mon0
Interface mon0:
ioctl(SIOCGIFINDEX) failed: No such device


What can cause this?



This is my wconfig:



wlan0     IEEE 802.11abg  ESSID:off/any  
Mode:Managed Access Point: Not-Associated
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off

ppp0 no wireless extensions.

lo no wireless extensions.


My OS is 14.10. My Laptop is Aspire 5745G.










share|improve this question
























  • solve this by any chance? i am having the same issue and i kept coming across a blocker of some sort with the options presented in the answer below
    – greenhouse
    Jun 13 '15 at 4:45













up vote
1
down vote

favorite









up vote
1
down vote

favorite











I'm trying to crack an wifi, but when i type sudo airmon-ng start wlan0 it shows this:



Found 4 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!

PID Name
463 avahi-daemon
475 avahi-daemon
683 NetworkManager
756 wpa_supplicant

Interface Chipset Driver

wlan0 Broadcom wl - [phy0]mon0: ERROR while getting interface flags: No such device

(monitor mode enabled on mon0)


Then, when I type sudo airodump-ng mon0 for the list with available BSSID it shows this:



sudo airodump-ng mon0
Interface mon0:
ioctl(SIOCGIFINDEX) failed: No such device


What can cause this?



This is my wconfig:



wlan0     IEEE 802.11abg  ESSID:off/any  
Mode:Managed Access Point: Not-Associated
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off

ppp0 no wireless extensions.

lo no wireless extensions.


My OS is 14.10. My Laptop is Aspire 5745G.










share|improve this question















I'm trying to crack an wifi, but when i type sudo airmon-ng start wlan0 it shows this:



Found 4 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!

PID Name
463 avahi-daemon
475 avahi-daemon
683 NetworkManager
756 wpa_supplicant

Interface Chipset Driver

wlan0 Broadcom wl - [phy0]mon0: ERROR while getting interface flags: No such device

(monitor mode enabled on mon0)


Then, when I type sudo airodump-ng mon0 for the list with available BSSID it shows this:



sudo airodump-ng mon0
Interface mon0:
ioctl(SIOCGIFINDEX) failed: No such device


What can cause this?



This is my wconfig:



wlan0     IEEE 802.11abg  ESSID:off/any  
Mode:Managed Access Point: Not-Associated
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off

ppp0 no wireless extensions.

lo no wireless extensions.


My OS is 14.10. My Laptop is Aspire 5745G.







wireless networking broadcom aircrack-ng






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Sep 13 '15 at 12:01









David Foerster

27.4k1363108




27.4k1363108










asked Dec 7 '14 at 20:43









Baragan Marius

6112




6112












  • solve this by any chance? i am having the same issue and i kept coming across a blocker of some sort with the options presented in the answer below
    – greenhouse
    Jun 13 '15 at 4:45


















  • solve this by any chance? i am having the same issue and i kept coming across a blocker of some sort with the options presented in the answer below
    – greenhouse
    Jun 13 '15 at 4:45
















solve this by any chance? i am having the same issue and i kept coming across a blocker of some sort with the options presented in the answer below
– greenhouse
Jun 13 '15 at 4:45




solve this by any chance? i am having the same issue and i kept coming across a blocker of some sort with the options presented in the answer below
– greenhouse
Jun 13 '15 at 4:45










5 Answers
5






active

oldest

votes

















up vote
0
down vote













The first error seems to indicated that Network Manager is already using wlan0 (in addition to wpa_supplicant and the other processes).



You don't have an interface called mon0, so that's why you get the second error.



You should be able to use aircrack if you don't use wifi via Network Manager (you can try stopping network manager and then running the command). Note that if Network Manager is not running, you have to handle the wifi configuration yourself.



You could also try adding a virtual interface to your wireless phy with iw.
To do this, look at the output of "iw phy". My wifi card is phy0, so:



"sudo iw phy phy0 interface add mon0 type monitor"



Then retry the second command.



You can get an idea of what your card supports with "iw phy phy0 info". Again, replace phy0 with the correct argument. Check that it supports monitor mode if you have problems adding a monitor interface.



I noticed you have a broadcom card, so monitor should be supported. You can check your wifi card support here http://wireless.kernel.org/en/users/Drivers






share|improve this answer






























    up vote
    0
    down vote













    type this before use aircrack-ng:



    sudo ifconfig <interface(wlan0)> down


    then use the aircrack-ng
    if not work try this:



    sudo airmon-ng check kill


    then airmon-ng start.............






    share|improve this answer




























      up vote
      0
      down vote













      Was seeing the same error running precompiled binaries on Raspian and ended up building from source to get past it.






      share|improve this answer





















      • While this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference.
        – Kevin Bowen
        Aug 9 '16 at 20:18










      • Thanks for the feedback and I see your point. But anything more detailed is likely to vary by system or configuration, and over time, and would likely cause more frustration than it would benefit the audience.
        – Josh Habdas
        Aug 10 '16 at 23:11


















      up vote
      0
      down vote













      This conflicting behavior comes from network manager.
      If you don't want to use sudo airmon-ng check kill (which totally stop network manager) you can add an exception for your mon0 interface as explained here: aircrack-ng : airmon-ng stop working after updating to 15.04 ( ioctl(SIOCSIWMODE) failed: Device or resource busy )



      1.Open network manger configuration file with root privileges



      sudo gedit /etc/NetworkManager/NetworkManager.conf


      2.Add the following lines at the end of your file to create an exception for your mode monitor interfaces.



      [keyfile]
      unmanaged-devices=interface-name:mon*;


      Once you saved the changes effects are immediate and airmon-ng will be able to handle properly the interface
      Be aware that you are using an outdated version of aircrack-ng (the one from ubuntu repositories I guess)
      I strongly suggest you to install a more recent version (in this case the mode monitor interface will be called wlan0mon and not mon0 anymore)
      Go to aircrack-ng website to download the latest stable release (Aircrack-ng 1.2 RC 4 ): aircrack-ng website






      share|improve this answer






























        up vote
        0
        down vote













        When you type sudo airodump-ng mon0, it appears




        sudo airodump-ng mon0

        Interface mon0:

        ioctl(SIOCGIFINDEX) failed: No such device




        cause you don't have that interface, but you have



        Interface   Chipset     Driver

        wlan0 Broadcom wl - [phy0]mon0: ERROR while getting interface flags: No such device

        (monitor mode enabled on mon0)


        try using sudo airodump-ng wlan0.



        By The Way your output said




        wl - [phy0]mon0: ERROR while getting interface flags: No such device




        cause you have aircrack-ng very old version, Make sure you installed the latest version of aircrack-ng package.



        Your not alone, another Question have same issue with yours.



        Hope this helps.






        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',
          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%2f557805%2fproblems-with-aircrack-ng%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          5 Answers
          5






          active

          oldest

          votes








          5 Answers
          5






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          0
          down vote













          The first error seems to indicated that Network Manager is already using wlan0 (in addition to wpa_supplicant and the other processes).



          You don't have an interface called mon0, so that's why you get the second error.



          You should be able to use aircrack if you don't use wifi via Network Manager (you can try stopping network manager and then running the command). Note that if Network Manager is not running, you have to handle the wifi configuration yourself.



          You could also try adding a virtual interface to your wireless phy with iw.
          To do this, look at the output of "iw phy". My wifi card is phy0, so:



          "sudo iw phy phy0 interface add mon0 type monitor"



          Then retry the second command.



          You can get an idea of what your card supports with "iw phy phy0 info". Again, replace phy0 with the correct argument. Check that it supports monitor mode if you have problems adding a monitor interface.



          I noticed you have a broadcom card, so monitor should be supported. You can check your wifi card support here http://wireless.kernel.org/en/users/Drivers






          share|improve this answer



























            up vote
            0
            down vote













            The first error seems to indicated that Network Manager is already using wlan0 (in addition to wpa_supplicant and the other processes).



            You don't have an interface called mon0, so that's why you get the second error.



            You should be able to use aircrack if you don't use wifi via Network Manager (you can try stopping network manager and then running the command). Note that if Network Manager is not running, you have to handle the wifi configuration yourself.



            You could also try adding a virtual interface to your wireless phy with iw.
            To do this, look at the output of "iw phy". My wifi card is phy0, so:



            "sudo iw phy phy0 interface add mon0 type monitor"



            Then retry the second command.



            You can get an idea of what your card supports with "iw phy phy0 info". Again, replace phy0 with the correct argument. Check that it supports monitor mode if you have problems adding a monitor interface.



            I noticed you have a broadcom card, so monitor should be supported. You can check your wifi card support here http://wireless.kernel.org/en/users/Drivers






            share|improve this answer

























              up vote
              0
              down vote










              up vote
              0
              down vote









              The first error seems to indicated that Network Manager is already using wlan0 (in addition to wpa_supplicant and the other processes).



              You don't have an interface called mon0, so that's why you get the second error.



              You should be able to use aircrack if you don't use wifi via Network Manager (you can try stopping network manager and then running the command). Note that if Network Manager is not running, you have to handle the wifi configuration yourself.



              You could also try adding a virtual interface to your wireless phy with iw.
              To do this, look at the output of "iw phy". My wifi card is phy0, so:



              "sudo iw phy phy0 interface add mon0 type monitor"



              Then retry the second command.



              You can get an idea of what your card supports with "iw phy phy0 info". Again, replace phy0 with the correct argument. Check that it supports monitor mode if you have problems adding a monitor interface.



              I noticed you have a broadcom card, so monitor should be supported. You can check your wifi card support here http://wireless.kernel.org/en/users/Drivers






              share|improve this answer














              The first error seems to indicated that Network Manager is already using wlan0 (in addition to wpa_supplicant and the other processes).



              You don't have an interface called mon0, so that's why you get the second error.



              You should be able to use aircrack if you don't use wifi via Network Manager (you can try stopping network manager and then running the command). Note that if Network Manager is not running, you have to handle the wifi configuration yourself.



              You could also try adding a virtual interface to your wireless phy with iw.
              To do this, look at the output of "iw phy". My wifi card is phy0, so:



              "sudo iw phy phy0 interface add mon0 type monitor"



              Then retry the second command.



              You can get an idea of what your card supports with "iw phy phy0 info". Again, replace phy0 with the correct argument. Check that it supports monitor mode if you have problems adding a monitor interface.



              I noticed you have a broadcom card, so monitor should be supported. You can check your wifi card support here http://wireless.kernel.org/en/users/Drivers







              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Dec 7 '14 at 23:05

























              answered Dec 7 '14 at 22:19









              ears_and_tails

              13




              13
























                  up vote
                  0
                  down vote













                  type this before use aircrack-ng:



                  sudo ifconfig <interface(wlan0)> down


                  then use the aircrack-ng
                  if not work try this:



                  sudo airmon-ng check kill


                  then airmon-ng start.............






                  share|improve this answer

























                    up vote
                    0
                    down vote













                    type this before use aircrack-ng:



                    sudo ifconfig <interface(wlan0)> down


                    then use the aircrack-ng
                    if not work try this:



                    sudo airmon-ng check kill


                    then airmon-ng start.............






                    share|improve this answer























                      up vote
                      0
                      down vote










                      up vote
                      0
                      down vote









                      type this before use aircrack-ng:



                      sudo ifconfig <interface(wlan0)> down


                      then use the aircrack-ng
                      if not work try this:



                      sudo airmon-ng check kill


                      then airmon-ng start.............






                      share|improve this answer












                      type this before use aircrack-ng:



                      sudo ifconfig <interface(wlan0)> down


                      then use the aircrack-ng
                      if not work try this:



                      sudo airmon-ng check kill


                      then airmon-ng start.............







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered Sep 12 '15 at 12:04









                      cloner

                      1




                      1






















                          up vote
                          0
                          down vote













                          Was seeing the same error running precompiled binaries on Raspian and ended up building from source to get past it.






                          share|improve this answer





















                          • While this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference.
                            – Kevin Bowen
                            Aug 9 '16 at 20:18










                          • Thanks for the feedback and I see your point. But anything more detailed is likely to vary by system or configuration, and over time, and would likely cause more frustration than it would benefit the audience.
                            – Josh Habdas
                            Aug 10 '16 at 23:11















                          up vote
                          0
                          down vote













                          Was seeing the same error running precompiled binaries on Raspian and ended up building from source to get past it.






                          share|improve this answer





















                          • While this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference.
                            – Kevin Bowen
                            Aug 9 '16 at 20:18










                          • Thanks for the feedback and I see your point. But anything more detailed is likely to vary by system or configuration, and over time, and would likely cause more frustration than it would benefit the audience.
                            – Josh Habdas
                            Aug 10 '16 at 23:11













                          up vote
                          0
                          down vote










                          up vote
                          0
                          down vote









                          Was seeing the same error running precompiled binaries on Raspian and ended up building from source to get past it.






                          share|improve this answer












                          Was seeing the same error running precompiled binaries on Raspian and ended up building from source to get past it.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Aug 9 '16 at 19:36









                          Josh Habdas

                          1012




                          1012












                          • While this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference.
                            – Kevin Bowen
                            Aug 9 '16 at 20:18










                          • Thanks for the feedback and I see your point. But anything more detailed is likely to vary by system or configuration, and over time, and would likely cause more frustration than it would benefit the audience.
                            – Josh Habdas
                            Aug 10 '16 at 23:11


















                          • While this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference.
                            – Kevin Bowen
                            Aug 9 '16 at 20:18










                          • Thanks for the feedback and I see your point. But anything more detailed is likely to vary by system or configuration, and over time, and would likely cause more frustration than it would benefit the audience.
                            – Josh Habdas
                            Aug 10 '16 at 23:11
















                          While this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference.
                          – Kevin Bowen
                          Aug 9 '16 at 20:18




                          While this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference.
                          – Kevin Bowen
                          Aug 9 '16 at 20:18












                          Thanks for the feedback and I see your point. But anything more detailed is likely to vary by system or configuration, and over time, and would likely cause more frustration than it would benefit the audience.
                          – Josh Habdas
                          Aug 10 '16 at 23:11




                          Thanks for the feedback and I see your point. But anything more detailed is likely to vary by system or configuration, and over time, and would likely cause more frustration than it would benefit the audience.
                          – Josh Habdas
                          Aug 10 '16 at 23:11










                          up vote
                          0
                          down vote













                          This conflicting behavior comes from network manager.
                          If you don't want to use sudo airmon-ng check kill (which totally stop network manager) you can add an exception for your mon0 interface as explained here: aircrack-ng : airmon-ng stop working after updating to 15.04 ( ioctl(SIOCSIWMODE) failed: Device or resource busy )



                          1.Open network manger configuration file with root privileges



                          sudo gedit /etc/NetworkManager/NetworkManager.conf


                          2.Add the following lines at the end of your file to create an exception for your mode monitor interfaces.



                          [keyfile]
                          unmanaged-devices=interface-name:mon*;


                          Once you saved the changes effects are immediate and airmon-ng will be able to handle properly the interface
                          Be aware that you are using an outdated version of aircrack-ng (the one from ubuntu repositories I guess)
                          I strongly suggest you to install a more recent version (in this case the mode monitor interface will be called wlan0mon and not mon0 anymore)
                          Go to aircrack-ng website to download the latest stable release (Aircrack-ng 1.2 RC 4 ): aircrack-ng website






                          share|improve this answer



























                            up vote
                            0
                            down vote













                            This conflicting behavior comes from network manager.
                            If you don't want to use sudo airmon-ng check kill (which totally stop network manager) you can add an exception for your mon0 interface as explained here: aircrack-ng : airmon-ng stop working after updating to 15.04 ( ioctl(SIOCSIWMODE) failed: Device or resource busy )



                            1.Open network manger configuration file with root privileges



                            sudo gedit /etc/NetworkManager/NetworkManager.conf


                            2.Add the following lines at the end of your file to create an exception for your mode monitor interfaces.



                            [keyfile]
                            unmanaged-devices=interface-name:mon*;


                            Once you saved the changes effects are immediate and airmon-ng will be able to handle properly the interface
                            Be aware that you are using an outdated version of aircrack-ng (the one from ubuntu repositories I guess)
                            I strongly suggest you to install a more recent version (in this case the mode monitor interface will be called wlan0mon and not mon0 anymore)
                            Go to aircrack-ng website to download the latest stable release (Aircrack-ng 1.2 RC 4 ): aircrack-ng website






                            share|improve this answer

























                              up vote
                              0
                              down vote










                              up vote
                              0
                              down vote









                              This conflicting behavior comes from network manager.
                              If you don't want to use sudo airmon-ng check kill (which totally stop network manager) you can add an exception for your mon0 interface as explained here: aircrack-ng : airmon-ng stop working after updating to 15.04 ( ioctl(SIOCSIWMODE) failed: Device or resource busy )



                              1.Open network manger configuration file with root privileges



                              sudo gedit /etc/NetworkManager/NetworkManager.conf


                              2.Add the following lines at the end of your file to create an exception for your mode monitor interfaces.



                              [keyfile]
                              unmanaged-devices=interface-name:mon*;


                              Once you saved the changes effects are immediate and airmon-ng will be able to handle properly the interface
                              Be aware that you are using an outdated version of aircrack-ng (the one from ubuntu repositories I guess)
                              I strongly suggest you to install a more recent version (in this case the mode monitor interface will be called wlan0mon and not mon0 anymore)
                              Go to aircrack-ng website to download the latest stable release (Aircrack-ng 1.2 RC 4 ): aircrack-ng website






                              share|improve this answer














                              This conflicting behavior comes from network manager.
                              If you don't want to use sudo airmon-ng check kill (which totally stop network manager) you can add an exception for your mon0 interface as explained here: aircrack-ng : airmon-ng stop working after updating to 15.04 ( ioctl(SIOCSIWMODE) failed: Device or resource busy )



                              1.Open network manger configuration file with root privileges



                              sudo gedit /etc/NetworkManager/NetworkManager.conf


                              2.Add the following lines at the end of your file to create an exception for your mode monitor interfaces.



                              [keyfile]
                              unmanaged-devices=interface-name:mon*;


                              Once you saved the changes effects are immediate and airmon-ng will be able to handle properly the interface
                              Be aware that you are using an outdated version of aircrack-ng (the one from ubuntu repositories I guess)
                              I strongly suggest you to install a more recent version (in this case the mode monitor interface will be called wlan0mon and not mon0 anymore)
                              Go to aircrack-ng website to download the latest stable release (Aircrack-ng 1.2 RC 4 ): aircrack-ng website







                              share|improve this answer














                              share|improve this answer



                              share|improve this answer








                              edited Apr 13 '17 at 12:23









                              Community

                              1




                              1










                              answered Feb 20 '17 at 16:00









                              kcdtv

                              559515




                              559515






















                                  up vote
                                  0
                                  down vote













                                  When you type sudo airodump-ng mon0, it appears




                                  sudo airodump-ng mon0

                                  Interface mon0:

                                  ioctl(SIOCGIFINDEX) failed: No such device




                                  cause you don't have that interface, but you have



                                  Interface   Chipset     Driver

                                  wlan0 Broadcom wl - [phy0]mon0: ERROR while getting interface flags: No such device

                                  (monitor mode enabled on mon0)


                                  try using sudo airodump-ng wlan0.



                                  By The Way your output said




                                  wl - [phy0]mon0: ERROR while getting interface flags: No such device




                                  cause you have aircrack-ng very old version, Make sure you installed the latest version of aircrack-ng package.



                                  Your not alone, another Question have same issue with yours.



                                  Hope this helps.






                                  share|improve this answer

























                                    up vote
                                    0
                                    down vote













                                    When you type sudo airodump-ng mon0, it appears




                                    sudo airodump-ng mon0

                                    Interface mon0:

                                    ioctl(SIOCGIFINDEX) failed: No such device




                                    cause you don't have that interface, but you have



                                    Interface   Chipset     Driver

                                    wlan0 Broadcom wl - [phy0]mon0: ERROR while getting interface flags: No such device

                                    (monitor mode enabled on mon0)


                                    try using sudo airodump-ng wlan0.



                                    By The Way your output said




                                    wl - [phy0]mon0: ERROR while getting interface flags: No such device




                                    cause you have aircrack-ng very old version, Make sure you installed the latest version of aircrack-ng package.



                                    Your not alone, another Question have same issue with yours.



                                    Hope this helps.






                                    share|improve this answer























                                      up vote
                                      0
                                      down vote










                                      up vote
                                      0
                                      down vote









                                      When you type sudo airodump-ng mon0, it appears




                                      sudo airodump-ng mon0

                                      Interface mon0:

                                      ioctl(SIOCGIFINDEX) failed: No such device




                                      cause you don't have that interface, but you have



                                      Interface   Chipset     Driver

                                      wlan0 Broadcom wl - [phy0]mon0: ERROR while getting interface flags: No such device

                                      (monitor mode enabled on mon0)


                                      try using sudo airodump-ng wlan0.



                                      By The Way your output said




                                      wl - [phy0]mon0: ERROR while getting interface flags: No such device




                                      cause you have aircrack-ng very old version, Make sure you installed the latest version of aircrack-ng package.



                                      Your not alone, another Question have same issue with yours.



                                      Hope this helps.






                                      share|improve this answer












                                      When you type sudo airodump-ng mon0, it appears




                                      sudo airodump-ng mon0

                                      Interface mon0:

                                      ioctl(SIOCGIFINDEX) failed: No such device




                                      cause you don't have that interface, but you have



                                      Interface   Chipset     Driver

                                      wlan0 Broadcom wl - [phy0]mon0: ERROR while getting interface flags: No such device

                                      (monitor mode enabled on mon0)


                                      try using sudo airodump-ng wlan0.



                                      By The Way your output said




                                      wl - [phy0]mon0: ERROR while getting interface flags: No such device




                                      cause you have aircrack-ng very old version, Make sure you installed the latest version of aircrack-ng package.



                                      Your not alone, another Question have same issue with yours.



                                      Hope this helps.







                                      share|improve this answer












                                      share|improve this answer



                                      share|improve this answer










                                      answered Oct 17 at 10:09









                                      abu-ahmed al-khatiri

                                      88415




                                      88415






























                                          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%2f557805%2fproblems-with-aircrack-ng%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 change which sound is reproduced for terminal bell?

                                          Can I use Tabulator js library in my java Spring + Thymeleaf project?

                                          Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents