Oops. I clicked "Reply" instead of "Reply to all". Forwarded to list.
---------- Forwarded message ----------
From: Stefanik Gábor <[EMAIL PROTECTED]>
Date: Mon, Mar 17, 2008 at 3:40 PM
Subject: Re: Asus WL-138G V2 (BCM4318 non-E rev02) scans but doesn't
associate using b43 driver, works with bcm43xx
To: Johannes Berg <[EMAIL PROTECTED]>
Something I forgot: I'm using OpenSUSE.
Also, I think it's more important to solve the no-transmit problem than the
channel 14 one, so let's not digress too much.
Some more comments are in the text.
On Mon, Mar 17, 2008 at 3:18 PM, Johannes Berg <[EMAIL PROTECTED]>
wrote:
>
> > With the old bcm43xx (softmac) driver, iwconfig returns "Operation not
> > permitted" for "iwconfig <card> channel 14". Kismet's backend process
> > crashes if I set its channel hopping range to include channel 14.
> > NetworkManager and iwlist scan doesn't scan on ch14. Channels 12 and
> > 13 are not affected, only the Japanese channel 14. Channels 1 through
> > 13 work fine, I can scan, associate, transmit, receive, even monitor
> > mode works.
>
> To be honest, both bcm43xx and ieee80211softmac have been removed from
> the kernel so nobody cares about channel 14 not being available there.
>
I know, just I wrote it down to be comparable to the new driver.
>
> > When mac80211 (or cfg80211 on wireless-testing) is loaded without
> > ieee80211_regdom, iwconfig goes up to channel 11, after that,
> > "Operation not permitted". Kismet doesn't crash though, it just prints
> > an error when it tries to switch to a channel over 11. NetworkManager
> > and iwlist scan skips channels 12, 13 and 14. Loading {mac|cfg}80211
> > with ieee80211_regdom=64 (which is Japan AFAIK, so it should allow 14
> > channels) makes channels 12 and 13 work to some extent, but not
> > channel 14.
>
> You have to load cfg80211 with ieee80211_regdom=JP, it's a character
> string now, using =64 will just get you US again and even 12 and 13
> won't work. I just tried, and channel 14 works flawlessly.
>
I tested with 2.6.25-rc4, so it's 64 there, yet it only went up to channel
13.
>
> > Iwconfig works up to ch13, while ch14 gives "Operation not permitted".
>
> You get operation not permitted when your configured regdomain doesn't
> include the channel you want. I also don't believe you that you get
> channels 12 and 13 when loading cfg80211 with ieee80211_regdom=64, that
> will get you only channels 1-11.
>
Again, in 2.6.25-rc4, the one that gets the parameter is mac80211, and the
value is 64. I remember receiving beacons on channel 12 (but obviously no
transmit).
>
> > Kismet goes into channel 12 and 13 nicely, but crashes on channel 14.
>
> Sounds like a kismet bug.
>
I don't know, as other channel hoppers (airodump-ng, for example) behave the
same way.
>
> > The different errors of Kismet suggest a regional lockout on the
> > hardware, which is likely specific to this card, and not present on
> > non-Asus 4318s. Maybe there is a protection/"cop" chip connected to
> > the radio, I don't know as I haven't removed the cover of the radio.
>
> Nope. There is no such thing. You cannot get an -EPERM error from the
> b43 driver.
I am not sure if it was "Operation not permitted", it might have been a
hardware-related error or "Operation not supported".
>
> johannes
>
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
