This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

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

Go to solution
fabianct
New Contributor III

‎08-31-2018 08:13 PM

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?

 

0 Kudos
1 ACCEPTED SOLUTION

Go to solution
fabianct
New Contributor III

‎09-05-2018 01:43 PM

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

 

0aa1f1e62ba645c8a3068cb01e56e8dd_0690c000006FL68AAG.png

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

0 Kudos
16 REPLIES 16

Go to solution
fabianct
New Contributor III

‎08-31-2018 08:32 PM

We currently have the controller in the Cloud Software Version: 8.2r2 that is, which of the options you propose should we follow?

 

0 Kudos

Go to solution
samantha_lynn
Esteemed Contributor III

‎08-31-2018 08:26 PM

The directions depend a bit on what HiveManager platform you are using.

 

If you are using HiveManager Classic (myhive.aerohive.com)- 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.

 

If you are using HiveManager (formerly NG, cloud.aerohive.com)- You'll want to go to Configure> Open the Network Policy> Open the CWP object> Expand "Advanced Configuration"> Under the "Network Settings" header, select the "Customize" option, which will again give you four IP address and netmask fields to fill in to replace the 1.1.1.1 scope.

 

I'm sorry, I'm not sure I understand your last question, could you clarify what you mean by on the AP250 there is a problem to appreciate?

0 Kudos
GTM-P2G8KFN