From owner-freebsd-wireless@FreeBSD.ORG Mon Nov 5 15:54:04 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 9F9AA2A5 for ; Mon, 5 Nov 2012 15:54:04 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-da0-f54.google.com (mail-da0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6E75A8FC12 for ; Mon, 5 Nov 2012 15:54:04 +0000 (UTC) Received: by mail-da0-f54.google.com with SMTP id z9so2868192dad.13 for ; Mon, 05 Nov 2012 07:54:03 -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=zMSYG1fhQBr8JNIwLq567JkOTc4tCCALtVazaic//8Q=; b=PCFa2lKJaVpQgYU7ET2IyMavyqp2/Gn+qfIDfwBULF8igxZCNso4V1nLojPXnLiwwn jzd0SJgf9245mR6/H4G8b6Nqua0VEwMsI9WIVmBY8LiPuw/hqZwMmlfXNXzyyogdOQT/ bfDvPkdATEB9dboHrGv4SXK0W+gEZnj9PRv+xiWAW4CHunK7U2sB8HjBPnMWrqfpKggy DhSPAXDBHKjqHZKPUN+9qmsmDvYY93t4zaWP5Ohei+N0ahWOCZOtijhWR35LYZhQIfFY 6QfJsPCQDtV2T1FDtSMMEe8elQK5fG++wgzPSDwHIqJFHgAv6pAZg3xnGWHfYGl5yHm9 bAOg== MIME-Version: 1.0 Received: by 10.68.238.199 with SMTP id vm7mr18615732pbc.105.1352130843654; Mon, 05 Nov 2012 07:54:03 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.68.124.130 with HTTP; Mon, 5 Nov 2012 07:54:03 -0800 (PST) In-Reply-To: <201211051849.51278.onyx@z-up.ru> References: <201211042144.08807.onyx@z-up.ru> <201211051849.51278.onyx@z-up.ru> Date: Mon, 5 Nov 2012 07:54:03 -0800 X-Google-Sender-Auth: j4LDVog1XLWUYXJ_j5mm2dZ38-I 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 15:54:04 -0000 On 5 November 2012 06:49, Dmitry Kolosov wrote: > Please take a look at this: http://pastebin.com/7H0BGTfZ > This is a tcpdump output on wireless router. > > Here, > f0:7d:68:af:0e:b6 - is my wireless router 1) > 00:1f:3a:25:47:2e - is my wireless client 3) > > First 2 packets from client (after powering up) contains something like > "Receiver not Ready". Huh.. Also, packets from 1) to 3) never reaches 3). As The RnR is just a broadcast frame generated from hostap. > you can see, 00:1f:3a:25:47:2e asking for DHCP (BOOTP/DHCP, Request packets) > over and over again. > > Same time, on client 3) tcpdump shows only request and no reply coming at all, > except packets with ethertype EAPOL (0x888e) (auth?) > > Any ideas? The first thing I'd do is start by verifying that the packet actually went out over the air. Put one of the atheros stations into monitor mode, then tcpdump -ni wlanX -y IEEE802_11_RADIO. If you run wireshark on FreeBSD as root, you can select the 802.11 capture format and it'll do that for you. That lets you see exactly what's going on. However, it only can decrypt frames sent to itself - so either you have to be running WEP or OPEN. WPA /WPA2 won't let you see frames destined to other stations. I'd also add "options ATH_DEBUG", AH_DEBUG and ATH_DIAGAPI to the kernel, so you can do more detailed debugging. 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. Adrian