From owner-freebsd-wireless@FreeBSD.ORG Mon Nov 5 16:47:37 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 52F5B89B for ; Mon, 5 Nov 2012 16:47:37 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 216278FC0C for ; Mon, 5 Nov 2012 16:47:37 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id rp8so4265244pbb.13 for ; Mon, 05 Nov 2012 08:47:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=ByJDiYK6l9IF+VwN9cmbQrYnEdBlUUAS3HeSHi4ZSko=; b=PQ3HTZv7o3dMeDmTfhU0tcXkCEh2Wa9aiw1sEyP9hTP3iuptmdby3Tfz0+GpqDrfVY LUPBlfj+QG4jZpQBHdfrE9ohkKcBckUrvmfGJMg1jdNq0zbOuja7pug9ru+yThHYeqoI hICQeAPSiZ1ZGSqVenVhpLsLGcIm02KKkSdcBrqGPDDBVOEvYIdlimXvUU5OF7wjBb0A LxswMPOkt7I/ihRSKGtiYyTlS+CCGFxk1PKRMNpcyt0TBnMFk7i+po2GmcZncPqlpLkP 9a/+gjqDDN+hVDJG7sQOosiPmP2vcL2PBszjxJmplwMxXDp8f+bz9elZUtsicP0EEVID o+tg== MIME-Version: 1.0 Received: by 10.68.137.41 with SMTP id qf9mr31695396pbb.103.1352134056954; Mon, 05 Nov 2012 08:47:36 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.68.124.130 with HTTP; Mon, 5 Nov 2012 08:47:36 -0800 (PST) In-Reply-To: <201211052039.55188.onyx@z-up.ru> References: <201211042144.08807.onyx@z-up.ru> <201211051849.51278.onyx@z-up.ru> <201211052039.55188.onyx@z-up.ru> Date: Mon, 5 Nov 2012 08:47:36 -0800 X-Google-Sender-Auth: Cg0W8Bn06MbOCwE3MAICb8RM_8A Message-ID: Subject: Re: Replacing wireless nic on my router From: Adrian Chadd To: onyx@z-up.ru Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Nov 2012 16:47:37 -0000 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 On 5 November 2012 08:39, Dmitry Kolosov 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.