View previous topic :: View next topic |
Author |
Message |
binro l33t
Joined: 06 May 2005 Posts: 738 Location: Bangkok, Thailand
|
Posted: Fri Nov 29, 2024 4:00 pm Post subject: New install - WiFi connection keeps on restarting |
|
|
I recently installed a system backed up from my desktop onto a laptop. The only significant difference is that the desktop was wired to the router and the laptop is using WiFi. I use NetworkManager and everything starts up as normal, it seems as soon as I do something like ssh to another system, the connection restarts:
Code: |
Nov 29 22:20:29 localhost kernel wlan0: Connection to AP 58:d5:6e:ca:62:ad lost
Nov 29 22:20:31 localhost ntpd[4709] Deleting interface #2 wlan0, 192.168.100.36#123, interface stats:
received=21, sent=21, dropped=0, active_time=314 secs
Nov 29 22:20:31 localhost ntpd[4709] 147.50.17.138 local addr 192.168.100.36 -> <null>
Nov 29 22:20:31 localhost ntpd[4709] 203.159.70.33 local addr 192.168.100.36 -> <null>
Nov 29 22:20:31 localhost ntpd[4709] 202.28.116.236 local addr 192.168.100.36 -> <null>
Nov 29 22:20:31 localhost ntpd[4709] 202.80.227.130 local addr 192.168.100.36 -> <null>
Nov 29 22:20:31 localhost kernel wlan0: authenticate with 58:d5:6e:ca:62:ad
Nov 29 22:20:31 localhost kernel wlan0: 80 MHz not supported, disabling VHT
Nov 29 22:20:31 localhost kernel wlan0: send auth to 58:d5:6e:ca:62:ad (try 1/3)
Nov 29 22:20:31 localhost kernel wlan0: authenticated
Nov 29 22:20:31 localhost kernel wlan0: associate with 58:d5:6e:ca:62:ad (try 1/3)
Nov 29 22:20:31 localhost kernel wlan0: RX AssocResp from 58:d5:6e:ca:62:ad (capab=0x431 status=0
aid=6)
Nov 29 22:20:31 localhost kernel wlan0: associated
Nov 29 22:20:32 localhost dhcpcd[4596] received SIGTERM, stopping
Nov 29 22:20:32 localhost dhcpcd[4596] wlan0: removing interface
Nov 29 22:20:32 localhost dhcpcd[6729] sending commands to dhcpcd process
Nov 29 22:20:32 localhost NetworkManager[4236] <warn> [1732893632.3432] dhcp-listener: dhcp-event:
(pid 4596) unhandled DHCP event for interface wlan0
Nov 29 22:20:32 localhost NetworkManager[4236] <warn> [1732893632.3576] dhcp-listener: dhcp-event:
(pid 4596) unhandled DHCP event for interface wlan0
Nov 29 22:20:32 localhost dhcpcd[4596] dhcpcd exited
Nov 29 22:21:17 localhost kernel wlan0: deauthenticating from 58:d5:6e:ca:62:ad by local choice (Reason:
3=DEAUTH_LEAVING)
Nov 29 22:21:17 localhost NetworkManager[4236] <warn> [1732893677.7951] device (wlan0): Activation:
failed for connection 'Binro.Org'
Nov 29 22:21:17 localhost dbus-daemon[4173] [system] Activating service name='org.freedesktop.nm_dispatcher'
requested by ':1.0' (uid=0 pid=4236 comm="/usr/sbin/NetworkManager --pid-file
/run/NetworkMa") (using servicehelper)
Nov 29 22:21:17 localhost dbus-daemon[4173] [system] Successfully activated service 'org.freedes
ktop.nm_dispatcher'
Nov 29 22:21:18 localhost /etc/init.d/NetworkManager[6956] status: inactive
Nov 29 22:21:18 localhost /etc/init.d/NetworkManager[6971] status: inactive
Nov 29 22:21:21 localhost kernel wlan0: authenticate with 58:d5:6e:ca:62:ad
Nov 29 22:21:21 localhost kernel wlan0: 80 MHz not supported, disabling VHT
Nov 29 22:21:21 localhost kernel wlan0: send auth to 58:d5:6e:ca:62:ad (try 1/3)
Nov 29 22:21:21 localhost kernel wlan0: authenticated
Nov 29 22:21:21 localhost kernel wlan0: associate with 58:d5:6e:ca:62:ad (try 1/3)
Nov 29 22:21:21 localhost kernel wlan0: RX AssocResp from 58:d5:6e:ca:62:ad (capab=0x431 status=0
aid=6)
Nov 29 22:21:21 localhost kernel wlan0: associated
Nov 29 22:21:22 localhost dhcpcd[6973] dhcpcd-10.1.0 starting
Nov 29 22:21:22 localhost dhcpcd[6973] DUID 00:01:00:01:1a:7a:7e:27:00:24:d7:ae:d7:08
Nov 29 22:21:22 localhost dhcpcd[6973] wlan0: connected to Access Point: Binro.Org
Nov 29 22:21:22 localhost dhcpcd[6973] wlan0: IAID e8:79:51:03
Nov 29 22:21:22 localhost dhcpcd[6973] wlan0: rebinding lease of 192.168.100.36
Nov 29 22:21:22 localhost dhcpcd[6973] wlan0: leased 192.168.100.36 for 43200 seconds
Nov 29 22:21:24 localhost /etc/init.d/NetworkManager[7003] status: inactive
Nov 29 22:21:24 localhost /etc/init.d/NetworkManager[7021] status: inactive
Nov 29 22:21:24 localhost /etc/init.d/NetworkManager[7041] status: inactive
Nov 29 22:21:26 localhost ntpd[4709] Listen normally on 3 wlan0 192.168.100.36:123
Nov 29 22:22:19 localhost kernel wlan0: Connection to AP 58:d5:6e:ca:62:ad lost
|
I use dnsmasq on the LAN server for DHCP and DNS but the only thing I can see there is the session reconnecting (which I suppose is to be expected). I have removed all the definitions from /etc/conf.d/net and deleted the symlinks from /etc/init.d/net.l; what else have I forgotten?
TIA
Robin _________________ "Ship me somewheres east of Suez, where the best is like the worst,
Where there ain't no Ten Commandments an' a man can raise a thirst"
from "Mandalay" by Rudyard Kipling |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54609 Location: 56N 3W
|
Posted: Fri Nov 29, 2024 4:22 pm Post subject: |
|
|
binro,
reason=3 means that the WiFi was told to disconnect.
The usual cause is that several things are trying to control it.
You may have at most, one, or they fight but none can win.
The usual approach is to disable all candidates that can start WiFi and prove it by rebooting.
Notice that WiFi does not start. That's a good sign.
Now add back exactly one service and reboot.
You should be good. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
binro l33t
Joined: 06 May 2005 Posts: 738 Location: Bangkok, Thailand
|
Posted: Fri Nov 29, 2024 5:18 pm Post subject: |
|
|
Neddy, thanks for the suggestion but AFAICT, there is only NM trying to start the connection. Looking at the KDE Settings network tab, apart from the active WiFi there are only connections active some weeks ago. \Were do I look for "candidates"? _________________ "Ship me somewheres east of Suez, where the best is like the worst,
Where there ain't no Ten Commandments an' a man can raise a thirst"
from "Mandalay" by Rudyard Kipling |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54609 Location: 56N 3W
|
Posted: Fri Nov 29, 2024 5:34 pm Post subject: |
|
|
Disable NetworkManager and reboot.
If WiFi works now, it's NetworkManager and something else fighting.
If it keeps cycling with reason=3, youhave several sometings still.
Both dhcpcd and wpa-supplicant can start WiFi too.
To use NetworkManager, neither must be started as a service. NetworkManager will take care of it.
The first step is to make WiFi not start at all. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
binro l33t
Joined: 06 May 2005 Posts: 738 Location: Bangkok, Thailand
|
Posted: Sat Nov 30, 2024 9:43 pm Post subject: |
|
|
I removed NM from the service start lists and rapidly discovered you must remove dependent services (netmount, sendmail, etc...), After rebooting there was no network connection. I started NM and the WiFi connected, so I left it for a long time and nothing bad happened. I then ssh'ed into another system and immediately the connection restarted. I had copied ~/.ssh from the desktop system and the public keys had the old host name after the Base64 key text, but that is just for humans, isn't it? Anyway the laptop is for the g/f and she won't be doing any shelling about, so I guess I can live with the weirdness!
Thanks anyway. _________________ "Ship me somewheres east of Suez, where the best is like the worst,
Where there ain't no Ten Commandments an' a man can raise a thirst"
from "Mandalay" by Rudyard Kipling |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54609 Location: 56N 3W
|
Posted: Sun Dec 01, 2024 1:02 pm Post subject: |
|
|
binro,
I't a very bad thing to copy the host keys from one system to another.
As you say, the plaintext is just for humans. The key is for ssh to identify the host its connecting to.r _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|