View previous topic :: View next topic |
Author |
Message |
creiss Tux's lil' helper
Joined: 21 Sep 2006 Posts: 102 Location: Dortmund
|
Posted: Wed Oct 05, 2022 8:14 am Post subject: Wlan / Roaming issue |
|
|
Hey all,
I am having -for some time now- a wireless lan issue. Every once in a rather frequent time my connection drops. I have to disable wlan and re-enable it to be able to get online again.
It took me a while to figure out whats causing it:
It happens when I am connected to a wlan that has roaming/ multiple APs. And I am roaming around from one AP to another. The this happens:
Code: | Oct 4 21:58:42 dalaeul kernel: wlp1s0: disconnect from AP 74:ac:b9:cb:d3:e2 for new auth to 74:ac:b9:ca:d3:e2
Oct 4 21:58:42 dalaeul kernel: wlp1s0: authenticate with 74:ac:b9:ca:d3:e2
Oct 4 21:58:42 dalaeul kernel: wlp1s0: send auth to 74:ac:b9:ca:d3:e2 (try 1/3)
Oct 4 21:58:42 dalaeul NetworkManager[4408]: <info> [1664913522.8214] device (wlp1s0): supplicant interface state: completed -> authenticating
Oct 4 21:58:42 dalaeul kernel: wlp1s0: authenticated
Oct 4 21:58:42 dalaeul kernel: wlp1s0: associate with 74:ac:b9:ca:d3:e2 (try 1/3)
Oct 4 21:58:42 dalaeul kernel: wlp1s0: RX ReassocResp from 74:ac:b9:ca:d3:e2 (capab=0x1431 status=0 aid=1)
Oct 4 21:58:42 dalaeul NetworkManager[4408]: <info> [1664913522.8429] device (wlp1s0): supplicant interface state: authenticating -> associating
Oct 4 21:58:42 dalaeul kernel: wlp1s0: associated
Oct 4 21:58:42 dalaeul kernel: wlp1s0: Limiting TX power to 20 (20 - 0) dBm as advertised by 74:ac:b9:ca:d3:e2
Oct 4 21:58:42 dalaeul NetworkManager[4408]: <info> [1664913522.8764] device (wlp1s0): supplicant interface state: associating -> completed
Oct 4 21:58:42 dalaeul NetworkManager[4408]: <info> [1664913522.8771] device (wlp1s0): ip:dhcp4: restarting
Oct 4 21:58:42 dalaeul NetworkManager[4408]: <info> [1664913522.8772] dhcp4 (wlp1s0): canceled DHCP transaction, DHCP client pid 14764
Oct 4 21:58:42 dalaeul NetworkManager[4408]: <info> [1664913522.8772] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Oct 4 21:58:42 dalaeul NetworkManager[4408]: <info> [1664913522.8772] dhcp4 (wlp1s0): state changed no lease
Oct 4 21:58:42 dalaeul dhcpcd[14764]: received SIGTERM, stopping
Oct 4 21:58:42 dalaeul dhcpcd[14764]: wlp1s0: removing interface
Oct 4 21:58:42 dalaeul NetworkManager[4408]: <info> [1664913522.8772] dhcp4 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Oct 4 21:58:42 dalaeul NetworkManager[4408]: <info> [1664913522.8797] dhcp4 (wlp1s0): dhcpcd started with pid 15954
Oct 4 21:58:42 dalaeul NetworkManager[4408]: <info> [1664913522.8799] device (wlp1s0): ip:dhcp6: restarting
Oct 4 21:58:42 dalaeul NetworkManager[4408]: <info> [1664913522.8800] dhcp6 (wlp1s0): canceled DHCP transaction
Oct 4 21:58:42 dalaeul NetworkManager[4408]: <info> [1664913522.8801] dhcp6 (wlp1s0): activation: beginning transaction (timeout in 45 seconds)
Oct 4 21:58:42 dalaeul dhcpcd[15954]: sending commands to dhcpcd process
Oct 4 21:58:42 dalaeul NetworkManager[4408]: <info> [1664913522.8832] dhcp4 (wlp1s0): client pid 15954 exited with status 0
Oct 4 21:58:42 dalaeul NetworkManager[4408]: <warn> [1664913522.8916] dhcp-listener: dhcp-event: (pid 14764) unhandled DHCP event for interface wlp1s0
Oct 4 21:58:42 dalaeul NetworkManager[4408]: <warn> [1664913522.9058] dhcp-listener: dhcp-event: (pid 14764) unhandled DHCP event for interface wlp1s0
Oct 4 21:58:42 dalaeul dhcpcd[14764]: dhcpcd exited
|
I enabled CONFIG_CFG80211_WEXT in kernel but that did no change anything.
I am sure this is fixable, but I am not quite sure how.
Any help is appreciated!
-Chris. _________________ Registered Linux User #38359 (http://counter.li.org) |
|
Back to top |
|
|
szatox Advocate
Joined: 27 Aug 2013 Posts: 3104
|
Posted: Wed Oct 05, 2022 12:09 pm Post subject: |
|
|
And what do you actually want to do?
Are those multiple APs actually the same network? You can try locking your client to a particular BSSID. Not sure if it helps, but it could provide some additional information. Like, is one of those AP's broken and you only hit it after your nearest AP goes down? |
|
Back to top |
|
|
creiss Tux's lil' helper
Joined: 21 Sep 2006 Posts: 102 Location: Dortmund
|
Posted: Wed Oct 05, 2022 12:50 pm Post subject: |
|
|
No,
its a multi-ap setup, from Unifi. Roaming is meant to happen. _________________ Registered Linux User #38359 (http://counter.li.org) |
|
Back to top |
|
|
|