Hi,
On Tuesday, 23 January 2007 20:59, Larry Finger wrote:
> Rafael J. Wysocki wrote:
> > Hi,
> >
> > First, thanks a lot for your work on the driver.
> >
> > Now, my observations: With the patch from
> >
> > https://lists.berlios.de/pipermail/bcm43xx-dev/2007-January/003484.html
> >
> > and the patch radio_enable_2.6.20 from
> >
> > ftp://lwfinger.dynalias.org/patches
> >
> > on top of 2.6.20-rc5 (x86_64), the bcm4311 card in my HPC nx6325 partially
> > works (I use the ieee80211softmac version of the driver). Namely,
> > everything
> > seems to be going on well and and interrupts are coming, I can run
> > "iwlist eth2 scan" and it reports something like the following:
> >
> > eth2 Scan completed :
> > Cell 01 - Address: 00:13:46:85:46:F9
> > ESSID:"[edited]"
> > Protocol:IEEE 802.11bg
> > Mode:Master
> > Channel:6
> > Encryption key:on
> > Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
> > 11 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
> > 48 Mb/s; 54 Mb/s
> > Quality=82/100 Signal level=-71 dBm Noise level=-68
> > dBm
> > IE: WPA Version 1
> > Group Cipher : WEP-40
> > Pairwise Ciphers (2) : WEP-40 TKIP
> > Authentication Suites (1) : PSK
> > Extra: Last beacon: 280ms ago
> >
> > but strangely enough this is someone else's access point, not mine.
> > My access point is a D-Link DI-624+ router, with different ESSID and
> > different MAC. It stands just next to my machine and yet it is not
> > detected
> > (it is detected by my second maching with bcm4306, though, and works with
> > it).
>
> First of all, please don't bother editing out the ESSID's from your postings.
> That information can
> be deduced by anyone in your vicinity very quickly, even if your ESSID is
> hidden.
This isn't mine, as I said, and that's why it's been edited. Well, I should
have edited the MAC too, but that isn't so easy to google out. ;-)
[--snip--]
> > The first problem is the D-Link router not being detected, but I think
> > someone
> > else has already reported similar problems with a D-Link access point, so it
> > seems there's something wrong with the bcm4311 vs D-Link APs in general.
>
> You might try using kismet or ethereal on another wireless device to capture
> the traffic from the 4311.
Yes, that sounds promising.
In the meantime I carried out another experiment. I found an unencrypted AP
close
to me and tried to associate with it. That seemed to work, so I configured the
interface manually with ifconfig and ran tcpdump on it. Then I received some
traffic from that network and figured out from it that there was the IP
192.168.1.101
in there, so I reconfigured my interface with the address 192.168.1.15 and tried
to ping the other host. There was no reply (Destination Host Unreachable), so
I started a network monitor (gkrellm) and ran a continuous ping from the
wireless interface. Then, no transmits were reported by the monitor.
So, it seems, the card is still unable to transmit, although it evidently
receives packets.
> > Of course the second one is the bit rates, but I have no idea if they are
> > related to each other.
>
> The bit rate output is a bug. Mine does it too - I'll find the problem.
Ah, I see there's a patch already. I'll try it and report back.
Greetings,
Rafael
--
If you don't have the time to read,
you don't have the time or the tools to write.
- Stephen King
_______________________________________________
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
