Re: [PATCH]: bcm43xx-d80211: fix hwcrypto issues (mcast)
On Fri, Nov 17, 2006 at 11:35:54AM +0100, Andreas Schwab wrote: Benjamin Herrenschmidt [EMAIL PROTECTED] writes: Well, the latest released version (fwcutter-005) contains a huge list of ... v3 URLs :-) Only 2 v4 in there. I'll check SVN. Still the same. One of them does not exist, the other one requires Javascript! MacOS X 10.4.8 Update for Intel [1] has AppleAirportBrcm4311 E99AD02FDD7699FA52F0B9153C8411C8 4.80.46.0 big-endian, supported in fwcutter-svn It's a 200MB download for just the one file, but w3m seems to be able to process it OK, so I assume it doesn't require Javascript. [1] http://www.apple.com/support/downloads/macosx1048updateintel.html -- --- Paul TBBle Hampson, B.Sc, LPI, MCSE On-hiatus Asian Studies student, ANU The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361) [EMAIL PROTECTED] Of course Pacman didn't influence us as kids. If it did, we'd be running around in darkened rooms, popping pills and listening to repetitive music. -- Kristian Wilson, Nintendo, Inc, 1989 License: http://creativecommons.org/licenses/by/2.1/au/ --- pgpkwvBXHFP3Y.pgp Description: PGP signature
Re: [PATCH]: bcm43xx-d80211: fix hwcrypto issues (mcast)
On Fri, Nov 17, 2006 at 06:46:29PM +1100, Benjamin Herrenschmidt wrote: On Thu, 2006-11-16 at 15:07 +0100, Michael Buesch wrote: This fixes various bcm43xx-d80211 hwcrypto issues, which mainly prevented mcast frames from being decrypted properly. This is mostly a rewrite of the key managing code. Note that after this patch v3 firmware is no longer supported. So what is the solution for Apple machines owner who only get a v3 firmware from Apple ? I remember you telling me the answer on irc but I wanted to make it public :-) Some web site we can d/l the windows updates and extract the FW ? http://bcm43xx.spugna.org/index.php?topic=141.msg517 provides the following links to 4.80.46.0: http://www.i-nz.net/files/perm/AppleAirPortBrcm4311.tar.gz http://www.i-nz.net/files/perm/bcmwl5-win32.tar.gz -- --- Paul TBBle Hampson, B.Sc, LPI, MCSE On-hiatus Asian Studies student, ANU The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361) [EMAIL PROTECTED] Of course Pacman didn't influence us as kids. If it did, we'd be running around in darkened rooms, popping pills and listening to repetitive music. -- Kristian Wilson, Nintendo, Inc, 1989 License: http://creativecommons.org/licenses/by/2.1/au/ --- pgpdU5wbcGLV6.pgp Description: PGP signature
Re: [PATCH, RFT]: Fix bcm43xx-d80211 hwcrypto
On Wed, Nov 15, 2006 at 07:48:08PM +0100, Michael Buesch wrote: Please test if this fixes hwcrypto. Note that we will require v4 firmware with this patch. I will remove v3 firmware support, because it's _really_ a huge pain to support both firmware versions. If someone wants to have v3 support, please fork my tree. Or alternatively simply install v4 firmware, which is a lot easier. ;) Tested fine for me with both TKIP sw encryption and WEP-104 hw encryption, on v4 firmware. (Without applying today's new wireless-dev patches) -- --- Paul TBBle Hampson, B.Sc, LPI, MCSE On-hiatus Asian Studies student, ANU The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361) [EMAIL PROTECTED] Of course Pacman didn't influence us as kids. If it did, we'd be running around in darkened rooms, popping pills and listening to repetitive music. -- Kristian Wilson, Nintendo, Inc, 1989 License: http://creativecommons.org/licenses/by/2.1/au/ --- - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: bcm43xx-d80211 broadcast reception with WPA
On Wed, Nov 15, 2006 at 01:29:59AM +1100, Paul TBBle Hampson wrote: Just to summarise results so far: (Current version) bcm43xx-d80211 w/v3 firmware and TKIP: Garbled broadcast RX bcm43xx-d80211 w/v4 firmware and TKIP: Garbled broadcast RX bcm43xx-d80211 w/v4 firmware and WEP-104: Correct broadcast RX (version from wireless-dev before October 23rd, unsure of exact date) bcm43xx (softmac) w/v3 firmware and TKIP: Correct broadcast RX Still to test: bcm43xx-d80211 w/v3 firmware and WEP-104 bcm43xx-d80211 w/v3 firmware and WEP-104: Garbled _everything_ RX Of course, that's to be expected. WEP only uses broadcast keys, and we knew they were failing in software mode. -- --- Paul TBBle Hampson, B.Sc, LPI, MCSE On-hiatus Asian Studies student, ANU The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361) [EMAIL PROTECTED] Of course Pacman didn't influence us as kids. If it did, we'd be running around in darkened rooms, popping pills and listening to repetitive music. -- Kristian Wilson, Nintendo, Inc, 1989 License: http://creativecommons.org/licenses/by/2.1/au/ --- - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: bcm43xx-d80211 broadcast reception with WPA
On Sun, Nov 12, 2006 at 09:34:27AM +0100, Michael Buesch wrote: On Sunday 12 November 2006 02:24, Paul TBBle Hampson wrote: On Sat, Nov 11, 2006 at 04:07:05PM +0100, Michael Buesch wrote: On Saturday 11 November 2006 07:32, Paul Hampson wrote: Michael Buesch mb at bu3sch.de writes: On Thursday 09 November 2006 23:23, Paul Hampson wrote: I've been backporting the bcm43xx-d80211 driver to whatever the released 2.6 kernel was using the rt2x00 project's d80211 stack (equivalent to current wireless-dev but with a workaround for not having a ieee80211_dev pointer and still using the _tfm interface instead of the _cypher interface.) As of last night's wireless-dev tree bcm43xx, everything seems to be operating fine except incoming broadcast traffic is coming in 14 bytes too long and scrambled. I presume this means it's not decrypting properly... It sounds like a bug in the hardware decryption setup. Are you using TKIP or not? Yes, it's using TKIP. The router docs and the loading of the tkip module when I use the softmac driver agree on this. TKIP is still software encryption. Did you try with WPA-AES, for example, which is hardware encryption? I've just tried with WEP-104, which reports hardware encryption for all four keys. Ah, and also note that you _need_ firmware from a v4 binary driver to have hardware encryption with bcm43xx. Just to summarise results so far: (Current version) bcm43xx-d80211 w/v3 firmware and TKIP: Garbled broadcast RX bcm43xx-d80211 w/v4 firmware and TKIP: Garbled broadcast RX bcm43xx-d80211 w/v4 firmware and WEP-104: Correct broadcast RX (version from wireless-dev before October 23rd, unsure of exact date) bcm43xx (softmac) w/v3 firmware and TKIP: Correct broadcast RX Still to test: bcm43xx-d80211 w/v3 firmware and WEP-104 I also tried looking at how the two drivers I've got here are clearing their keys and comparing them to the bcm specs, and there's nothing obviously wrong that I can see. Sadly I can't compare the drivers directly since one is using the v3 specs and one the v4 specs... -_- And to top it off, current wireless-dev's softmac bcm43xx driver doesn't build against 2.6.18, and I'm not yet motivated into munging it into doing so, unless it will have diagnostic advantage to this situation. (It'll require also building a new ieee80211softmac at least) -- --- Paul TBBle Hampson, B.Sc, LPI, MCSE On-hiatus Asian Studies student, ANU The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361) [EMAIL PROTECTED] Of course Pacman didn't influence us as kids. If it did, we'd be running around in darkened rooms, popping pills and listening to repetitive music. -- Kristian Wilson, Nintendo, Inc, 1989 License: http://creativecommons.org/licenses/by/2.1/au/ --- pgpjEPc1lK5rF.pgp Description: PGP signature
Re: bcm43xx-d80211 broadcast reception with WPA
On Sat, Nov 11, 2006 at 04:07:05PM +0100, Michael Buesch wrote: Please _don't_ remove CCs. Sorry, I was sending via the gmane web interface, I guess it doesn't honour CCs. This one's via muttng's NNTP support to gmane, so I _think_ it's going to the right places. On Saturday 11 November 2006 07:32, Paul Hampson wrote: Michael Buesch mb at bu3sch.de writes: On Thursday 09 November 2006 23:23, Paul Hampson wrote: I've been backporting the bcm43xx-d80211 driver to whatever the released 2.6 kernel was using the rt2x00 project's d80211 stack (equivalent to current wireless-dev but with a workaround for not having a ieee80211_dev pointer and still using the _tfm interface instead of the _cypher interface.) As of last night's wireless-dev tree bcm43xx, everything seems to be operating fine except incoming broadcast traffic is coming in 14 bytes too long and scrambled. I presume this means it's not decrypting properly... It sounds like a bug in the hardware decryption setup. Are you using TKIP or not? Yes, it's using TKIP. The router docs and the loading of the tkip module when I use the softmac driver agree on this. TKIP is still software encryption. Did you try with WPA-AES, for example, which is hardware encryption? The router here only supports TKIP that I can see. There's another network I'll be on on Monday night which I might be able to throw into WPA2 mode... In fact, I was there yesterday and couldn't even get a DHCP IP address, but didn't have the time to diagnose it. The problem might be that the card tries to decrypt mcast frames in the crypto hardware, although we did not set a key. So it uses a random key to decrypt. That obviously results in crap. Eww, yuck. -- --- Paul TBBle Hampson, B.Sc, LPI, MCSE On-hiatus Asian Studies student, ANU The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361) [EMAIL PROTECTED] Of course Pacman didn't influence us as kids. If it did, we'd be running around in darkened rooms, popping pills and listening to repetitive music. -- Kristian Wilson, Nintendo, Inc, 1989 License: http://creativecommons.org/licenses/by/2.1/au/ --- - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html