[PVE-User] PVE 6, wireless and regulatory database...

[Alwin Antreich]

On Wed, May 20, 2020 at 10:58:16PM +0200, Marco Gaiarin wrote:
> Mandi! Alwin Antreich
>   In chel di` si favelave...
> 
> > Debian uses a different file name for the signature file then ubuntu.
> 
> A-HA!
> 
> 
> > You can always download the latest wireless-regdb and replace the db +
> > signature files.
> > https://wireless.wiki.kernel.org/en/developers/regulatory/wireless-regdb
> 
> I've downloaded and installed by hand ubuntu package
> (wireless-regdb_2018.05.09-0ubuntu1_all.deb) and installed flawlessy.
> 
> Now regulatory DB load:
> 
>  May 20 22:35:03 ino kernel: [    7.795925] cfg80211: Loading compiled-in X.509 certificates for regulatory database
>  May 20 22:35:03 ino kernel: [    7.816343] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
>  May 20 22:35:03 ino kernel: [    7.961683] ath: EEPROM regdomain: 0x809c
>  May 20 22:35:03 ino kernel: [    7.961684] ath: EEPROM indicates we should expect a country code
>  May 20 22:35:03 ino kernel: [    7.961685] ath: doing EEPROM country->regdmn map search
>  May 20 22:35:03 ino kernel: [    7.961686] ath: country maps to regdmn code: 0x52
>  May 20 22:35:03 ino kernel: [    7.961686] ath: Country alpha2 being used: CN
>  May 20 22:35:03 ino kernel: [    7.961687] ath: Regpair used: 0x52
>  May 20 22:35:03 ino kernel: [    7.963108] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
>  May 20 22:35:03 ino kernel: [    7.964097] ieee80211 phy0: Atheros AR9287 Rev:2 mem=0xffffa51c0d300000, irq=16
>  May 20 22:35:03 ino kernel: [    7.981453] ath9k 0000:10:00.0 wls1: renamed from wlan0
> 
> it make sense to fire up a bug in PVE BTS, to have this package added
> in repository?
It is not an issue with the package. I forgot about the alternatives in
Debian (thanks Thomas). Once you set the alternative (tool:
update-alternatives) to the regulatory.db-upstream it will be loaded
without complaining.

I suppose Debian can't switch to the signed database yet, since their
shipped kernel version might not yet know how to handle the signed
regulatory.db.

--
Cheers,
Alwin