Can not connect to hotel WiFi

[Mint_ST]

Hello,

I cannot connect to hotel wifi where after connecting you have to go to hotel login page to enter password and accept terms and conditions.
When I click on the wifi name in network manager, it tries to connect and then it says disconnected...If I go to chrome or firefox I don't get the login page (while network manager is showing trying to connect)

I have Linux Mint 17.3 on Dell XPS 14z laptop with "Intel centrino Advanced-N 6230".

I can connect to any other network that asks for password but cannot connect if login (redirect) page is involved.

Thank you.

[Mint_ST]

Output of mintwifi.py

Note: currently I am connected to my phone's hotspot.

Code: Select all

-------------------------
* I. scanning WIFI PCI devices...
  -- Intel Corporation Centrino Advanced-N 6230 [Rainbow Peak] (rev 34)
      ==> PCI ID = 8086:0091 (rev 34)
-------------------------
* II. querying ndiswrapper...
-------------------------
* III. querying iwconfig...
eth0      no wireless extensions.

wlan0     IEEE 802.11abgn  ESSID:"ST1_HotSpot"  
          Mode:Managed  Frequency:2.437 GHz  Access Point: 50:2E:5C:EC:AF:09   
          Bit Rate=65 Mb/s   Tx-Power=15 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=46/70  Signal level=-64 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:1  Invalid misc:553   Missed beacon:0

lo        no wireless extensions.

-------------------------
* IV. querying ifconfig...
eth0      Link encap:Ethernet  HWaddr d4:be:d9:14:6a:b9  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:11665 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11665 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1398759 (1.3 MB)  TX bytes:1398759 (1.3 MB)

wlan0     Link encap:Ethernet  HWaddr 88:53:2e:93:03:91  
          inet addr:192.168.1.10  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::8a53:2eff:fe93:391/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:29025 errors:0 dropped:0 overruns:0 frame:0
          TX packets:19537 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:22137402 (22.1 MB)  TX bytes:3314099 (3.3 MB)

-------------------------
* V. querying DHCP...
RTNETLINK answers: File exists
-------------------------
* VI. querying nslookup google.com...
Server:		192.168.1.1
Address:	192.168.1.1#53

Non-authoritative answer:
Name:	google.com
Address: 216.58.217.142

[jmg]

A workaround:

Sometimes wifi login pages (at some hotels, etc.) don't work with Linux, but work with mobile phones, etc. Therefore, we can just connect our mobile phone to the wifi using the login page, and then connect this mobile phone to our Linux laptop with a USB cable, and go to something like Settings > USB tethering (in our phone) to enable this.

In this way, our Linux laptop has internet through a wired connection to the mobile phone, which is connected to the wifi.

[m-s-a]

I think this has to do with the "captive portal" mechanism that those access points are using (https://en.wikipedia.org/wiki/Captive_portal).
They use a mechanism that is similar to a DNS hacking attack, which is why linux blocks it.
If you can figure out the IP of that access point (usually the same as the gateway?) , you can try to point your browser to that address directly (e.g. http://192.168.100.1/ if that's the gateway IP in this example). That way, you should be able to get the authentication token and from there on, things should work.

[deleted]

I've found that you have to allow all on FF or Chrome if you have script blockers, popups, and ad blockers enabled.
-H

[hrmcrm]

There is a fix at http://askubuntu.com/a/872155/671313 that worked for me. This is on a dual-boot ThinkPad X201. Windows 10 Firefox redirected to the hotel login page. Mint 18.1 KDE 64-bit Firefox and Konqueror would not go to the login page. The computer connected OK to the hotel wifi, but could not login to access the Internet. Changing resolvconf as described in the referenced post fixed the problem at this one hotel.
Regards,

[Mandywins]

Try icanhazip.com It worked for me!