WPA-PSK problem. Client getting DEauthed - RC 4.
Bookmark this page:
 Yahoo!
 Google
 Windows Live
 del.icio.us
 digg
 Netscape
|
|
|||||||||||||
|
Posted by TheDood on April 4, 2008, 5:48 pm
Please log in for more thread options with WPA-PSK. They seems to work fine for about 1 - 2 hours, but then they are knocked off the network. Running a wireshark trace it showed that the AP sends 3 WPA-PSK handshakes that the PDA never responds to. The AP then sends a DEauth with reason code 4 - which indicates that the AP or backend controller cancelled the session due to inactivity. Access point: Cisco AIR-LAP1242AG-A-K9. Anyone experience this issue? Anything to look for? | |||||||||||||
|
Posted by Peter Pan on April 4, 2008, 10:39 pm
Please log in for more thread options What types of PDA, and is it native support for WPA or an addon program? | |||||||||||||
| Similar Threads | Posted |
| WPA-PSK problem. Client getting DEauthed - RC 4. | April 4, 2008, 5:48 pm |
| Problem with Odyssey Client scan lists | August 26, 2005, 7:33 am |
| Dhcp daemon --> router --> WAP --> client problem | January 27, 2008, 11:01 am |
| Edge-Core VG007 Wireless Client Problem | September 17, 2007, 8:36 am |
| Access Point that supports Wireless Client - Client Mode | December 27, 2006, 11:25 am |
| Client to Client hotspot isolation | February 23, 2005, 1:10 pm |
| WaveRider Client-to-Client? | December 19, 2004, 8:46 pm |
| Best 5 GHz Client Card ? | December 31, 2004, 2:43 pm |
| AP and Client in the same time | January 24, 2006, 9:22 am |
| client manager for dos? | March 9, 2006, 2:49 am |
| Wireless client ? | August 10, 2006, 8:53 am |
| Netgear vpn client | September 24, 2006, 1:17 am |
| Setting up client | November 1, 2006, 5:35 pm |
| How does an AP know if a client is still connected? | March 21, 2007, 4:03 am |
| Can an AP client be detected | August 16, 2007, 9:03 pm |
> with WPA-PSK. They seems to work fine for about 1 - 2 hours, but then
> they are knocked off the network. Running a wireshark trace it showed
> that the AP sends 3 WPA-PSK handshakes that the PDA never responds to.
> The AP then sends a DEauth with reason code 4 - which indicates that
> the AP or backend controller cancelled the session due to inactivity.
>
> Access point: Cisco AIR-LAP1242AG-A-K9.
>
> Anyone experience this issue? Anything to look for?