[NOT SOLVED] wifi portal unreachable DNS PROBE FINISHED NO INTERNET

Yann · 2019-03-30 17:33:15

Hi everyone,
I am on 4.20.13-arch1-1-ARCH with i3 4.16.1-107 WM.
I have been trying for 3 weeks now to connect my system to an open wifi at my university.

Now the situation is that I can connect to the open eduspot wifi network with wpa_supplicant. So I have an IP address from the router but I can not get to the portal router page.
I tested everything on 2 different Dell laptops with the same arch system. Both have the exact same behavior. When I am connected (automatically with wpa), I open my preferred browser (vivaldi 2.3.1440.48-1) and can not get to the portal. I enter the good url request because the browser says to me that it is looking for the router page (a particular login router url). I get the same when I try 1.1.1.1 or http://google.com. With any of these tries it redirects me to the router portal url page but always ends with the DNS_PROBE_FINISHED_NO_INTERNET error.

My DNS are well configured 1.1.1.1 and 8.8.8.8 in resolv.conf. Here too I tried everything, all possible configurations but still DNS_PROBE_FINISHED_NO_INTERNET. I looked at all the vivaldi setups, nothing. I tried with firefox this morning, same error.
At first, I was thinking that the router was blacklisting my first laptop but when having the exact same issue with the second one for the first time I think the problem is somewhere else. Moreover, I tested with my android smartphone android and it directly shows up the portal router popup connection.
It finally seems that it's not:

the browser because tested vivaldi and firefox (last versions on a clean system)
The DNS conf, I tried lots of different ones
The entered url calling the portal seems well
The router because able to connect with my smartphone and windows computers (other students)

I begin to think that the problem is os related, am I missing a kernel module or a special daemon for this kind of connection?

Other useful info, my addresses seems a little strange to me (I am not familiar):

inet  172.24.45.94/21    brd  172.24.47.255

Why are the brd "different" than my IP? 47 instead of 45?
And I am not able to ping the router. I tried:

ping 172.24.45.1
ping 172.24.47.1
ping 192.168.0.1

nothing..

Can someone help me with my situation and direct me toward a solution?

Thanks for your time.

Last edited by Yann (2019-04-18 11:22:46)

ewaller · 2019-03-30 18:51:08

It would seem to me this is a chicken and egg thing. You cannot reach 1.1.1.1 or 8.8.8.8 until the captive portal allows your packets to route to the Internet. Do you know the IP address of the portal? If so, you could use that. Also, it is likely that the DHCP connection provides you with the address of a DNS server that is inside the domain that you can reach; one that will know about the portal address. It sounds like you are overriding that by forcing the use of a DNS server that is outside the domain, and therefore blocked.

Yann · 2019-03-30 19:01:17

Thanks ewaller for your answer. Your explanation makes sens.

No, I don't know the adress of the portal, how can I discover it when connected to the network? (nmap?)
I did not succeed to ping anything. Any idea of IP that will answer?
Also, what is this private IP:

inet  172.24.45.94/21    brd  172.24.47.255

Can you tell me why they are different?

seth · 2019-03-31 08:21:50

Different from what?

What likely is happening is that your browser wants to contact a different domain, eg. for the adblocker or to perform some security checks (I think nanny'd browsing is default for chromium, see "safe browsing" and stuff in chrome://settings/ - it might be disabled in a por… private window/tab), so check this and/or use a dumber browser (eg. netsurf, ideally you can use links/lynx on the console)

Yann · 2019-03-31 09:12:11

seth wrote:

Different from what?

Yann wrote:

Other useful info, my addresses seems a little strange to me (I am not familiar):
inet 172.24.45.94/21 brd 172.24.47.255
Why are the brd "different" than my IP? 47 instead of 45?

ok seth, so you think even for vivaldi or firefox it's likely a security parameter?

An advanced question, is it another way to conturn the portal? A standard protocol/API to directly furnish the username and password to the open wifi router and so performing a direct connection?

Last edited by Yann (2019-03-31 10:43:22)

seth · 2019-03-31 12:47:25

Ah, missed that.
"brd" is the broadcast domain, the subnet mask is 3 bits shorter than "usual" so that should be ok and due to the specific network layout.

Vivaldi *is* chrome (chromium) and I'm pretty sure FF has a nanny feature as well (but idk whether it's active by default)
At the very least you could try to "curl https://www.google.com > wtf.htm" and see whether that gets you the expected portal page.

eduspot unlike eduroam seems to rely on captive portals, you can perhaps script your way in (ie. w/ a simple curl post) but these things are no standardized or even just specified :-(
(Also *every* information I found is in French… seems a local thing?)

Lone_Wolf · 2019-03-31 13:03:11

No, I don't know the adress of the portal, how can I discover it when connected to the network?

You have a url for the portal page, have someone run a ping to that url on a system that has connection.
The output should show the ip-address corresponding to the url.

Yann · 2019-03-31 16:27:29

Thanks seth and Lone_Wolf.
Very good suggestions, I am going to:

get the portal IP through ping
try a simple curl in a terminal
search a little more for the nanny vivaldi setting
if not working try another simple browser
if making progress, I will investigate for an eventual automatic login regarding the router with a script

Doing that ASAP.
Thanks for your time.

Last edited by Yann (2019-03-31 16:31:21)

Yann · 2019-04-01 10:08:10

results this morning:

I installed a x terminal app on my android phone, connect to the eduspot network and ping the portal url (portailwifixxxxx) to get the portal IP: getting 172.24.47.254 --> not sure what to do with that next ...
curl https://www.google.com > wtf.htm --> Could not resolve host: www.google.com
nanny parameters: chrome://settings/ --> I changed most of them, no change
tried netsurf browser, same problem --> could not connect to server or could not resolve host name errors

Then, I booted on a manjaro drive, it connects directly to the portal.. So I guess there is something on manjaro (settings, packages or daemons) that are not on my minimal arch system. I try to keep as minimal as possible, I don't use NetworkManager for example.

Also, it seems that I should set:

phase2="auth=MSCHAPV2"

in my /etc/wpa_supplicant/wpa.conf for this kind of eduspot network.

I am going to check that this afternoon.

Last edited by Yann (2019-04-01 10:34:10)

Lone_Wolf · 2019-04-01 10:30:16

The difference is probably not in packages, but in configuration.

You know the ip address of the portal router now, verify you can ping it from archlinux.

Assuming that works , try

drill google.com @172.24.47.254 # comes with ldns

and post the output.

Yann · 2019-04-01 10:35:15

I did ping it and it answered. Ok, will try:

drill google.com @172.24.47.254 # comes with ldns

Yann · 2019-04-01 14:46:18

$ drill google.com @172.24.47.254 # comes with ldns

[8541:8562:0401/152238.902145:ERROR:connection_factory_impl.cc(411)] Failed to connect to MCS endpoint with error -137

Error: error sending query: Could not send or receive, because of network error

I spent 40 minutes trying different conf in my /etc/wpa_supplicant/wpa.conf file:

# eduspot university
network={
	ssid="eduspot"
        key_mgmt=NONE
	#scan_ssid=1
	#key_mgmt=WPA-EAP
	#phase1="peaplabel=0"
	#eap=TTLS
	#eap=PEAP
	id_str="open_wifi"
	#phase2="auth=MSCHAPV2"
	#phase2="auth=PAP"
}

I noticed that I was not able to connect to the router without:

key_mgmt=NONE

So, I think that it could be a conf problem that the KDE layer solves. Do you have any idea about what I should try now?

Thanks a lot for your time.

seth · 2019-04-01 16:01:45

eduspot is *not* eduroam and everything I found suggests that it does NOT support EAP.

Apparently the drill approach gets you dis-associated from the AP…

I frankly do not understand the "Could not resolve host: www.google.com" .

Try to

nmap 172.24.47.254

Ultimately wireshark the connection attempts.

It might also be beneficial to compare the "ip a", "ip r" and "cat /etc/resolv.conf" outputs among the arch and the manjaro system.

Yann · 2019-04-01 22:23:03

I read more french documentation about the eduspot network.
This network:

doesn't need any WEP key
needs the TCP/IP parameters to be in automatic mode
needs the browser to not block the popups

I am probably wrong, but the error coming from

curl https://www.google.com

with 1.1.1.1 in my resolv.conf seems pretty normal to me. I ask it to access internet to resolv the google.com domain name but the AP has not already registered me.

ASAP I will:

try nmap
compare the /etc/resolv.conf files between the Manjaro one and mine

OMT, Thanks.

Last edited by Yann (2019-04-01 22:25:09)

seth · 2019-04-02 06:22:26

If this is portal based, any attempt to resolve anything should get you the portal - unless there's a dumb useragent filter …
What browser did you use on manjaro?

Yann · 2019-04-02 08:50:28

Ok, I understand. I used firefox (base). It shows directly a popup about authentification when connected to the eduspot open wifi.

So, there is any way to conturn a captive portal? The only way is to identify through the portal?

Yann · 2019-04-02 18:19:38

nmap 172.24.47.254

Starting Nmap 7.70 ( https://nmap.org ) at 2019-04-02 19:37 CEST
[30120:30166:0402/193738.688544:ERROR:connection_factory_impl.cc(411)] Failed to connect to MCS endpoint with error -137
Nmap scan report for 172.24.47.254
Host is up (0.0032s latency).
Not shown: 995 filtered ports
PORT     STATE  SERVICE
22/tcp   closed ssh 
53/tcp   open   domain
80/tcp   closed http
443/tcp  open   https
8000/tcp open   http-alt

Nmap done: 1 IP address (1 host up) scanned in 21.25 seconds

http is closed?!

On the manjaro system, resolv.conf is empty.

I begin to be tired by this problem, I think I am going to let it..

Last edited by Yann (2019-04-02 18:21:27)

seth · 2019-04-02 19:14:15

Manjaro probably operates on systemd-resolved (+ Networkmanager?)
https is open and so is 8080, what happens if you try to open https://172.24.47.254 or http://172.24.47.254:8080 with firefox?

Yann · 2019-04-03 09:07:49

The classes have finished 1 week ago, I will go back there in 2 weeks and try:

https://172.24.47.254
http://172.24.47.254:8080

in firefox.

Indeed, I think Manjaro has a layer that manages that better with something like systemd-resolved (and/or Networkmanager). Will try that.

Thanks seth.

seth · 2019-04-03 11:38:44

This is not about "a layer that manages", but merely that we don't know the DNS config of the manjaro system, because it's not done w/ resolv.conf.
We'd still need that info (along "ip a" and "ip r")

Yann · 2019-04-03 11:49:00

I won't have the opportunity to go over there soon. I am going to let it like this.
OMT, thanks for your time.

Last edited by Yann (2019-04-18 11:23:44)

Arch Linux

#1 2019-03-30 17:33:15

[NOT SOLVED] wifi portal unreachable DNS PROBE FINISHED NO INTERNET

#2 2019-03-30 18:51:08

Re: [NOT SOLVED] wifi portal unreachable DNS PROBE FINISHED NO INTERNET

#3 2019-03-30 19:01:17

Re: [NOT SOLVED] wifi portal unreachable DNS PROBE FINISHED NO INTERNET

#4 2019-03-31 08:21:50

Re: [NOT SOLVED] wifi portal unreachable DNS PROBE FINISHED NO INTERNET

#5 2019-03-31 09:12:11

Re: [NOT SOLVED] wifi portal unreachable DNS PROBE FINISHED NO INTERNET

#6 2019-03-31 12:47:25

Re: [NOT SOLVED] wifi portal unreachable DNS PROBE FINISHED NO INTERNET

#7 2019-03-31 13:03:11

Re: [NOT SOLVED] wifi portal unreachable DNS PROBE FINISHED NO INTERNET

#8 2019-03-31 16:27:29

Re: [NOT SOLVED] wifi portal unreachable DNS PROBE FINISHED NO INTERNET

#9 2019-04-01 10:08:10

Re: [NOT SOLVED] wifi portal unreachable DNS PROBE FINISHED NO INTERNET

#10 2019-04-01 10:30:16

Re: [NOT SOLVED] wifi portal unreachable DNS PROBE FINISHED NO INTERNET

#11 2019-04-01 10:35:15

Re: [NOT SOLVED] wifi portal unreachable DNS PROBE FINISHED NO INTERNET

#12 2019-04-01 14:46:18

Re: [NOT SOLVED] wifi portal unreachable DNS PROBE FINISHED NO INTERNET

#13 2019-04-01 16:01:45

Re: [NOT SOLVED] wifi portal unreachable DNS PROBE FINISHED NO INTERNET

#14 2019-04-01 22:23:03

Re: [NOT SOLVED] wifi portal unreachable DNS PROBE FINISHED NO INTERNET

#15 2019-04-02 06:22:26

Re: [NOT SOLVED] wifi portal unreachable DNS PROBE FINISHED NO INTERNET

#16 2019-04-02 08:50:28

Re: [NOT SOLVED] wifi portal unreachable DNS PROBE FINISHED NO INTERNET

#17 2019-04-02 18:19:38

Re: [NOT SOLVED] wifi portal unreachable DNS PROBE FINISHED NO INTERNET

#18 2019-04-02 19:14:15

Re: [NOT SOLVED] wifi portal unreachable DNS PROBE FINISHED NO INTERNET

#19 2019-04-03 09:07:49

Re: [NOT SOLVED] wifi portal unreachable DNS PROBE FINISHED NO INTERNET

#20 2019-04-03 11:38:44

Re: [NOT SOLVED] wifi portal unreachable DNS PROBE FINISHED NO INTERNET

#21 2019-04-03 11:49:00

Re: [NOT SOLVED] wifi portal unreachable DNS PROBE FINISHED NO INTERNET

Board footer