Re: [opensuse-arm] wlan getting new hw-address every 5 minutes on raspberry pi 3

[Matthias Brugger]

On 11/09/2016 05:52 PM, Jogchum Reitsma wrote:
Hi Matthias,

Op 09-11-16 om 13:24 schreef Matthias Brugger:


On 11/08/2016 09:44 PM, Jogchum Reitsma wrote:
Hi,

After succeeding in getting wifi enabled on the pi 3 (see my previous
posting 6th of nov., 20:31 WET, and follow ups) the next problem arises:

Would you mind to document this in the wiki, so that the next person
who wants to try RPi3 doesn't have to search the list archive (or
askes the question again).
I'm not sure where to put this in the wiki. The only specific place
seems to me

https://en.opensuse.org/HCL:Raspberry_Pi3

but that's just a bit about where to get the images, and how to install
them. Seems somewhat inapporpriate to me to put is there.


As there already exists a "Tips for openSUSE Tumbleweed (upstream)" 
maybe under a new section:
Tips for non-upstream openSUSE Tumbleweed


every 5 minutes the wifi connection gets another hw-address, and hence
another ip address... Rather inconvenient.

Dmesg spits out the following:

[ 1306.573949] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1306.576314] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
[ 1306.576327] cfg80211: World regulatory domain updated:
[ 1306.576341] cfg80211:  DFS Master region: unset
[ 1306.576341] cfg80211:   (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp), (dfs_cac_time)
[ 1306.576347] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz),
(N/A, 2000 mBm), (N/A)
[ 1306.576352] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000
KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 1306.576355] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz),
(N/A, 2000 mBm), (N/A)
[ 1306.576359] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz,
160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 1306.576362] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz,
160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 1306.576366] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz),
(N/A, 2000 mBm), (0 s)
[ 1306.576370] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz),
(N/A, 2000 mBm), (N/A)
[ 1306.576373] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz),
(N/A, 0 mBm), (N/A)
[ 1307.277503] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 1622.583086] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1622.585585] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
[ 1622.585603] cfg80211: World regulatory domain updated:
[ 1622.585611] cfg80211:  DFS Master region: unset
[ 1622.585611] cfg80211:   (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp), (dfs_cac_time)
[ 1622.585618] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz),
(N/A, 2000 mBm), (N/A)
[ 1622.585623] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000
KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 1622.585626] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz),
(N/A, 2000 mBm), (N/A)
[ 1622.585630] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz,
160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 1622.585634] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz,
160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 1622.585637] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz),
(N/A, 2000 mBm), (0 s)
[ 1622.585641] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz),
(N/A, 2000 mBm), (N/A)
[ 1622.585644] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz),
(N/A, 0 mBm), (N/A)
[ 1623.287611] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 1938.580273] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 1938.587515] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
[ 1938.587571] cfg80211: World regulatory domain updated:
[ 1938.587604] cfg80211:  DFS Master region: unset
[ 1938.587604] cfg80211:   (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp), (dfs_cac_time)
[ 1938.587617] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz),
(N/A, 2000 mBm), (N/A)
[ 1938.587633] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000
KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 1938.587654] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz),
(N/A, 2000 mBm), (N/A)
[ 1938.587666] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz,
160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 1938.587676] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz,
160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 1938.587687] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz),
(N/A, 2000 mBm), (0 s)
[ 1938.587694] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz),
(N/A, 2000 mBm), (N/A)
[ 1938.587705] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz),
(N/A, 0 mBm), (N/A)
[ 1939.294771] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 2083.905735] fuse init (API version 7.23)
[ 2254.629486] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 2254.631800] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code
[ 2254.631815] cfg80211: World regulatory domain updated:
[ 2254.631823] cfg80211:  DFS Master region: unset
[ 2254.631823] cfg80211:   (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp), (dfs_cac_time)
[ 2254.631828] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz),
(N/A, 2000 mBm), (N/A)
[ 2254.631833] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000
KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 2254.631836] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz),
(N/A, 2000 mBm), (N/A)
[ 2254.631840] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz,
160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[ 2254.631844] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz,
160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[ 2254.631847] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz),
(N/A, 2000 mBm), (0 s)
[ 2254.631850] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz),
(N/A, 2000 mBm), (N/A)
[ 2254.631853] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz),
(N/A, 0 mBm), (N/A)
[ 2255.303333] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

================================================================

ever going.

What is going on here, and what can be done? Of course I did some
googling, but I didn't find anything alike...


I think the best would be to open a bug in bugzilla for this.
Maybe you want to attache the wpa_supplicant log as well. Not sure
about this, I'm rather a wifi noop.
I'll await the dialogue with Stefan before issuing a bugreport.


Thanks,
Matthias
I'm not sure where to put

What do you mean? In bugzilla?
This should be openSUSE -> openSUSE Tumbleweed
Component: Network
Hardware: aarch64
and put in the summary a prefix like "RPi3:"

Regards,
Matthias
--
To unsubscribe, e-mail: opensuse-arm+unsubscr...@opensuse.org
To contact the owner, e-mail: opensuse-arm+ow...@opensuse.org