Server
The server shouldn't only do airmon-ng's work, but all the receiving/sending of frames together.
- Build list of accesspoints
- Save every available information in these lists
- Connect the wifi clients accordingly to the (last) associated AP(s)
- There should be a database in the server, so that each client instantly has the same knowledge as the server
- Streams all received packets to all connected clients, receive packets from clients and inject them (user can give their filter options so that only useful packets are sent and bandwith is saved).
- Set filters to limit the bandwidth used for each client (filter based on ieee80211 header bits)
- Recording and replaying of frame sequences
- Auto processing all passive attacks (ska keystream calculation, wpa handshake saving, essid decloaking), just like airodump-ng now
- Connect to other servers to allow distributed cracking, database synchronisation and remote injection
- Automaticially write the pcap and/or keystream file after a specified amount of data or time
- Load multiple pcap files when starting to initially fill the database to resume a previous injection/cracking session
- Read configuration out of a .conf file
- Can be started without an interface, so you can do a remote/offline analysis
