NetworkManager resets regulatory domain to incorrect value

Bug #1670325 reported by Ken Sharp
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

I have added COUNTRY=GB to /etc/default/crda. During boot the RD is correctly set:

[ 28.766534] cfg80211: World regulatory domain updated:
[ 28.766541] cfg80211: DFS Master region: unset
[ 28.766543] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 28.766546] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 28.766549] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 28.766552] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[ 28.766555] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 28.766559] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 28.766561] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[ 28.766564] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[ 28.766567] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[ 28.913419] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 28.914230] ieee80211 phy0: hwaddr 00:16:44:a4:26:df, RTL8187BvE V0 + rtl8225z2, rfkill mask 2
[ 28.936096] rtl8187: Customer ID is 0x04
[ 28.947344] rtl8187: wireless switch is on
[ 28.947535] usbcore: registered new interface driver rtl8187
[ 28.949935] rtl8187 1-2:1.0 wlx001644a426df: renamed from wlan0
[ 29.093483] cfg80211: Regulatory domain changed to country: GB
[ 29.093490] cfg80211: DFS Master region: ETSI
[ 29.093492] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 29.093495] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 29.093498] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 29.093502] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 29.093505] cfg80211: (5490000 KHz - 5710000 KHz @ 160000 KHz), (N/A, 2700 mBm), (0 s)
[ 29.093507] cfg80211: (57000000 KHz - 66000000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)

But when the interface is associated it is incorrectly reset:

[ 472.548695] wlx001644a426df: authenticate with c0:3e:<cut>
[ 472.823175] wlx001644a426df: send auth to c0:3e:<cut> (try 1/3)
[ 472.824852] wlx001644a426df: authenticated
[ 472.828048] wlx001644a426df: associate with c0:3e:<cut> (try 1/3)
[ 472.831871] wlx001644a426df: RX AssocResp from c0:3e:<cut> (capab=0x1411 status=0 aid=5)
[ 472.835223] wlx001644a426df: associated
[ 472.835295] IPv6: ADDRCONF(NETDEV_CHANGE): wlx001644a426df: link becomes ready
[ 472.843644] cfg80211: Regulatory domain changed to country: DE
[ 472.843650] cfg80211: DFS Master region: ETSI
[ 472.843653] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 472.843656] cfg80211: (2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 472.843659] cfg80211: (5150000 KHz - 5250000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 472.843663] cfg80211: (5250000 KHz - 5350000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 472.843666] cfg80211: (5470000 KHz - 5725000 KHz @ 160000 KHz), (N/A, 2698 mBm), (0 s)
[ 472.843668] cfg80211: (57000000 KHz - 66000000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
[ 472.933487] wlx001644a426df: Limiting TX power to 20 (20 - 0) dBm as advertised by c0:3e:<cut>

Now, if I HUP wpa_supplicant then it correctly sets the RD again:

[ 1661.809047] wlx001644a426df: deauthenticating from c0:3e:<cut> by local choice (Reason: 3=DEAUTH_LEAVING)
[ 1661.965254] cfg80211: World regulatory domain updated:
[ 1661.965262] cfg80211: DFS Master region: unset
[ 1661.965264] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 1661.965268] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 1661.965271] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 1661.965274] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[ 1661.965277] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 1661.965280] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 1661.965283] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[ 1661.965286] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[ 1661.965288] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[ 1661.983415] cfg80211: Regulatory domain changed to country: GB
[ 1661.983422] cfg80211: DFS Master region: ETSI
[ 1661.983424] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 1661.983428] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 1661.983431] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 1661.983435] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 1661.983438] cfg80211: (5490000 KHz - 5710000 KHz @ 160000 KHz), (N/A, 2700 mBm), (0 s)
[ 1661.983440] cfg80211: (57000000 KHz - 66000000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)

But now I'm not associated with the AP.

I tried adding "iw reg set GB" to the "start" area of /etc/network/if-up.d/wpasupplicant but that didn't work. I may have put it in the incorrect place though.
I can't find an NM configuration that overrides the default file.

Is there something wrong with a script somewhere?

At this moment in time I am unaware of a workaround. I'll probably have to remove NM as usual.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: wpasupplicant 2.4-0ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-65.86-generic 4.4.49
Uname: Linux 4.4.0-65-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Mon Mar 6 11:06:24 2017
InstallationDate: Installed on 2017-02-27 (6 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Ken Sharp (kennybobs) wrote :
affects: wpa (Ubuntu) → network-manager (Ubuntu)
summary: - wpa_supplicant resets regulatory domain to incorrect value
+ NetworkManager resets regulatory domain to incorrect value
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.