On Thursday 17 August 2006 19:00, Larry Finger wrote:
The last ping before I took this output took 333 ms.
Larry
larrylap:~ # cat /debug/bcm43xx/eth1/tx_status
Last 100 logged xmitstatus blobs (Latest first):
0x00: cookie: 0xb182, flags: 0x01, cnt1: 0x00, cnt2: 0x01, seq:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Larry Finger wrote:
Kevin Crocker (teq) wrote:
Hi,
Yes, I have one of these devices in my laptop.
Yes, I want to get it to work.
03:02.0 Network controller: Broadcom Corporation BCM4306
802.11b/g
Wireless LAN Controller (rev 02)
03:02.0
On Friday 18 August 2006 13:52, Michael Buesch wrote:
Hm, I don't see anything special.
There's only one packet retried once, but even that succeed after the retry.
I would say that's normal noise.
So, what's going on there? Did you try with another card and driver, but with
the
same AP?
Hi guys,
Does bcm43xx set a flag or use some statistic as an indicator for an
802.11 frame with a bad or corrupted header? I am referring to only
the header and not the entire frame. Thanks.
--CLW
--
**
Clifton L. Watson, Ph.D.
On Fri, 2006-08-18 at 08:01 -0400, Kevin Crocker (teq) wrote:
eth1 IEEE 802.11b/g ESSID: off/any Nickname:Broadcom 4306
Mode: Managed Frequency=2.437 GHz Access Point: Invalid
Bit Rate=1 Mb/s
RTS thr: off Fragment thr:off
Encryption key: off
Try this exact sequence of commands:
rmmod bcm43xx
modprobe bcm43xx
ip route flush all
ip address flush dev eth1
ip link set dev eth1 up
ip address add dev eth1 local 192.168.1.2 peer 192.168.1.1
ip route add default via 192.168.1.1
iwlist eth1 scanning # This is important! It
[EMAIL PROTECTED] wrote:
On Fri, 2006-08-18 at 08:01 -0400, Kevin Crocker (teq) wrote:
eth1 IEEE 802.11b/g ESSID: off/any Nickname:Broadcom 4306
Mode: Managed Frequency=2.437 GHz Access Point: Invalid
Bit Rate=1 Mb/s
RTS thr: off Fragment thr:off
Michael Buesch wrote:
On Friday 18 August 2006 13:52, Michael Buesch wrote:
Hm, I don't see anything special.
There's only one packet retried once, but even that succeed after the retry.
I would say that's normal noise.
So, what's going on there? Did you try with another card and driver, but
On Friday 18 August 2006 22:05, Larry Finger wrote:
I will set up a configuration that lets me capture packets in monitor mode
using kismet and send you the capture file. The host I will be using is
for the capture is rather low powered, so it doesn't have X, but it makes a
good file server.
ip link set dev eth1 up
(bcm43xx: Card IRQ register not responding. Giving up. SIOCSIFFLAGS:
No such device)
That is clearly a bug in your kernel's bcm43xx driver. The developers
here might be interested in your dmesg log, I don't know.
You might try the latest driver: git clone
On Friday 18 August 2006 23:41, Ivan Matveich wrote:
ip link set dev eth1 up
(bcm43xx: Card IRQ register not responding. Giving up. SIOCSIFFLAGS:
No such device)
That is clearly a bug in your kernel's bcm43xx driver. The developers
here might be interested in your dmesg log, I don't
11 matches
Mail list logo
