Opened 5 years ago

Last modified 5 years ago

#13054 new defect

Recent trunk - setting regulatory did not work

Reported by: anonymous Owned by: developers
Priority: highest Milestone: Chaos Calmer 15.05
Component: packages Version: Trunk
Keywords: Cc:


I changed the regulatory in luci and saved&apply. It did not seem to changed anything. So i reboot with luci. In the wireless settings it still show after reboot the changed regulatory settings, but an "iw reg get" shows the default regulatory. Also in dmesg it did not set anywhere the changed regulatory.

I cant set the channel i need and so cant setup my wireless network.

Attachments (0)

Change History (4)

comment:1 Changed 5 years ago by anonymous

Not a dev, but you have to supply more information or your ticket will be closed.

If the device in question is from Netgear with Atheros chipset you might experience issues similar too
If your problem is similar then your bugfix is to compile an image yourself or try other OpenWRT based images from european sources where that regulation doesnt apply. Official OpenWRT images wouldnt support these circumventions of (incorrect) hardware settings

comment:2 Changed 5 years ago by anonymous

Its a self compiled image. The device is an atheros 93xx with 1tx and 1rx (150mbit). Ath-regdomain hack is activated. Luci is been compiled into the image.

Sorry, forgot to write this down.

What you mean is something other. When you did not have ath-regdomain enabled, then you can see in the logfiles, that it change the regdulatory. But the driver did not accept the new area and iw show same possible channels/power like before. But an iw reg get shows, when i remember right, the new regulatory.

my problem is as told, that it dont care about the settings in luci and also after reboot nothing changes. it just did not try to set them. When i set regulatory with iw command, then everything is fine. i already wrote this above. so it could not be, that i could have forget to enable the ath regdomain.

comment:3 Changed 5 years ago by anonymous

try r35752 ( svn update -r 35752 )

comment:4 Changed 5 years ago by anonymous

I finaly find out when this error come and can reproduce it all the time.

The trunk i used now is r35900. It does not seem to have any change since many versions.

When you set regulatory to something else then in the Atheros eeprom AND the interface is not enabled(after fist configuration), it did not change it. Also after a reboot, when the interface stay disabled, it stay at the wrong regulatory and dont care about what is been set in the wireles setting.

When it get enabled, first THEN it changes the regulatory!

The problem is, that you cant set the correct channel FIRST before enable the inferface, because it is still not available in the list (because the eeprom-regulatory did not provide the needed channel).

Could a dev (nbd?) quickly correct this error?


Add Comment

Modify Ticket

as new .

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.