Ubuntu

redirect does not work in specific netowk

Asked by Bastian

I have a weird issue:

I can usually access the internet just fine, including public Wifis with captive portals (I just now dialed into one).

However, there is one public Wifi which I am unable to use, because I cannot get to the captive portal.
**I think the reason is, that for some reason Ubuntu will not let me get forwarded in this specific network**
So I can browse 192.168.0.1, getting to the router's maintainance login-page. When entering any other URL, I should actually get forwarded to the captive portal page thus getting forwarded to another URL than the one I had originally requested.

**Here are proposed fixes that do not help**

- https://blog.ham1.co.uk/2016/02/06/cannot-sign-in-using-hotel-wifi-on-linux-ubuntu-mint/
- https://ubuntuforums.org/showthread.php?t=1330428
- https://askubuntu.com/questions/826998/cannot-log-in-to-public-open-wifi-connection?utm_medium=organic&utm_source=google_rich_qa&utm_campaign=google_rich_qa

Question information

Language:
English Edit question
Status:
Open
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#1

Does it affect all browsers?

Revision history for this message
Bastian (baloe) said : 		#2

it affects all browsers, i.e. Firefox, Chromium and Chrome.

Also, I've been using a few public networks this week which all of them had captive login pages to which I was redirected without any issue. What seems to be particular about this one is only its gateway's IP address which I think is equal to the one in my private home network.

Also, I'm on a dual boot machine and Windows 10 has no trouble with this network

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#3

All I can suggest is to report a bug with network-manager

Maybe others can advise

Revision history for this message
Giuseppe (giuseppegalano) said : 		#4

I had the same problem.

* Internet was not working
* Captive Login Page did not show up automatically
* Wifi icon was a question mark ( ? )
* curl -v example.com returned, after some time, "Could not resolve host: example.com".
* I noticed that I was able to ping Google DNS 8.8.8.8

I added 8.8.8.8 to the DNS server list for my WiFi connection, via the following steps:

* Click on the WiFi icon (mine was a question mark, because WiFi was not working)
* Click on the WiFi network name, then Wifi Settings, then the wheel close to my WiFi network, then IPv4 tab
* Wrote 8.8.8.8 in the DNS text box (leave "Automatic DNS" switched on)
* Apply changes
* Restart network manager: sudo service network-manager restart

And it worked for me.

systemd-resolve --status now returns two DNS Servers for the WiFi connection, the first one is the DNS assigned by the network, the second one is 8.8.8.8

Hope this can help.

Revision history for this message
Ryan (ryanclose86) said : 		#5

I am having the same problem with 18.04, except adding 8.8.8.8 to the DNS box did not help. When I type "route" in CLI, I get zero results. I AM able to access the wifi login page on my android phone, and I am able to access regular secured wifi on the Ubuntu machine.

Can you help with this problem?

Provide an answer of your own, or ask Bastian for more information if necessary.

To post a message you must log in.