When/where the regulatory domain is intended to be setup ? If I set up it manually with "iw reg set" this setting is lost after a reboot. So it seems that a startup script needs to set the regulatory domain after every reboot, if you want full WLAN function after a reboot.
Why is the regulatory.bin file installed in /usr/lib and iw in/usr/sbin, whereas the other parts of the framework are living in / ? If you want to mount /usr over a WLAN connection, this will restrict you to use channels 1-11 for that WLAN .
On Friday 20 February 2009 18:29:41 Markus Koßmann wrote:
When/where the regulatory domain is intended to be setup ? If I set up it manually with "iw reg set" this setting is lost after a reboot. So it seems that a startup script needs to set the regulatory domain after every reboot, if you want full WLAN function after a reboot.
Why is the regulatory.bin file installed in /usr/lib and iw in/usr/sbin, whereas the other parts of the framework are living in / ? If you want to mount /usr over a WLAN connection, this will restrict you to use channels 1-11 for that WLAN .
One other question: Are these packages installed by default if needed? I run zypper dup last week and those packages were not installed at all, it seems there are some missing dependencies...
Andreas
Am Montag, 23. Februar 2009 schrieb Andreas Jaeger:
On Friday 20 February 2009 18:29:41 Markus Koßmann wrote:
When/where the regulatory domain is intended to be setup ?
No, there is no such place yet.
If I set up it manually with "iw reg set" this setting is lost after a reboot. So it seems that a startup script needs to set the regulatory domain after every reboot, if you want full WLAN function after a reboot. Why is the regulatory.bin file installed in /usr/lib and iw in/usr/sbin, whereas the other parts of the framework are living in / ? If you want to mount /usr over a WLAN connection, this will restrict you to use channels 1-11 for that WLAN .
One other question: Are these packages installed by default if needed?
No, not yet. I've packaged them for factory only one or two weeks ago.
I run zypper dup last week and those packages were not installed at all, it seems there are some missing dependencies...
I wouldn't say missing dependencies. CRDA + wireless-regdb are needed by the kernel but I don't think we want the kernel to depend on a user space program. Furthermore the wireless satck will still be functional without CRDA. Maybe all three packages should be installed as part of the base system?
Helmut
Am Montag, 23. Februar 2009 schrieb Helmut Schaa:
I wouldn't say missing dependencies. CRDA + wireless-regdb are needed by the kernel but I don't think we want the kernel to depend on a user space program.
Couldn't that be handled like the firmware packages? Install only, if there is a driver loaded that needs it.
Furthermore the wireless satck will still be functional without CRDA.
IMHO that remaining functionality is too limited. Think about a WLAN , where the router is intentionally configured not to use channel 1-11,maybe because that range is overloaded with other WLANs. After the Upgrade to factory/11.2 you won't be able to connect to that WLAN any more without setting the regulatory domain.
Hi,
Furthermore the wireless satck will still be functional without CRDA.
IMHO that remaining functionality is too limited. Think about a WLAN , where the router is intentionally configured not to use channel 1-11,maybe because that range is overloaded with other WLANs. After the Upgrade to factory/11.2 you won't be able to connect to that WLAN any more without setting the regulatory domain.
There were allready problems with the regulatory domain before. I was not able to connect with ath5k to a network on channel 13 ...
See: https://bugzilla.novell.com/show_bug.cgi?id=392853
regards Felix Möller
Am Montag, 23. Februar 2009 schrieb Markus Koßmann:
Am Montag, 23. Februar 2009 schrieb Helmut Schaa:
I wouldn't say missing dependencies. CRDA + wireless-regdb are needed by the kernel but I don't think we want the kernel to depend on a user space program.
Couldn't that be handled like the firmware packages?
Not really, we would have to add all modaliases of all wireless modules that need crda to the package.
I guess we simply want all three packages installed by default.
Helmut
Am Montag, 23. Februar 2009 schrieb Felix Möller:
Hi,
Furthermore the wireless satck will still be functional without CRDA.
IMHO that remaining functionality is too limited. Think about a WLAN , where the router is intentionally configured not to use channel 1-11,maybe because that range is overloaded with other WLANs. After the Upgrade to factory/11.2 you won't be able to connect to that WLAN any more without setting the regulatory domain.
There were allready problems with the regulatory domain before. I was not able to connect with ath5k to a network on channel 13 ...
Right. Using channels 12 and 13 (and 14 in Japan) should be possible with factory now (if crda, wireless-regdb and iw is installed and the regulatory domain is set correctly).
Helmut
On Tuesday 24 February 2009 08:10:13 Helmut Schaa wrote:
Am Montag, 23. Februar 2009 schrieb Markus Koßmann:
Am Montag, 23. Februar 2009 schrieb Helmut Schaa:
I wouldn't say missing dependencies. CRDA + wireless-regdb are needed by the kernel but I don't think we want the kernel to depend on a user space program.
Couldn't that be handled like the firmware packages?
Not really, we would have to add all modaliases of all wireless modules that need crda to the package.
I guess we simply want all three packages installed by default.
What about making them dependend by wireless-tools? Please discuss with Coolo what's best here. He can also make the changes to install them by default.
Andreas
-
Andreas Jaeger -
Felix Möller -
Helmut Schaa -
Markus Koßmann