Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #255516

Re: Unable to associate to mobile hotspot

From Lucio Crusca <lucio@sulweb.org>
Newsgroups linux.debian.user
Subject Re: Unable to associate to mobile hotspot
Date 2023-03-02 19:40 +0100
Message-ID <G4W0q-9BNa-11@gated-at.bofh.it> (permalink)
References <G4UKZ-9B6S-1@gated-at.bofh.it> <G4VQJ-9BJH-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw



Il 02/03/23 18:55, Charles Curley ha scritto:
> grep -i networkmanager /var/log/syslog

Thanks, I looked at the logs, but I couldn't find the problem. The SSID 
is "papospot". Here are the relevant log entries:


2023-03-02T18:07:18.857868+01:00 t470 NetworkManager[678]: <info> 
[1677776838.8553] device (wlp4s0): disconnecting for new activation request.
2023-03-02T18:07:18.858078+01:00 t470 NetworkManager[678]: <info> 
[1677776838.8553] device (wlp4s0): state change: activated -> 
deactivating (reason 'new-activation', sys-iface-state: 'managed')
2023-03-02T18:07:18.858172+01:00 t470 NetworkManager[678]: <info> 
[1677776838.8562] manager: NetworkManager state is now CONNECTED_LOCAL
2023-03-02T18:07:18.858274+01:00 t470 NetworkManager[678]: <info> 
[1677776838.8565] audit: op="connection-add-activate" 
uuid="0df150fb-e0b6-4227-bf49-a261db8257df" name="papospot" pid=2676 
uid=1000 result=
"success"
2023-03-02T18:07:18.860097+01:00 t470 dbus-daemon[622]: [system] 
Activating via systemd: service name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.13' 
(uid=0 pid=678 comm="/usr/sbin/NetworkManager --no-daemon")
2023-03-02T18:07:18.912369+01:00 t470 systemd[1]: Starting 
NetworkManager-dispatcher.service - Network Manager Script Dispatcher 
Service...
2023-03-02T18:07:18.923258+01:00 t470 systemd[1]: Started 
NetworkManager-dispatcher.service - Network Manager Script Dispatcher 
Service.
2023-03-02T18:07:19.045740+01:00 t470 NetworkManager[678]: <info> 
[1677776839.0455] device (wlp4s0): state change: deactivating -> 
disconnected (reason 'new-activation', sys-iface-state: 'managed')
2023-03-02T18:07:19.051519+01:00 t470 NetworkManager[678]: <info> 
[1677776839.0488] dhcp6 (wlp4s0): canceled DHCP transaction
2023-03-02T18:07:19.051953+01:00 t470 NetworkManager[678]: <info> 
[1677776839.0488] dhcp6 (wlp4s0): activation: beginning transaction 
(timeout in 45 seconds)
2023-03-02T18:07:19.052922+01:00 t470 NetworkManager[678]: <info> 
[1677776839.0489] dhcp6 (wlp4s0): state changed no lease
2023-03-02T18:07:19.090338+01:00 t470 NetworkManager[678]: <info> 
[1677776839.0901] device (wlp4s0): set-hw-addr: set MAC address to 
2E:D1:85:CF:A6:77 (scanning)
2023-03-02T18:07:19.146216+01:00 t470 NetworkManager[678]: <info> 
[1677776839.1440] device (wlp4s0): Activation: starting connection 
'papospot' (0df150fb-e0b6-4227-bf49-a261db8257df)
2023-03-02T18:07:19.146484+01:00 t470 NetworkManager[678]: <info> 
[1677776839.1445] device (wlp4s0): supplicant interface state: completed 
-> disconnected
2023-03-02T18:07:19.146680+01:00 t470 NetworkManager[678]: <info> 
[1677776839.1446] device (p2p-dev-wlp4s0): supplicant management 
interface state: completed -> disconnected
2023-03-02T18:07:19.146846+01:00 t470 NetworkManager[678]: <info> 
[1677776839.1452] device (wlp4s0): state change: disconnected -> prepare 
(reason 'none', sys-iface-state: 'managed')
2023-03-02T18:07:19.147050+01:00 t470 NetworkManager[678]: <info> 
[1677776839.1456] manager: NetworkManager state is now CONNECTING
2023-03-02T18:07:19.178500+01:00 t470 NetworkManager[678]: <info> 
[1677776839.1782] device (wlp4s0): set-hw-addr: reset MAC address to 
9C:FC:E8:B6:64:0D (preserve)
2023-03-02T18:07:19.183295+01:00 t470 NetworkManager[678]: <info> 
[1677776839.1827] device (wlp4s0): state change: prepare -> config 
(reason 'none', sys-iface-state: 'managed')
2023-03-02T18:07:19.183568+01:00 t470 NetworkManager[678]: <info> 
[1677776839.1831] device (wlp4s0): Activation: (wifi) access point 
'papospot' has security, but secrets are required.
2023-03-02T18:07:19.183740+01:00 t470 NetworkManager[678]: <info> 
[1677776839.1831] device (wlp4s0): state change: config -> need-auth 
(reason 'none', sys-iface-state: 'managed')
2023-03-02T18:07:29.203802+01:00 t470 systemd[1]: 
NetworkManager-dispatcher.service: Deactivated successfully.
2023-03-02T18:07:29.905561+01:00 t470 NetworkManager[678]: <info> 
[1677776849.9042] device (wlp4s0): state change: need-auth -> prepare 
(reason 'none', sys-iface-state: 'managed')
2023-03-02T18:07:29.906353+01:00 t470 NetworkManager[678]: <info> 
[1677776849.9059] device (wlp4s0): state change: prepare -> config 
(reason 'none', sys-iface-state: 'managed')
2023-03-02T18:07:29.907611+01:00 t470 NetworkManager[678]: <info> 
[1677776849.9067] device (wlp4s0): Activation: (wifi) connection 
'papospot' has security, and secrets exist.  No new secrets needed.
2023-03-02T18:07:29.907846+01:00 t470 NetworkManager[678]: <info> 
[1677776849.9067] Config: added 'ssid' value 'papospot'
2023-03-02T18:07:29.908013+01:00 t470 NetworkManager[678]: <info> 
[1677776849.9067] Config: added 'scan_ssid' value '1'
2023-03-02T18:07:29.908152+01:00 t470 NetworkManager[678]: <info> 
[1677776849.9068] Config: added 'bgscan' value 'simple:30:-70:86400'
2023-03-02T18:07:29.908259+01:00 t470 NetworkManager[678]: <info> 
[1677776849.9068] Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 
FT-PSK SAE FT-SAE'
2023-03-02T18:07:29.908378+01:00 t470 NetworkManager[678]: <info> 
[1677776849.9068] Config: added 'auth_alg' value 'OPEN'
2023-03-02T18:07:29.908499+01:00 t470 NetworkManager[678]: <info> 
[1677776849.9068] Config: added 'psk' value '<hidden>'
2023-03-02T18:07:29.936821+01:00 t470 NetworkManager[678]: <info> 
[1677776849.9366] device (wlp4s0): supplicant interface state: 
disconnected -> scanning

Back to linux.debian.user | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Unable to associate to mobile hotspot Lucio Crusca <lucio@sulweb.org> - 2023-03-02 18:20 +0100
  Re: Unable to associate to mobile hotspot Charles Curley <charlescurley@charlescurley.com> - 2023-03-02 19:30 +0100
    Re: Unable to associate to mobile hotspot Lucio Crusca <lucio@sulweb.org> - 2023-03-02 19:40 +0100
      Re: Unable to associate to mobile hotspot Charles Curley <charlescurley@charlescurley.com> - 2023-03-02 20:30 +0100
        Re: Unable to associate to mobile hotspot Lucio Crusca <lucio@sulweb.org> - 2023-03-02 22:40 +0100
          Re: Unable to associate to mobile hotspot Charles Curley <charlescurley@charlescurley.com> - 2023-03-03 01:00 +0100
            Re: Unable to associate to mobile hotspot didier gaumet <didier.gaumet@gmail.com> - 2023-03-03 09:30 +0100
              Re: Unable to associate to mobile hotspot Lucio Crusca <lucio@sulweb.org> - 2023-03-03 12:20 +0100
  Re: Unable to associate to mobile hotspot Rodrigo Cunha <rodrigo.root.rj@gmail.com> - 2023-03-04 05:30 +0100
    Re: Unable to associate to mobile hotspot Lucio Crusca <lucio@sulweb.org> - 2023-03-07 12:00 +0100
      Re: Unable to associate to mobile hotspot David Wright <deblis@lionunicorn.co.uk> - 2023-03-07 15:50 +0100
        Re: Unable to associate to mobile hotspot Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2023-03-07 22:40 +0100
      Re: Unable to associate to mobile hotspot Rodrigo Cunha <rodrigo.root.rj@gmail.com> - 2023-03-08 06:50 +0100

csiph-web