Vista TCP

I'm having a problem with a 802.11n WiFi driver I am developing for Vista
(build 5384).

When I use a static IP address, everything works fine. However, if I use
DHCP, I don't get a DHCP address allocated to me from the AP.

I know DHCP in Vista 5384 works because I have a Realtek 8185 802.11g card
that works OK.

Here are a couple of clues to the problem:

1. The first thing I found was that the driver was transmitting the DHCP
DISCOVER broadcast packet and then receiving a DHCP OFFER broadcast back
from the AP. However, the driver's packets filters were setup to handle
only DIRECTED (i.e. unicast) packets. This seemed a little strange, since I
believe during TCP protocol initialization the driver should be called to
set the the MULTICAST and BROADCAST filters.

2. Thinking that perhaps I had a problem with the packet filters, I
jury-rigged the driver to accept all packets which then started indicating
the DHCP OFFFER broadcasts up to the protocols. This did not work. TCP
still would not transmit a DHCP REQUEST packet to the AP.

3. Thinking that I still have a problem with the packet filters, I add more
debug traces to the driver and rerum the test. PRESTO! Now I have a valid
DHCP address from the AP. Strange. However, now I cannot ping the AP.

Anybody have any thoughts about this problem?

((&->

pavel_a
Tue Jun 20 14:57:02 CDT 2006

You write a native ndis 6 miniport, correct?

--PA

"QuasiCodo" wrote:
> I'm having a problem with a 802.11n WiFi driver I am developing for Vista
> (build 5384).
>
> When I use a static IP address, everything works fine. However, if I use
> DHCP, I don't get a DHCP address allocated to me from the AP.
>
> I know DHCP in Vista 5384 works because I have a Realtek 8185 802.11g card
> that works OK.
>
> Here are a couple of clues to the problem:
>
> 1. The first thing I found was that the driver was transmitting the DHCP
> DISCOVER broadcast packet and then receiving a DHCP OFFER broadcast back
> from the AP. However, the driver's packets filters were setup to handle
> only DIRECTED (i.e. unicast) packets. This seemed a little strange, since I
> believe during TCP protocol initialization the driver should be called to
> set the the MULTICAST and BROADCAST filters.
>
> 2. Thinking that perhaps I had a problem with the packet filters, I
> jury-rigged the driver to accept all packets which then started indicating
> the DHCP OFFFER broadcasts up to the protocols. This did not work. TCP
> still would not transmit a DHCP REQUEST packet to the AP.
>
> 3. Thinking that I still have a problem with the packet filters, I add more
> debug traces to the driver and rerum the test. PRESTO! Now I have a valid
> DHCP address from the AP. Strange. However, now I cannot ping the AP.
>
> Anybody have any thoughts about this problem?
>
> ((&->
>
>
>

QuasiCodo
Tue Jun 20 15:18:34 CDT 2006

Native WiFi -- Correct. I just have something out of skelter. It might be
that I don't have some indication to NDIS set up just right. In the
indications, I've given NDIS: CONN_START, ASSOC_START, LINK_STATE,
LINK_STATE, ASSOC_COMPLETE, LINK_QUALITY, CONN_COMPLETE. These seem to be
working to establish an association and connection with the AP and since
static IP address let me xfer packets back and forth.

((&->

"Pavel A." <pavel_a@NOwritemeNO.com> wrote in message
news:59A5A5BA-476E-4924-B857-1052FB058DA7@microsoft.com...
> You write a native ndis 6 miniport, correct?
>
> --PA
>
> "QuasiCodo" wrote:
>> I'm having a problem with a 802.11n WiFi driver I am developing for Vista
>> (build 5384).
>>
>> When I use a static IP address, everything works fine. However, if I use
>> DHCP, I don't get a DHCP address allocated to me from the AP.
>>
>> I know DHCP in Vista 5384 works because I have a Realtek 8185 802.11g
>> card
>> that works OK.
>>
>> Here are a couple of clues to the problem:
>>
>> 1. The first thing I found was that the driver was transmitting the DHCP
>> DISCOVER broadcast packet and then receiving a DHCP OFFER broadcast back
>> from the AP. However, the driver's packets filters were setup to handle
>> only DIRECTED (i.e. unicast) packets. This seemed a little strange,
>> since I
>> believe during TCP protocol initialization the driver should be called to
>> set the the MULTICAST and BROADCAST filters.
>>
>> 2. Thinking that perhaps I had a problem with the packet filters, I
>> jury-rigged the driver to accept all packets which then started
>> indicating
>> the DHCP OFFFER broadcasts up to the protocols. This did not work. TCP
>> still would not transmit a DHCP REQUEST packet to the AP.
>>
>> 3. Thinking that I still have a problem with the packet filters, I add
>> more
>> debug traces to the driver and rerum the test. PRESTO! Now I have a
>> valid
>> DHCP address from the AP. Strange. However, now I cannot ping the AP.
>>
>> Anybody have any thoughts about this problem?
>>
>> ((&->
>>
>>
>>