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

samantha_lynn · ‎08-31-2018

Once you uncheck the "use default network settings" option, you can fill in any internal IP address that is not currently in use on your network, other than the 1.1.x.x scope. This scope will be given to clients only while they authenticate, once they are fully authenticated they will get an IP address from the DHCP server on your client VLAN.

fabianct · ‎08-31-2018

OK thanks, now in the option Web Server Domain Name we have xyz.com.co this FQDN in our internal and external DNS point to 1.1.1.1, then the question is:

uncheck Use default network settings, we can change the IP that aerohive suggest (Which?) in our internal DNS?

samantha_lynn · ‎08-31-2018

If you can send me a screen shot of your About HiveManager page, I can confirm the steps you need to follow. If you'd rather share this with me directly, you can email me at communityhelp@aerohive.com.

samantha_lynn · ‎08-31-2018

You would want to use the instructions for HiveManager Classic.

You'll want to go to Configuration> Open the Network Policy> Open the CWP object and Edit it> Expand "Optional Advanced Configuration" and uncheck the box next to "Use default network settings", which should show you four IP address and netmask fields you can fill in to use a network scope other than the 1.1.1.1 addresses.

fabianct · ‎08-31-2018

The steps you propose do not match the version of HiveManager that we have

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