Just returned to my laptop to find a popup telling me I must log in. Never seen this popup before but clicked on it and the opened a browser window which, after a pause, just had two characters: OK. No further instructions.
This is certainly not OK because all my wifi credentials are correct. Whatever I do I cannot get any access to the internet using wifi any longer.
Fortunately I had a cable to hand so have been able to get here using that but what is going on please.
It seems updates have wiped my wifi login password but even when I restore them in NM I can connect but then cannot access internet. Hope the above means more to you than me!
Now all is good after rebooting and resetting NM network configuration. I unplugged after realizing that I would be pinging using lan connection and here are the results:-
alastair@IBMW530:~> ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 3c:97:0e:bc:f1:50 brd ff:ff:ff:ff:ff:ff
inet 192.168.169.196/25 brd 192.168.169.255 scope global dynamic noprefixroute enp0s25
valid_lft 81484sec preferred_lft 81484sec
inet6 fe80::ac96:ecc1:466e:d584/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 3c:a9:f4:56:ee:8c brd ff:ff:ff:ff:ff:ff
inet 192.168.169.223/25 brd 192.168.169.255 scope global dynamic noprefixroute wlp3s0
valid_lft 67064sec preferred_lft 67064sec
inet6 fe80::24ff:e5ec:c982:6820/64 scope link noprefixroute
valid_lft forever preferred_lft forever
4: wwp0s20u4i6: <BROADCAST,MULTICAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 4e:be:ba:e8:1e:84 brd ff:ff:ff:ff:ff:ff
alastair@IBMW530:~> ping -c3 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=118 time=22.6 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=118 time=21.9 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=118 time=22.7 ms
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 21.936/22.390/22.653/0.322 ms
alastair@IBMW530:~> ^C
alastair@IBMW530:~> ping -c3 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=118 time=25.1 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=118 time=26.4 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=118 time=26.7 ms
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 25.058/26.042/26.655/0.703 ms
alastair@IBMW530:~> ping -c3 google.com
PING google.com (142.250.180.14) 56(84) bytes of data.
64 bytes from lhr25s32-in-f14.1e100.net (142.250.180.14): icmp_seq=1 ttl=118 time=50.4 ms
64 bytes from lhr25s32-in-f14.1e100.net (142.250.180.14): icmp_seq=2 ttl=118 time=32.7 ms
64 bytes from lhr25s32-in-f14.1e100.net (142.250.180.14): icmp_seq=3 ttl=118 time=27.8 ms
--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 27.772/36.971/50.435/9.730 ms
alastair@IBMW530:~> rfkill list all
Absolute path to 'rfkill' is '/usr/sbin/rfkill', so running it may require superuser privileges (eg. root).
alastair@IBMW530:~> sudo rfkill list all
[sudo] password for root:
0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
1: tpacpi_wwan_sw: Wireless WAN
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
alastair@IBMW530:~>
I have no idea why this should happen suddenly and even less understanding of why I should get a browser telling me it was OK when clearly it was not.
I shall blame KDE but if you know what caused this issue I would appreciate your advice.
Many thanks.
Budge.
No as the first command shows but then I pulled the cable but meanwhile I found that the login details had been deleted in NM and re-entered them, hence the commands worked as expected.
I have no idea what had happened as I had been using laptop normally and left it running and when I returned to it to continue working I found I had lost my connection and had this unrecognised popup.
I would like to know why and what prompted these changes so I can remove or edit them. I have a suspicion they are related to changes in the underlaying security sysems; I suspect PolKit. Will have to read up. If you can shine any light please do.
Thanks for coming to my rescue once more.
Regards,
Budge.
Given the usual complete lack of any real facts in your posts it is only possible to guess. It looks like captive portal request which is triggered if NetworkManager connectivity check URL does not return an expected answer (which is empty body in case of default openSUSE checks). This may happen for multiple reasons including temporary glitch of your ISP.
But if you really want an answer then at least show the screenshot of actual dialog and tell what DE you are using. I can again guess that this is KDE based on “OK” you saw …
Hi arvidjaar,
Many thanks for your help once more and I am sorry my panic posting was not too helpful. My reason for not sharing all the important information is that I had returned to the laptop to resume work and then had to quickly try and get my system back up. All the data I might have shown was ephemeral, had been lost and could not be repeated.
I am using KDE desktop on Tumbleweed on the laptop. Captive portal doesn’t mean much to me but I do use NM on the laptop and the NM connectivity check makes sense as does your explanation about the browser although I was blissfully unaware that this was going on in the background.
What is less clear is that the screen was not blank but said OK when clearly it was not OK. This has only happened twice within a period of about 36 hours and I have no idea what prompted the faults in the first place.
Thanks again.
Budge.
Assuming you still have problems to access Google …
Captive portal is used to automatically request authentication before allowing further access. It is web page to which any browser request is redirected until user is authenticated. Network management program may detect it by the “wrong” response to connectivity check. NetworkManager sets connectivity state to PORTAL and that triggers desktop environment into presenting “you need to log in” dialog.
I am using KDE desktop … What is less clear is that the screen was not blank but said OK when clearly it was not OK.
Because any browser request is redirected to captive portal, KDE starts browser with http://networkcheck.kde.org/ URL.
bor@bor-Latitude-E5450:~$ curl http://networkcheck.kde.org/
OK
bor@bor-Latitude-E5450:~$
The fact that you got browser window with this content means Internet connectivity was likely present. This is not the same URL as used by NetworkManager, so it is possible that NetworkManager received some non-empty response e.g. due to temporary problems on SUSE servers resulting in attempt to trigger captive portal by KDE.
Hi Steve,
All beyond me I am afraid. No idea which program is using this captive portal. As for resetting my router this is several devices away through switches and UTM. The problem seems to have gone away for now but I do feel even less in control. Thanks for the info anyhow. Some might sink in!
Regards,
Budge.