You need to verify that the packet is actually going out over the air,
and that it's being received by the client.

It could be rejected for a variety of reasons:

* If it's going out the wrong rate, because somehow it's going out
(say) 11n when the client i 11g;
* It's being received at the other end but it's being rejected - eg
out of sequence, or incorrect encryption setup.

The newer NIC brings with it a different HAL (AR5416/AR9002 HAL versus
AR5212 HAL) and so there may be some subtle behavioural changes.

Have you tried running the AP in open mode and ensuring everything can



On 5 November 2012 08:39, Dmitry Kolosov <o...@z-up.ru> wrote:
>> The first thing I'd do is start by verifying that the packet actually
>> went out over the air.
> I think they do. In both ways. I can see it on AP with tcpdump. Linux and
> WinXP installed on the same laptop working fine with same AP before and
> after changing wireless nic on AP.
>> I'd also use athstats to see if your station is receiving the DHCP
>> replies. The "Rx" counter should be going up each time the server
>> sends the response.
> Can't i see it with tcpdump? I'm starting tcpdump on AP and on client at the
> same time and run `dhclient wlan0` on client. On client i see outgoing DHCP
> request after association with AP. On AP i see incoming DHCP request from
> client! On AP i see outgoing DHCP reply to client! But i don't see incoming
> DHCP reply on clinet with tcpdump -y IEEE802_11_RADIO or with default media
> type.
> Thanks in advance, Adrian.
> Really weird. All other devices working just fine.
freebsd-wireless@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Reply via email to