Question Waiting for Beacon - I'm confused...

Discussion in 'Xiaopan Support' started by StarTux, 2 Jun 2013.

  1. StarTux

    StarTux Well-Known Member

    Joined:
    28 May 2013
    Messages:
    6
    Likes Received:
    11
    Sorry if this has been asked before - I did search first but could not find an answer.

    I don't understand why it is that when I scan with Minidwep to see APs, each shows multiple beacons detected for each AP. But when try a WPS attack, more often than not, it fails to get even one beacon from the AP.

    Is this common? I am fairly new to this. I've been using Xiaopan 0.4.6 and today tried 0.4.6.1.
    Seemed to be the same on this issue.

    Can anyone shed light on this? o_O
     
  2. ecrudragon

    ecrudragon Legendary ^_^
    VIP

    Joined:
    15 Apr 2013
    Messages:
    145
    Likes Received:
    33
    StarTux WPS won't be enable for that particular AP which means you can't attack this AP with reaver, find any other way
     
  3. StarTux

    StarTux Well-Known Member

    Joined:
    28 May 2013
    Messages:
    6
    Likes Received:
    11
    That's confusing too. Sometimes APs show as using WPS, then next time I scan it might show they aren't?

    It's quite inconsistent, however the signal is quite weak also, like -85.
     
  4. Fantasma

    Fantasma Well-Known Member

    Joined:
    31 May 2012
    Messages:
    734
    Likes Received:
    440
    It mean you are too far from the AP that you are trying to attack
     
  5. StarTux

    StarTux Well-Known Member

    Joined:
    28 May 2013
    Messages:
    6
    Likes Received:
    11
    Does being too far also occasionally cause false reporting of WPS vulnerability on some APs?
     

Share This Page

Loading...