Jump to content

ViTALiTY

Active Members
  • Posts

    36
  • Joined

  • Last visited

Everything posted by ViTALiTY

  1. Nevermind, it's just a WPS lock. Now, from what I've seen, there are some things to try. The mdk3 attacks, but they have to be automated. Found a script to do it by repzeroworld: https://forums.hak5.org/index.php?/topic/32494-reaver-ap-rate-limiting-detected-and-automatic-mdk3-solution/ But it's for reaver... I need it working for Bully, as reaver just hangs on the "Association sucessfull" message. Another thing I wanted to try out was something like a mac changer automated script, to change mac address every x seconds. But how viable is this option? Don't the interfaces have to be down in order to change the MAC? If so, that would mean that I would have to automate that too. Stopping the attack on Bully, changing the MAC, and starting the attack again... Can anyone shed some light on all this?
  2. Is there anything like this for Bully? Reaver doesn't work with me unfortunately.
  3. Would anyone kindly explain to what exactly happened here and how can I improve the attack? Thanks in advance!
  4. Thanks. I don't know why have I forgot to set the SSH access. Another question... Because now this is happening and I have no idea why. Using Kali, Bully gets the beacon right away but times out. Here, Bully does not get the beacon. The power is always around 70%. The AP shows up on wash, it has the vulnerability. Isn't that enough? Or is anything else wrong?
  5. Ok, great. Sorry for the stupid question, but where exactly do I enter the command?
  6. What do you mean by that? "ifconfig wlan1 down"?
  7. Forgot to add something. If it helps, I'm using wlan0 as client to another AP and wlan1 to use Bully (but not on that AP of course).
  8. Everytime I try to use Bully, this happens. Could anyone please help me out? Thanks in advance.
×
×
  • Create New...