Re: Operation wpa_driver_wext_set_countermeasures not supported

2007-12-29 Thread David Woodhouse
On Tue, 2007-12-18 at 12:36 +0100, Robert Allerstorfer wrote: done. I have recompiled and replaced the original b43.ko from 'kernel-2.6.23.9-90.fc8.src.rpm', with the modified 'phy.c' [if (B43_DEBUG) changed to if (0) on line 741]. Using Fedora's build mechanism, I had to built the entire

Re: Operation wpa_driver_wext_set_countermeasures not supported

2007-12-18 Thread Michael Buesch
On Tuesday 18 December 2007 12:36:02 Robert Allerstorfer wrote: On Mon, 17 Dec 2007, 15:14 GMT+01 Michael Buesch wrote: Please test what I suggested. done. I have recompiled and replaced the original b43.ko from 'kernel-2.6.23.9-90.fc8.src.rpm', with the modified 'phy.c' [if (B43_DEBUG)

Re: Operation wpa_driver_wext_set_countermeasures not supported

2007-12-17 Thread Johannes Berg
ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x04, vendor 0x4243) ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x05, vendor 0x4243) MAC core ID MAC core revision According to

Re: Operation wpa_driver_wext_set_countermeasures not supported

2007-12-17 Thread Michael Buesch
On Monday 17 December 2007 02:46:29 Robert Allerstorfer wrote: On Thu, 13 Dec 2007, 00:20 GMT+01 Michael Buesch wrote: On Wednesday 12 December 2007 23:48:10 Robert Allerstorfer wrote: Before starting wpa_supplicant: [EMAIL PROTECTED] ~]# dmesg | egrep 'b43|ssb|wlan0|wmaster0' ssb:

Re: Operation wpa_driver_wext_set_countermeasures not supported

2007-12-17 Thread Robert Allerstorfer
On Mon, 17 Dec 2007, 10:05 GMT+01 Johannes Berg wrote: ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x05, vendor 0x4243) MAC core ID MAC core revision The MAC core revision is =5 so you need b43. Thank you for making this

Re: Operation wpa_driver_wext_set_countermeasures not supported

2007-12-17 Thread Robert Allerstorfer
On Mon, 17 Dec 2007, 11:00 GMT+01 Michael Buesch wrote: On Monday 17 December 2007 02:46:29 Robert Allerstorfer wrote: The strange thing is that the b43-phy0 debug: !WARNING!... line disappeared from the dmesg output after I replaced ssb.ko by a self-compiled version (and - of course -

Re: Operation wpa_driver_wext_set_countermeasures not supported

2007-12-17 Thread Michael Buesch
On Monday 17 December 2007 13:49:00 Robert Allerstorfer wrote: On Mon, 17 Dec 2007, 11:00 GMT+01 Michael Buesch wrote: On Monday 17 December 2007 02:46:29 Robert Allerstorfer wrote: The strange thing is that the b43-phy0 debug: !WARNING!... line disappeared from the dmesg output after I

Re: Operation wpa_driver_wext_set_countermeasures not supported

2007-12-17 Thread Robert Allerstorfer
On Mon, 17 Dec 2007, 13:53 GMT+01 Michael Buesch wrote: On Monday 17 December 2007 13:49:00 Robert Allerstorfer wrote: After rebooting several times, the output of dmesg | egrep 'b43|ssb|wlan0|wmaster0' sometimes contains such a warning line and sometimes it doesn't. Expected. So try the

Re: Operation wpa_driver_wext_set_countermeasures not supported

2007-12-17 Thread Michael Buesch
On Monday 17 December 2007 14:43:37 Robert Allerstorfer wrote: On Mon, 17 Dec 2007, 13:53 GMT+01 Michael Buesch wrote: On Monday 17 December 2007 13:49:00 Robert Allerstorfer wrote: After rebooting several times, the output of dmesg | egrep 'b43|ssb|wlan0|wmaster0' sometimes contains

Re: Operation wpa_driver_wext_set_countermeasures not supported

2007-12-17 Thread Robert Allerstorfer
On Mon, 17 Dec 2007, 14:46 GMT+01 Michael Buesch wrote: On Monday 17 December 2007 14:43:37 Robert Allerstorfer wrote: But shouldn't setting/unsetting B43_DEBUG only affect the verbosity level of the kernel messages, but not change any functionality? No. Aha, reading the corresponding

Re: Operation wpa_driver_wext_set_countermeasures not supported

2007-12-17 Thread Michael Buesch
On Monday 17 December 2007 15:09:32 Robert Allerstorfer wrote: On Mon, 17 Dec 2007, 14:46 GMT+01 Michael Buesch wrote: On Monday 17 December 2007 14:43:37 Robert Allerstorfer wrote: But shouldn't setting/unsetting B43_DEBUG only affect the verbosity level of the kernel messages, but not

Re: Operation wpa_driver_wext_set_countermeasures not supported

2007-12-17 Thread Holger Schurig
On Monday 17 December 2007 15:09:32 Robert Allerstorfer wrote: But shouldn't setting/unsetting B43_DEBUG only affect the verbosity level of the kernel messages, but not change any functionality? No. So that means enabling Broadcom 43xx debugging may disable functionality? You're confused

Re: Operation wpa_driver_wext_set_countermeasures not supported

2007-12-17 Thread Mark Hagger
On Mon, 2007-12-17 at 15:28 +0100, Holger Schurig wrote: Note that there might be rare situations where turning on debug messages change functionality: in the case of race-conditions. I'll leave the explanation of this to your google skills :-) It is of course a, shall we say, not

Re: Operation wpa_driver_wext_set_countermeasures not supported

2007-12-16 Thread Robert Allerstorfer
On Thu, 13 Dec 2007, 00:20 GMT+01 Michael Buesch wrote: On Wednesday 12 December 2007 23:48:10 Robert Allerstorfer wrote: Before starting wpa_supplicant: [EMAIL PROTECTED] ~]# dmesg | egrep 'b43|ssb|wlan0|wmaster0' ssb: SPROM revision 1 detected. ssb: Sonics Silicon Backplane found on PCI

Re: Operation wpa_driver_wext_set_countermeasures not supported

2007-12-13 Thread Holger Schurig
What is reason 3 for disassociating? WLAN_REASON_DEAUTH_LEAVING = 3, But I don't know what LEAVING means in this case. If a client decides to roam, it can (not a must, after all the client can be in reception hole) send a de-auth mesage to the old AP.

Operation wpa_driver_wext_set_countermeasures not supported

2007-12-12 Thread Robert Allerstorfer
Hi, I have just updated the kernel of Fedora 8 running on my iBook G4 from the latest official one (2.6.23.8-63) to the latest testing version (2.6.23.9-90). This solved all the ioctl[SIOCSIWAUTH]: Operation not supported errors which occured after wpa_supplicant issued the

Re: Operation wpa_driver_wext_set_countermeasures not supported

2007-12-12 Thread Michael Buesch
On Wednesday 12 December 2007 23:48:10 Robert Allerstorfer wrote: Before starting wpa_supplicant: [EMAIL PROTECTED] ~]# dmesg | egrep 'b43|ssb|wlan0|wmaster0' ssb: SPROM revision 1 detected. ssb: Sonics Silicon Backplane found on PCI device 0001:10:12.0 b43-phy0: Broadcom 4306 WLAN found