Wifi problem since 4.14.x

Hikarou · 2017-12-10 14:38:01

Hello everyone,

Long time lurker, first time poster.
Thanks for all the tips and tricks found on this forum and especially on the wiki, now I have a problem without a solution.
Since I upgraded linux to 4.14.x I have a problem with my wireless card.
I could connect to my wireless router, but couldn't connect to the internet.
I happens that it only fetched an IPv6 address and therefore I couldn't access to a major part of Internet.
I split my wireless router in two to have access as I would either to 2.4Ghz or 5Ghz channel.
When I connect to the 2.4Ghz channel, I fetch both IPv4 and IPv6 addresses and can freely surf.
With the 5Ghz channel, same problem : Only IPv6.
It doesn't bother me much going through 2.4Ghz at home since I could split on the router myself, but at the university, I can't choose and if the band steering is ON, it would probably try to connect me to the 5Ghz channel.
So does anyone have a solution, either to get me a correct IPv4 through the 5Ghz channel or, meanwhile I still have the problem, ask my wireless card to fetch only on the 2.4Ghz channel ?

My hardware : (lspci)

03:00.0 Network controller: Intel Corporation Wireless 7260 (rev 83)

Which uses the iwlwifi module
I tried both solutions on https://wiki.archlinux.org/index.php/Wi … on#iwlwifi
I didn't try the power saving solution, since I have a connection and at least an IPv6 address.

Thanks in advance for your answers

Hikarou

shihjay2 · 2017-12-10 16:59:35

I have the same issue with the Intel 7265 AC chip. I found that downgrading NetworkManager to 1.8.5dev allows me to connect on the 5Ghz channel. I'm not sure why since it only occurred after upgrading the Linux kennel to 4.14. I figured it was a temporary solution until one figured out the problem which I think is kernel related.

Head_on_a_Stick · 2017-12-10 19:28:37

@both: please attempt to connect manually and post any error messages here verbatim.

Please also check the dmesg(8) output, I have vague memories of transient firmware problems with Intel cards but I may have eaten too much cheese last night

Hikarou · 2017-12-10 23:45:19

Thanks for both your answers.
For the dmesg. Both using a 2.4Ghz channel and 5Ghz they have the same output :
Where XX:XX:XX:XX:XX:XX is the MAC address of the 2.4 GHz and YY:YY:YY:YY:YY:YY the MAC address of the 5Ghz

Deconnection from 2.4 to 5

[  808.477811] wlp3s0: deauthenticating from XX:XX:XX:XX:XX:XX by local choice (Reason: 3=DEAUTH_LEAVING)
[  808.502687] wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)
[  808.505316] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  808.580944] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  816.037477] wlp3s0: authenticate with a8:d3:f7:bb:00:81
[  816.040259] wlp3s0: send auth to YY:YY:YY:YY:YY:YY (try 1/3)
[  816.042370] wlp3s0: authenticated
[  816.047641] wlp3s0: associate with YY:YY:YY:YY:YY:YY (try 1/3)
[  816.049977] wlp3s0: RX AssocResp from YY:YY:YY:YY:YY:YY (capab=0x11 status=0 aid=5)
[  816.051106] wlp3s0: associated
[  816.051139] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready

And from 5 to 2.4

[  989.548824] wlp3s0: deauthenticating from YY:YY:YY:YY:YY:YY by local choice (Reason: 3=DEAUTH_LEAVING)
[  989.635532] wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)
[  989.638095] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  989.679116] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  992.957622] wlp3s0: authenticate with XX:XX:XX:XX:XX:XX
[  992.960129] wlp3s0: send auth to XX:XX:XX:XX:XX:XX (try 1/3)
[  992.963077] wlp3s0: authenticated
[  992.965877] wlp3s0: associate with XX:XX:XX:XX:XX:XX (try 1/3)
[  992.971697] wlp3s0: RX AssocResp from XX:XX:XX:XX:XX:XX (capab=0x411 status=0 aid=1)
[  992.973222] wlp3s0: associated
[  992.973258] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready

I usually use NetworkManager.
To connect manually, I used wpa_supplicant with this

# wpa_supplicant -B -i wlp3s0 -c <(wpa_passphrase ZZZZZZZZZZZZ AAAAAAAAAAAAA)

And got exactly the same output and same reaction.

Should I try with the iw module ?

Now, I came back from my girlfriend's house and could connect to her 5Ghz channel... I'm quite confused now...
I must say that all my others devices at home are connected through the 5Ghz channel and have both IPs...
I'll take another look tomorrow at university for further output.

Hikarou · 2017-12-11 09:22:17

Tried at the university... And it works on the 5Ghz channel...
I'm quite lost right now...
I'll look at my Router's configuration, as soon as I can.
Sorry for wasting your time.

