topic Re: How to resolve the problem with captive portal seek 1.1.1.1 for Chrome Users in Aerohive Migrated Content

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

fabianct — Sat, 01 Sep 2018 03:13:35 GMT

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?

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

samantha_lynn — Sat, 01 Sep 2018 03:26:02 GMT

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?

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

fabianct — Sat, 01 Sep 2018 03:32:43 GMT

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

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

fabianct — Sat, 01 Sep 2018 03:36:56 GMT

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

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

samantha_lynn — Sat, 01 Sep 2018 03:37:02 GMT

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.

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

samantha_lynn — Sat, 01 Sep 2018 03:40:22 GMT

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.

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

fabianct — Sat, 01 Sep 2018 03:41:01 GMT

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?

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

samantha_lynn — Sat, 01 Sep 2018 03:43:14 GMT

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.

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

fabianct — Sat, 01 Sep 2018 03:46:26 GMT

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

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

fabianct — Sat, 01 Sep 2018 03:54:57 GMT

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.

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

samantha_lynn — Sat, 01 Sep 2018 03:56:53 GMT

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

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

fabianct — Sat, 01 Sep 2018 04:09:53 GMT

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

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

fabianct — Sat, 01 Sep 2018 05:49:07 GMT

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?

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

zharkov1968 — Tue, 04 Sep 2018 05:35:18 GMT

Thanks for this topic. Recently ran into the same problem. After upgrading Hive Manager and setting additional IPs for CWP it was working for awhile. Now guest devices fail to access new IP, like 10.0.4.1

Found that the firewall policy for guest users blocks access to internal network by default (10.0.0.0/255.0.0.0)

Question: For guests to be able to see CWP on say 10.0.4.1 should I allow access in the firewall policy for guest users?

Thanks in advance.

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

fabianct — Wed, 05 Sep 2018 01:46:21 GMT

Remember that you can use any network segment that you are not using in your network to place in 802.11a radio and another segment in 802b / g radio, now if that segment you have there is blocked with the firewall, it is recommended that you do not block it.

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

fabianct — Wed, 05 Sep 2018 20:43:14 GMT

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

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

fabianct — Wed, 05 Sep 2018 22:31:07 GMT

For step 3 of the post above, to give an example of what should be done, create a type A record in the local DNS point the name webserver.xyz.com.co pointing to the ip 192.168.8.1 and create another record type A with that same FQDN pointing to the ip 192.168.9.1