abaddon

first off airjack does a number of things that host ap doesnt, it will let you switch to modes that host ap will not, its more stable than host ap, it will allow you to send data frames both from and to ds without a driver change out, it will allow you to send frames from within monitor mode (though not very well) it will allow you to switch to such modes as mode 5 which wont send out beacons but will still give you the ability to send frames while having the firmware handle frame ack's and the like...the other major difference is that when i first started writing drivers like airjack there was no such thing as the host ap so i had to go it alone, so i just stay'ed that path rather than making host ap do something it really wasnt ment to...

to address your second question, for somethings the disassociate will work the same, for others it will not, one thing it doesnt do if you send out disassociate frames is it will not attack adhoc networks as they do not associate (they only authenticate), another difference is that sometimes one some hardware if you simply disassociate them they wont send out proberequest anymore and that is one of the ways i get the ESSID in essid_jack...the final reason why i chose the deauth rather than the disassociate (although i believe i left it in as an option to choose which you wanted) was because if i deauth you, you are forced to re-authenticate and reassociate, this causes you to have to go through twice the number of steps to get back on, and when we're trying to take down an entire network that goes along way...

--Abaddon

http://802.11ninja.net