Date: Wed, 7 Nov 2012 13:28:25 +1100 (EST) From: Ian Smith <smithi@nimnet.asn.au> To: Adrian Chadd <adrian@freebsd.org> Cc: freebsd-wireless@freebsd.org Subject: Re: Replacing wireless nic on my router Message-ID: <20121107132255.I83367@sola.nimnet.asn.au> In-Reply-To: <CAJ-Vmon=m_hOnAP_enmW8BcO=T23bMucf-vKYdtNDOsd35VWnA@mail.gmail.com> References: <201211042144.08807.onyx@z-up.ru> <201211051849.51278.onyx@z-up.ru> <CAJ-VmonZp1NRbRu0Zvz_6kaR5wSpj6WhFrGT=YErGLWLG=rQXw@mail.gmail.com> <201211052039.55188.onyx@z-up.ru> <CAJ-Vmon=m_hOnAP_enmW8BcO=T23bMucf-vKYdtNDOsd35VWnA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 5 Nov 2012 08:47:36 -0800, Adrian Chadd wrote: > Hi, > > 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 > associate? > > Thanks, > > > > Adrian Maybe a silly question, it's more likely a wireless problem as you suspect, but are we sure there's no firewall involved that might be dropping DHCP responses on the client? cheers, Ian > > On 5 November 2012 08:39, Dmitry Kolosov <onyx@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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121107132255.I83367>