From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arend van Spriel Date: Thu, 20 Jun 2013 10:36:42 +0200 Subject: BCM4331 deauthenticates every five minutes In-Reply-To: <51C2BE54.20509@broadcom.com> References: <20130619160911.GB4784@cmadams.net> <51C1DDEB.3090701@lwfinger.net> <20130619164227.GC4784@cmadams.net> <20130619175850.GD4784@cmadams.net> <51C21B7C.2030005@broadcom.com> <20130619211108.GG4784@cmadams.net> <51C2BE54.20509@broadcom.com> Message-ID: <51C2BF1A.5010908@broadcom.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Chris Adams Cc: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= , Larry Finger , b43-dev@lists.infradead.org, linux-wireless On 06/20/2013 10:33 AM, Arend van Spriel wrote: > On 06/19/2013 11:11 PM, Chris Adams wrote: >> Once upon a time, Arend van Spriel said: >>> Can you make a capture using a wireless sniffer (using your thinkpad >>> maybe)? >> >> How would I go about doing that? I've done lots of network debugging >> with tcpdump and such, but not much wireless stuff. >> > > I use wireshark these days. If you install that you can use the steps > below and select the wireless interface in wireshark to capture. I use > wlan0 as interface name, but it may be different for you. > > 1. disable network-manager so it won't interfere. > 2. bring the interface down > $ sudo ifconfig wlan0 down > 3. change interface type to monitor > $ sudo iw dev wlan0 set type monitor > 4. bring up the interface > $ sudo ifconfig wlan0 up > 5. start wireshark and select wlan0 > $ gksudo wireshark > > It will complain that running wireshark as root is not secure. If you > care about that, you should read [1]. Forgot a step. You need to select a channel. You can do that before starting a capture in wireshark: $ sudo iw dev wlan0 set channel 5 > Regards, > Arend > > [1] > http://wiki.wireshark.org/Security#Administrator.2Froot_account_not_required.21 > > > -- > To unsubscribe from this list: send the line "unsubscribe > linux-wireless" in > the body of a message to majordomo at vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >