Can't connect to public wifi network [CLOSED]

art · 2019-09-04 11:02:17

Masters of Arch! How to connect to public network? I do that easily if I just booted the system. But if after the sleeping (laptop) it won't connect to the previous or even new network. Now there should be captive screen but no http request are made. Please see the below. The system was updated on 2 Sep (pacman -Syu). It is KDE Plasma.

Here is an example. The same situation with every public network.

art@arch-pc ~]$ nmcli d wifi list -rescan yes
IN-USE  SSID                         MODE   CHAN  RATE        SIGNAL  BARS  SECURIT>
        Beeline_WiFi_FREE            Infra  36    270 Mbit/s  59      ▂▄▆_  --     >
*       Beeline_WiFi_Starbucks_FREE  Infra  36    270 Mbit/s  38      ▂▄__  --     >
        TP-LINK_1DFE                 Infra  2     270 Mbit/s  25      ▂___  WPA2   >
        AlShaya-WiFi                 Infra  8     130 Mbit/s  20      ▂___  WPA2 80>
        Hongkong                     Infra  36    54 Mbit/s   20      ▂___  --     >

[art@arch-pc ~]$ nmcli d wifi connect 'Beeline_WiFi_Starbucks_FREE'
Device 'wlp3s0' successfully activated with '87f466d5-11b7-49bd-a373-33b6b5675aa5'.

[art@arch-pc ~]$ curl http://ya.ru -v 
* Could not resolve host: ya.ru
curl: (6) Could not resolve host: ya.ru

[art@arch-pc ~]$ ip a
# .. (other interfaces removed)
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether [MYMAC HERE] brd ff:ff:ff:ff:ff:ff
    inet 172.17.180.61/16 brd 172.17.255.255 scope global dynamic noprefixroute wlp3s0
       valid_lft 1785sec preferred_lft 1785sec
       
[art@arch-pc ~]$ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
^C
--- 1.1.1.1 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 24ms


[art@arch-pc ~]$ sudo dhcpcd 
[sudo] password for art: 
dev: loaded udev
DUID  [some id here]
wlp3s0: IAID [some id here]
wlp3s0: adding address [some address here]
ipv6_addaddr1: Permission denied
enp0s25: waiting for carrier
wlp3s0: soliciting an IPv6 router
wlp3s0: soliciting a DHCP lease
wlp3s0: offered 172.17.10.69 from 172.17.0.1
wlp3s0: ignoring offer of 172.17.10.69 from 172.17.0.1
wlp3s0: ignoring offer of 172.17.10.69 from 172.17.0.1
wlp3s0: probing address 172.17.10.69/16
wlp3s0: leased 172.17.10.69 for 1800 seconds
wlp3s0: adding route to 172.17.0.0/16
wlp3s0: adding default route via 172.17.0.1
forked to background, child pid 6277

[art@arch-pc ~]$ ip a
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether [my id here] brd ff:ff:ff:ff:ff:ff
    inet 172.17.180.61/16 brd 172.17.255.255 scope global dynamic noprefixroute wlp3s0
       valid_lft 1678sec preferred_lft 1678sec
    inet 172.17.10.69/16 brd 172.17.255.255 scope global secondary noprefixroute wlp3s0
       valid_lft forever preferred_lft forever
       
[art@arch-pc ~]$ ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
ping: sendmsg: Operation not permitted
^C
--- 1.1.1.1 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

[art@arch-pc ~]$ curl http://ya.ru -v
* Could not resolve host: ya.ru
curl: (6) Could not resolve host: ya.ru



AFTER RESTARTING THE SYSTEM. KDE Plasma connector connects and displays that I should "Log in" (captive screen).

[art@arch-pc ~]$ curl http://ya.ru -v
*   Trying 87.250.250.242:80...
* TCP_NODELAY set
* Connected to ya.ru (87.250.250.242) port 80 (#0)
> GET / HTTP/1.1
> Host: ya.ru
> User-Agent: curl/7.65.3
> Accept: */*
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< ...  [here goes the captive screen]

Last edited by art (2019-10-25 14:28:29)

seth · 2019-09-04 14:04:18

I do that easily if I just booted the system. But if after the sleeping (laptop) it won't connect to the previous or even new network.

This is not at all reflected by the subject of the thread so please edit your post and choose a better subject.
Also post the output of "sudo journalctl -b" after this happened, you can use https://wiki.archlinux.org/index.php/Pastebin to feed the journal directly into a pastebin service.

art · 2019-10-25 14:28:18

Not actual. This can be closed.

seth · 2019-10-25 14:38:38

Please don't mark your thread as "closed" since that indicates a mod has locked it.
You can report it for deletion instead if you wish to abandon it (and since it has at this point no meaningful content)

Arch Linux

#1 2019-09-04 11:02:17

Can't connect to public wifi network [CLOSED]

#2 2019-09-04 14:04:18

Re: Can't connect to public wifi network [CLOSED]

#3 2019-10-25 14:28:18

Re: Can't connect to public wifi network [CLOSED]

#4 2019-10-25 14:38:38

Re: Can't connect to public wifi network [CLOSED]

Board footer