Quote:
Originally Posted by TheBrotherOf
Thanks for the nice tutorial. I have a question about the logic behind the attack. It seems like we're not doing any sort of NAT in order for the victim to see internet access (unless I'm missing something), so what are we really going to get out of this? Once someone connects, notices the lack of internet connection, won't they just disconnect and try to move on? What sort of information are we able to gather or which exploits are we trying to achieve?
|
You're right. I have to add the NAT or whatever. But as I'm not doing real exploitation of a victim, I'm fine to see that it works. But I will try to set up some NAT or it would be great if you could test and contribute.
Btw does it work with http or only with https for you?
Quote:
Originally Posted by TheBrotherOf
While I have been able to get this mostly working, I'm still having some issues:
1.) Windows never connects to my rogue AP. It always errors out (Windows can't connect to ________).
|
Maybe something is wrong with your DHCP client on the attacker. Check your dhcp configuration again. I had the same issue and this was my fault.
Quote:
Originally Posted by TheBrotherOf
2.) I can connect with my Blackberry, and it gets an IP address, but it never stays connected for more than about 15 seconds. It will disconnect (or be disco'd) and then reconnect via another fake SSID from the rogue AP.
I've tried lowering the MTU size but that seems to have no effect. Anyone else have these issues?
|
The Blackberry issue is interesting. I'm not quite sure, but maybe try airbase without -P -C 30. I think then the attacker shouldn't set up a AP for every probed ESSID he sees flying aroung

. But I think maybe it's just the same issue as with the windows pc.