Refrain from confusing the router with an extra trailing eapol start

From Tizzaran d576c488785107620fd5e4b9776bb50c5a75bd5f
Return expected extended supported rates when associating

[From Tizzaran f504bec916b6de35fd4d7d3e5537cc4f71687aca]
More detailed SQL error codes

[From Tizzaran 774f2f3c142aab5588737289a84fa654b8e1da46]
Notice deauthentication packets.  This stops us from pounding routers with EAPOL_START packets that no longer consider us associated.

[From Tizzaran 27fdd03f5c5f78d0183f150f9de043120a5e86bd]
Add function to retransmit the last packet.  EAPOL_SEND now has the retry flag set after the first transmission.

Conflicts:
	globule.c

[From Tizzaran e7787d284d84eda36b5452c1b5a7393cdb509049]
Fixed the issue 195 of the original reaver-wps project: Stuck at 99%

The problem was that the pin_count never reached the get_max_pin_attempts value, so the loop was never broken
I replaced the pin_count variable with a function which calculates the current pin_count on the fly

git-svn-id: http://reaver-wps-fork.googlecode.com/svn/trunk@6 24fcba9c-2a07-bdb3-7e59-f74f9f0294fe

Conflicts:
	cracker.c

[From reaver-wps-fork.googlecode.com b37897186ab5dd4a90f4f854d180f72b072e6bc4]
README: note picking status
indent -linux cracker.c to make this next merge pick easier
Improved verbose messages and status print (now it includes elapsed and estimated time)

Also, in this version I fixed a potential bug, which was probably the cause of the Issue number 1 (Segmentation fault exception)

git-svn-id: http://reaver-wps-fork.googlecode.com/svn/trunk@7 24fcba9c-2a07-bdb3-7e59-f74f9f0294fe

Conflicts:
	cracker.c
	cracker.h

[reaver-wps-fork 09ee0023591a427fb6f9ec38738eee8a610799bd]
note status