[Winpcap-users] associated, but not connected

[Bryan Kadzban]

On Tue, Oct 11, 2005 at 05:55:35PM +0200, Michal Szostakiewicz wrote:
> (windows says that the connection is limited or there is no connection
> at all)

I'm not sure about the "no connection at all" state, but the "connection
is limited" state is determined by whether a DHCP server responds.

If you're associated but haven't gone through the EAP exchange, or
haven't gone through the WPA/WPA2 4-way handshake, then your card won't
be able to pass any traffic, including a DHCP request.  And DHCP failing
is what causes XP to say "this connection has limited or no
connectivity".

So, you could check whether the interface has an IP address assigned.
If it has a 169.254.0.0/16 address, or 0.0.0.0, then DHCP has failed,
and you're probably in that state.  To look at this, you could either
run ipconfig and try to parse its output, or you could look into the
API calls that would be required to find this information out.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.winpcap.org/pipermail/winpcap-users/attachments/20051011/383acfc2/attachment.pgp