Extreme Networks

fabianct · ‎08-31-2018

Users who use Chrome as a browser, have been presenting problems in deploying the captive portal, looking in the Google forums they say that those captive portals that point to the IP 1.1.1.1 that to date it is a new DNS go to have problems and it is suggested that the manufacturers of these solutions use another address.

Therefore, what is AeroHive's way of modifying that the captive portal points to IP 1.1.1.1 without affecting its current functioning. Why in the AP230 equipment does the portal quickly unfold and in the AP250 there is a problem to appreciate it?

fabianct · ‎09-05-2018

Hello everyone, finally the stabilization with the captive portal was given in the following way:

1. When the option "Use default network setting" is unchecked, the values that you must place there as suggested by AeroHive is to use 4 ranges of private networks that are not routed or are being used or in your local LAN and that are not routed networks in Internet, therefore in our case we used the networks that are specified in the graph

2. In the field "Web Server Domain Name" is an FQDN server name, for example if your domain is called xyz.com.co the name for example that would go there is webserver.xyz.com.co

3. In your local DNS it is suggested to create 2 type registers in the Forward zone corresponding to xyz.com.co with the first IP in the radius of 802.11a and radius 802.11b / g as the IP address, and both type A registers point to webserver.xyz.com.co

Temporarily depending on the technology of the wireless network card that the user has if it is 802.11n, it will receive a temporary IP 192.168.9.x and if it is 802.11ac it will receive an ip 192.168.8.x. Once you have authenticated in the captive portal, you will be assigned the IP with which you will be able to navigate or access the services of the network.

You can use any private ip range suggest for the follow RFC:

http://www.ietf.org/rfc/rfc1918.txt

http://tools.ietf.org/html/rfc3330

I hope this post helps everyone solve a problem

View solution in original post

fabianct · ‎08-31-2018

Thanks for your help, I have these questions:

a user who is finally connected through the captive portal is given an IP of the network 192.168.250.x / 24, however with the example of IP addresses that you gave me users initially receive an ip 10.10.4.x / 24 is normal ?, this is how it should work?

We also replace in the internal and external DNS the portal xyz.com.co that before pointed to 1.1.1.1 we put it to point to 1.2.1.1, this is fine?

fabianct · ‎08-31-2018

let us do some tests and we write to you how it went

samantha_lynn · ‎08-31-2018

In those boxes you need to fill in an IP scope that is not in use on your backend network. Any private scope will do. For example, 10.10.1.1/255.255.255.0, 10.10.2.1/255.255.255.0, 10.10.3.1/255.255.255.0, and 10.10.4.1/255.255.255.0. You'll have to fill in each box before you can save

fabianct · ‎08-31-2018

it is not possible to save the changes after "use default network settings" is unchecked, because it forces the information to be filled in order to save.

fabianct · ‎08-31-2018

Uncheck use default network settings force us to fill this data to can continue save de change, what can i do?...

Extreme Networks

How to resolve the problem with captive portal seek 1.1.1.1 for Chrome Users

How to resolve the problem with captive portal seek 1.1.1.1 for Chrome Users