All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: "Chris Adams" <cma@cmadams.net>,
	"Rafał Miłecki" <zajec5@gmail.com>,
	"Larry Finger" <Larry.Finger@lwfinger.net>,
	b43-dev@lists.infradead.org,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: BCM4331 deauthenticates every five minutes
Date: Thu, 20 Jun 2013 10:24:46 -0500	[thread overview]
Message-ID: <1371741886.10995.3.camel@dcbw.foobar.com> (raw)
In-Reply-To: <51C2BE54.20509@broadcom.com>

On Thu, 2013-06-20 at 10:33 +0200, Arend van Spriel wrote:
> On 06/19/2013 11:11 PM, Chris Adams wrote:
> > Once upon a time, Arend van Spriel <arend@broadcom.com> 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.

It should be enough run "nmcli nm wifi off" and then un-rfkill the
interface, and NM will leave it alone until you turn wifi back on.  It
will also remove the interface from wpa_supplicant.

Dan

> 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].
> 
> 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

WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dcbw@redhat.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: "Chris Adams" <cma@cmadams.net>,
	"Rafał Miłecki" <zajec5@gmail.com>,
	"Larry Finger" <Larry.Finger@lwfinger.net>,
	b43-dev@lists.infradead.org,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: BCM4331 deauthenticates every five minutes
Date: Thu, 20 Jun 2013 10:24:46 -0500	[thread overview]
Message-ID: <1371741886.10995.3.camel@dcbw.foobar.com> (raw)
In-Reply-To: <51C2BE54.20509@broadcom.com>

On Thu, 2013-06-20 at 10:33 +0200, Arend van Spriel wrote:
> On 06/19/2013 11:11 PM, Chris Adams wrote:
> > Once upon a time, Arend van Spriel <arend@broadcom.com> 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.

It should be enough run "nmcli nm wifi off" and then un-rfkill the
interface, and NM will leave it alone until you turn wifi back on.  It
will also remove the interface from wpa_supplicant.

Dan

> 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].
> 
> 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@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



  parent reply	other threads:[~2013-06-20 15:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-19 16:09 BCM4331 deauthenticates every five minutes Chris Adams
2013-06-19 16:35 ` Larry Finger
2013-06-19 16:35   ` Larry Finger
2013-06-19 16:42   ` Chris Adams
2013-06-19 16:42     ` Chris Adams
2013-06-19 16:57     ` Rafał Miłecki
2013-06-19 16:57       ` Rafał Miłecki
2013-06-19 17:58       ` Chris Adams
2013-06-19 17:58         ` Chris Adams
2013-06-19 19:30         ` Rafał Miłecki
2013-06-19 19:30           ` Rafał Miłecki
2013-06-19 20:58         ` Arend van Spriel
2013-06-19 20:58           ` Arend van Spriel
2013-06-19 21:11           ` Chris Adams
2013-06-19 21:11             ` Chris Adams
2013-06-20  8:33             ` Arend van Spriel
2013-06-20  8:33               ` Arend van Spriel
2013-06-20  8:36               ` Arend van Spriel
2013-06-20  8:36                 ` Arend van Spriel
2013-06-20 15:24               ` Dan Williams [this message]
2013-06-20 15:24                 ` Dan Williams
2013-06-20  0:28         ` Chris Adams
2013-06-20  0:28           ` Chris Adams
2013-06-24 13:22           ` Chris Adams
2013-06-24 13:22             ` Chris Adams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1371741886.10995.3.camel@dcbw.foobar.com \
    --to=dcbw@redhat.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=arend@broadcom.com \
    --cc=b43-dev@lists.infradead.org \
    --cc=cma@cmadams.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=zajec5@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.