For comparison, at the university, the dmesg :
XX:XX:XX:XX:XX:XX => 5Ghz channel
YY:YY:YY:YY:YY:YY => 2.4Ghz channel

[   10.083646] wlp3s0: authenticate with XX:XX:XX:XX:XX:XX
[   10.086603] wlp3s0: send auth to XX:XX:XX:XX:XX:XX (try 1/3)
[   10.087317] wlp3s0: authenticated
[   10.090009] wlp3s0: associate with XX:XX:XX:XX:XX:XX (try 1/3)
[   10.091533] wlp3s0: RX AssocResp from XX:XX:XX:XX:XX:XX (capab=0x111 status=0 aid=13)
[   10.092597] wlp3s0: associated
[   10.092621] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[   10.128541] wlp3s0: Limiting TX power to 17 dBm as advertised by XX:XX:XX:XX:XX:XX
[  112.304699] wlp3s0: disconnect from AP XX:XX:XX:XX:XX:XX for new auth to 78:ba:f9:d8:8a:a1
[  112.308518] wlp3s0: authenticate with YY:YY:YY:YY:YY:YY
[  112.312010] wlp3s0: send auth to YY:YY:YY:YY:YY:YY (try 1/3)
[  112.316209] wlp3s0: authenticated
[  112.318347] wlp3s0: associate with YY:YY:YY:YY:YY:YY (try 1/3)
[  112.320836] wlp3s0: RX ReassocResp from YY:YY:YY:YY:YY:YY (capab=0x421 status=17 aid=0)
[  112.320838] wlp3s0: 78:ba:f9:d8:8a:a1 denied association (code=17)
[  112.567998] wlp3s0: authenticate with XX:XX:XX:XX:XX:XX
[  112.570775] wlp3s0: send auth to XX:XX:XX:XX:XX:XX (try 1/3)
[  112.571736] wlp3s0: authenticated
[  112.575018] wlp3s0: associate with XX:XX:XX:XX:XX:XX (try 1/3)
[  112.576497] wlp3s0: RX AssocResp from XX:XX:XX:XX:XX:XX (capab=0x111 status=0 aid=13)
[  112.578000] wlp3s0: associated
[  112.592856] wlp3s0: Limiting TX power to 17 dBm as advertised by XX:XX:XX:XX:XX:XX
[  282.141651] wlp3s0: disconnect from AP XX:XX:XX:XX:XX:XX for new auth to YY:YY:YY:YY:YY:YY
[  282.150832] wlp3s0: authenticate with YY:YY:YY:YY:YY:YY
[  282.153744] wlp3s0: send auth to YY:YY:YY:YY:YY:YY (try 1/3)
[  282.158749] wlp3s0: authenticated
[  282.165352] wlp3s0: associate with YY:YY:YY:YY:YY:YY (try 1/3)
[  282.173382] wlp3s0: RX ReassocResp from YY:YY:YY:YY:YY:YY (capab=0x421 status=17 aid=0)
[  282.173386] wlp3s0: 78:ba:f9:d8:8a:a1 denied association (code=17)
[  282.386879] wlp3s0: authenticate with XX:XX:XX:XX:XX:XX
[  282.389603] wlp3s0: send auth to XX:XX:XX:XX:XX:XX (try 1/3)
[  282.390964] wlp3s0: authenticated
[  282.392012] wlp3s0: associate with XX:XX:XX:XX:XX:XX (try 1/3)
[  282.393570] wlp3s0: RX AssocResp from XX:XX:XX:XX:XX:XX (capab=0x111 status=0 aid=13)
[  282.395061] wlp3s0: associated
[  282.428144] wlp3s0: Limiting TX power to 17 dBm as advertised by 78:ba:f9:d8:8a:ae

Last edited by Hikarou (2017-12-11 09:26:31)

shihjay2 · 2017-12-12 19:56:31

@Hikarou, this may be helpful as I think with the updates to NetworkManager to 1.10+, the Intel firmware is no longer is responding the way it used to and I've had to add a configuration file to NetworkManager to disable mac spoofing. See https://bbs.archlinux.org/viewtopic.php … 4#p1656444 for instructions on doing this; this may be why you're able to connect to another network but not another, especially if you already have a previous connection set with your router.

Arch Linux

#1 2017-12-10 14:38:01

Wifi problem since 4.14.x

#2 2017-12-10 16:59:35

Re: Wifi problem since 4.14.x

#3 2017-12-10 19:28:37

Re: Wifi problem since 4.14.x

#4 2017-12-10 23:45:19

Re: Wifi problem since 4.14.x

#5 2017-12-11 09:22:17

Re: Wifi problem since 4.14.x

#6 2017-12-12 19:56:31

Re: Wifi problem since 4.14.x

Board footer