From: Larry Finger <Larry.Finger@lwfinger.net>
To: b43-dev@lists.infradead.org
Subject: Broadcom 4303 HP Pavilion zv5000
Date: Tue, 18 Oct 2011 13:30:58 -0500 [thread overview]
Message-ID: <4E9DC5E2.8070708@lwfinger.net> (raw)
In-Reply-To: <4E9DB5FD.6090902@vodafone.es>
On 10/18/2011 12:23 PM, Jes?s Vidal Panal?s wrote:
> El 18/10/11 17:34, Larry Finger escribi?:
>> On 10/18/2011 10:05 AM, Jes?s Vidal Panal?s wrote:
>>>>
>>> Running Wireshark on this laptop and capturing wireless interface does not show
>>> traffic at all. So there is something wrong.
>>
>> For unknown reasons, wireshark fails to capture data on my computer as well
>> abd my BCM4303 works. Use kismet.
>>
>> Larry
>>
>>
>>
> Ok. I've installed kismet, i've edited kismet.conf file, setting only source to
> this: source=b43legacy,wlan0,addme
>
> I ran kismet, and i can see my wifi essid. Packts is updating everytime, so
> sniffing is working fine. Now, what can i do with kismet to probe if my card is
> sending packets?
In general, do not drop the mailing list from the distribution list. ALWAYS use
"reply-all". All of my debugging is made available on the list. If you do not
accept that restriction, then I will be unable to help you.
You can analyze the .pcap file produced by kismet with wireshark. Look for probe
requests from your BCM4303 and the response from the AP. If you cannot analyze
the data, it is OK to send the pcap file to me privately. I will limit the
traffic to just your ESSID and post it on the list if I cannot figure out what
is wrong.
Larry
next prev parent reply other threads:[~2011-10-18 18:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-17 8:30 Broadcom 4303 HP Pavilion zv5000 Jesús Vidal Panalés
2011-10-17 9:41 ` Rafał Miłecki
2011-10-17 14:21 ` Jesús Vidal Panalés
2011-10-17 14:46 ` Larry Finger
2011-10-17 14:54 ` Jesús Vidal Panalés
2011-10-18 15:05 ` Jesús Vidal Panalés
2011-10-18 15:34 ` Larry Finger
[not found] ` <4E9DB5FD.6090902@vodafone.es>
2011-10-18 18:30 ` Larry Finger [this message]
2011-10-18 19:15 ` Jesús Vidal Panalés
2011-10-18 19:31 ` Larry Finger
2011-10-18 19:43 ` Jesús Vidal Panalés
2011-10-18 20:05 ` Larry Finger
2011-10-18 20:39 ` Jesús Vidal Panalés
2011-10-18 21:05 ` Larry Finger
2011-10-19 12:15 ` Jesús Vidal Panalés
2011-10-19 12:42 ` Larry Finger
2011-10-19 13:14 ` Jesús Vidal Panalés
2011-10-19 14:21 ` Larry Finger
2011-10-19 14:27 ` Jesús Vidal Panalés
2011-10-19 17:26 ` Jesús Vidal Panalés
2011-10-19 21:14 ` Jesús Vidal Panalés
2011-10-19 23:29 ` Larry Finger
2011-10-20 8:10 ` Jesús Vidal Panalés
2011-10-21 10:53 ` Rafał Miłecki
2011-10-21 12:09 ` Jesús Vidal Panalés
2011-10-21 12:14 ` Rafał Miłecki
2011-10-21 19:54 ` Jesús Vidal Panalés
2011-12-01 11:51 ` Jesús Vidal Panalés
2011-12-01 16:07 ` Larry Finger
2011-12-01 16:28 ` Jesús Vidal Panalés
2011-12-01 20:55 ` Jesús Vidal Panalés
2011-12-01 21:17 ` Larry Finger
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=4E9DC5E2.8070708@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox