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

Groups > linux.debian.user > #255512 > unrolled thread

Unable to associate to mobile hotspot

Back to article view | Back to linux.debian.user

Contents

  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

#255512 — Unable to associate to mobile hotspot

I'm using Sid/amd64 on my notebook and I have a Android smartphone. My 
notebook has no problems to associate to every WiFI access point I 
tested so far, including mobile phones hotspots, except the hotspot of 
my own smartphone.

On the other hand, another notebook I have (booted with Systemrescuecd) 
has no problems to associate to my smartphone hotspot, and the same is 
true for other notebooks of a few friends I asked to.

I'm using XFCE, though I suspect that doesn't make any difference, 
because Systemrescuecd also uses XFCE.

When I try to associate my notebook to my smartphone hotspot, the 
password dialog simply pops up again, but I'm sure I enter the correct 
password.

I've already tried changing the password, changing the SSID, removing 
the network from NetworkManager and rebooting everything: no dice.

Can you please help me spot the problem?

[toc] | [next] | [standalone]

#255515

On Thu, 2 Mar 2023 18:08:18 +0100
Lucio Crusca <lucio@sulweb.org> wrote:

> Can you please help me spot the problem?

This might give you some ideas. As root, run:

grep -i networkmanager /var/log/syslog

Or run "tail -f /var/log/syslog" and watch it do its thing.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#255516

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

[toc] | [prev] | [next] | [standalone]

#255517

On Thu, 2 Mar 2023 19:37:59 +0100
Lucio Crusca <lucio@sulweb.org> wrote:

> 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>'

Interesting. Looking at a successful login I made this morning, the
next several likes after this one are from the supplicant as it goes
through its gyrations. I would think there would be more lines from the
supplicant.

You might compare this with a successful login elsewhere.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#255521

Il 02/03/23 20:22, Charles Curley ha scritto:
I would think there would be more lines from the
> supplicant.

Yes, there are, but I only posted the logs you asked for (grep -i 
networkmanager). Here is what wpa-supplicat has to say about the problem:

2023-03-02T21:38:57.606785+01:00 t470 wpa_supplicant[679]: wlp4s0: 
Trying to associate with e2:2f:70:ee:a8:a9 (SSID='papospot' freq=5745 MHz)
2023-03-02T21:38:57.607570+01:00 t470 NetworkManager[678]: <info> 
[1677789537.6074] device (wlp4s0): supplicant interface state: 
authenticating -> associating
2023-03-02T21:38:57.607738+01:00 t470 NetworkManager[678]: <info> 
[1677789537.6075] device (p2p-dev-wlp4s0): supplicant management 
interface state: authenticating -> associating
2023-03-02T21:38:57.611072+01:00 t470 kernel: [606294.336798] wlp4s0: 
associate with e2:2f:70:ee:a8:a9 (try 1/3)
2023-03-02T21:38:57.614962+01:00 t470 kernel: [606294.343825] wlp4s0: RX 
AssocResp from e2:2f:70:ee:a8:a9 (capab=0x1131 status=0 aid=1)
2023-03-02T21:38:57.629866+01:00 t470 wpa_supplicant[679]: wlp4s0: 
Associated with e2:2f:70:ee:a8:a9
2023-03-02T21:38:57.630072+01:00 t470 wpa_supplicant[679]: wlp4s0: 
CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
2023-03-02T21:38:57.630987+01:00 t470 kernel: [606294.358880] wlp4s0: 
associated
2023-03-02T21:38:57.635364+01:00 t470 NetworkManager[678]: <info> 
[1677789537.6352] device (wlp4s0): supplicant interface state: 
associating -> associated
2023-03-02T21:38:57.635534+01:00 t470 NetworkManager[678]: <info> 
[1677789537.6353] device (p2p-dev-wlp4s0): supplicant management 
interface state: associating -> associated
2023-03-02T21:38:57.666997+01:00 t470 kernel: [606294.392568] wlp4s0: 
disassociated from e2:2f:70:ee:a8:a9 (Reason: 2=PREV_AUTH_NOT_VALID)
2023-03-02T21:38:57.667599+01:00 t470 NetworkManager[678]: <info> 
[1677789537.6675] device (wlp4s0): supplicant interface state: 
associated -> 4way_handshake
2023-03-02T21:38:57.667775+01:00 t470 NetworkManager[678]: <info> 
[1677789537.6675] device (p2p-dev-wlp4s0): supplicant management 
interface state: associated -> 4way_handshake
2023-03-02T21:38:57.757491+01:00 t470 wpa_supplicant[679]: wlp4s0: 
CTRL-EVENT-DISCONNECTED bssid=e2:2f:70:ee:a8:a9 reason=2
2023-03-02T21:38:57.757650+01:00 t470 wpa_supplicant[679]: wlp4s0: WPA: 
4-Way Handshake failed - pre-shared key may be incorrect
2023-03-02T21:38:57.757747+01:00 t470 wpa_supplicant[679]: wlp4s0: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="papospot" auth_failures=1 
duration=10 reason=WRONG_KEY
2023-03-02T21:38:57.763028+01:00 t470 NetworkManager[678]: <info> 
[1677789537.7629] device (wlp4s0): supplicant interface state: 
4way_handshake -> disconnected
2023-03-02T21:38:57.763223+01:00 t470 NetworkManager[678]: <info> 
[1677789537.7630] device (wlp4s0): Activation: (wifi) disconnected 
during association, asking for new key


I'm no expert, but seems to me it's complaining about wrong credentials. 
However I'm more than sure I'm entering the correct password, I even 
changed it to something dead simple like 12345678.

[toc] | [prev] | [next] | [standalone]

#255525

On Thu, 2 Mar 2023 22:38:36 +0100
Lucio Crusca <lucio@sulweb.org> wrote:

> Yes, there are, but I only posted the logs you asked for (grep -i 
> networkmanager). Here is what wpa-supplicat has to say about the
> problem:

Sorry about that. You are Sid, I'm on Bullseye. Different log file
formats.

I see some lines in there that are suspicious, but I don't know enough
about wpa_supplicant to go further. Anyone else?

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[toc] | [prev] | [next] | [standalone]

#255541

Le 03/03/2023 à 00:53, Charles Curley a écrit :
[...]
> I see some lines in there that are suspicious, but I don't know enough
> about wpa_supplicant to go further. Anyone else?

Hello,

I would look at the WPA type used by the android hotspot: in the past I 
have had problems with pure WPA3 or even hybrid WPA3/WPA2, so I would 
try to configure -at least temporarily- this hotspot in pure WPA2 mode 
to see if the Debian client client can successfully use it...

[toc] | [prev] | [next] | [standalone]

#255543

Il 03/03/23 09:29, didier gaumet ha scritto:
> I would look at the WPA type used by the android hotspot: in the past I 
> have had problems with pure WPA3 or even hybrid WPA3/WPA2, so I would 
> try to configure -at least temporarily- this hotspot in pure WPA2 mode 

Sadly my Redmi Note 8 with MIUI Global 12.5.2 does not offer that kind 
of option in the hotspot configuration. I can only switch between 2.4GHz 
and 5GHz, choose security mode between none and WPA2 Personal, make it 
visible or not and nothing else.

[toc] | [prev] | [next] | [standalone]

#255573

[Multipart message — attachments visible in raw view] — view raw

>
> I'm using Sid/amd64 on my notebook and I have a Android smartphone. My
> notebook has no problems to associate to every WiFI access point I
> tested so far, including mobile phones hotspots, except the hotspot of
> my own smartphone.
>

What is your kernel?
I saw in a forum from Arch that a problem in the kernel is causing this. On
the Debian list, there is a solution. But you would have to update the
default group to intel_iommu=off.
Follow the link.
https://forums.debian.net/viewtopic.php?p=740221

On Thu, Mar 2, 2023 at 2:13 PM Lucio Crusca <lucio@sulweb.org> wrote:

> I'm using Sid/amd64 on my notebook and I have a Android smartphone. My
> notebook has no problems to associate to every WiFI access point I
> tested so far, including mobile phones hotspots, except the hotspot of
> my own smartphone.
>
> On the other hand, another notebook I have (booted with Systemrescuecd)
> has no problems to associate to my smartphone hotspot, and the same is
> true for other notebooks of a few friends I asked to.
>
> I'm using XFCE, though I suspect that doesn't make any difference,
> because Systemrescuecd also uses XFCE.
>
> When I try to associate my notebook to my smartphone hotspot, the
> password dialog simply pops up again, but I'm sure I enter the correct
> password.
>
> I've already tried changing the password, changing the SSID, removing
> the network from NetworkManager and rebooting everything: no dice.
>
> Can you please help me spot the problem?
>
>
>

-- 
Atenciosamente,
Rodrigo da Silva Cunha
São Gonçalo, RJ - Brasil

[toc] | [prev] | [next] | [standalone]

#255672

Il 04/03/23 05:23, Rodrigo Cunha ha scritto:
> What is your kernel?

Linux t470 6.1.0-5-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.12-1 
(2023-02-15) x86_64 GNU/Linux


> I saw in a forum from Arch that a problem in the kernel is causing this. 

I've read through the forum posts you linked, and the ones linked 
therein. I'm afraid it's quite a different problem. My wifi connection 
has no stability issues: it just refuses to associate to this specific 
hotspot, but it works like a charm with others. My logs do not show the 
CTRL-EVENT-BEACON-LOSS message. My network adapter is not Atheros.

At any rate, I've tried adding "intel_iommu=off" to my kernel parameters 
and rebooted, but nothing changed.

[toc] | [prev] | [next] | [standalone]

#255677

On Tue 07 Mar 2023 at 11:56:09 (+0100), Lucio Crusca wrote:
> 
> I've read through the forum posts you linked, and the ones linked
> therein. I'm afraid it's quite a different problem. My wifi connection
> has no stability issues: it just refuses to associate to this specific
> hotspot, but it works like a charm with others. My logs do not show
> the CTRL-EVENT-BEACON-LOSS message. My network adapter is not Atheros.
> 
> At any rate, I've tried adding "intel_iommu=off" to my kernel
> parameters and rebooted, but nothing changed.

In view of:

wlp4s0: disassociated from e2:…:a9 (Reason: 2=PREV_AUTH_NOT_VALID)
wlp4s0: CTRL-EVENT-DISCONNECTED bssid=e2:…:a9 reason=2
wlp4s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlp4s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="papospot" auth_failures=1
        duration=10 reason=WRONG_KEY

have you tried to get more information with this option in
wpa_supplicant:

       -K     Include keys (passwords, etc.) in debug output.

You'd probably need to redact the logs, were you to post them.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#255695

[Multipart message — attachments visible in raw view] — view raw

On Tue, Mar 7, 2023 at 9:44 AM David Wright <deblis@lionunicorn.co.uk>
wrote:

> On Tue 07 Mar 2023 at 11:56:09 (+0100), Lucio Crusca wrote:
> >
> > I've read through the forum posts you linked, and the ones linked
> > therein. I'm afraid it's quite a different problem. My wifi connection
> > has no stability issues: it just refuses to associate to this specific
> > hotspot, but it works like a charm with others. My logs do not show
> > the CTRL-EVENT-BEACON-LOSS message. My network adapter is not Atheros.
> >
> > At any rate, I've tried adding "intel_iommu=off" to my kernel
> > parameters and rebooted, but nothing changed.
>
> In view of:
>
> wlp4s0: disassociated from e2:…:a9 (Reason: 2=PREV_AUTH_NOT_VALID)
> wlp4s0: CTRL-EVENT-DISCONNECTED bssid=e2:…:a9 reason=2
> wlp4s0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
> wlp4s0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="papospot" auth_failures=1
>         duration=10 reason=WRONG_KEY
>

According to these messages your WPA Pre-Shared Key is wrong. You can try
to disable WPA and connect to it as an open network temporarily just to
test the hardware and drivers.



> have you tried to get more information with this option in
> wpa_supplicant:
>
>        -K     Include keys (passwords, etc.) in debug output.
>
> You'd probably need to redact the logs, were you to post them.
>
> Cheers,
> David.
>
>

-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

[toc] | [prev] | [next] | [standalone]

#255703

[Multipart message — attachments visible in raw view] — view raw

>
> At any rate, I've tried adding "intel_iommu=off" to my kernel parameters
> and rebooted, but nothing changed.
>


Steps:
sudo nano /etc/default/grub
Change from this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
To this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_iommu=off"
Update grup:
sudo update-grub
Reinstall system.
shutdown -r now

Then,
*journal -b *and post here.

If skip task update-grub does not work.


On Tue, Mar 7, 2023 at 7:56 AM Lucio Crusca <lucio@sulweb.org> wrote:

> Il 04/03/23 05:23, Rodrigo Cunha ha scritto:
> > What is your kernel?
>
> Linux t470 6.1.0-5-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.12-1
> (2023-02-15) x86_64 GNU/Linux
>
>
> > I saw in a forum from Arch that a problem in the kernel is causing this.
>
> I've read through the forum posts you linked, and the ones linked
> therein. I'm afraid it's quite a different problem. My wifi connection
> has no stability issues: it just refuses to associate to this specific
> hotspot, but it works like a charm with others. My logs do not show the
> CTRL-EVENT-BEACON-LOSS message. My network adapter is not Atheros.
>
> At any rate, I've tried adding "intel_iommu=off" to my kernel parameters
> and rebooted, but nothing changed.
>


-- 
Atenciosamente,
Rodrigo da Silva Cunha
São Gonçalo, RJ - Brasil

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web