El 18/10/11 20:30, Larry Finger escribió:
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.
Ok, i thought that "reply to the list" on thunderbird was working
fine...sudo -s
sorry
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
Uhmmm....my bcm4301 is not sending any packets. In fact, using kismet if
i execute dmesg i don't see any message trying to connect on the
output...there is only inizitialization of the driver.
_______________________________________________
b43-dev mailing list
b43-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/b43-dev
