Controllerless Networks

can anyone help, I have an issue that I had last year I assumed was fixed but it seems that it may have resolved itself before I could find the issue, but now the problem is back.

SETUP:
We have one IAP (AP535) with an IP of 10.81.67.26 (DHCP Assigned) with a Virtual IP of 10.81.67.250.
We have 3 Networks setup, Staff, Chromebooks, and Guest, the networks Staff and Chromebooks work fine.

Guest if I use no security then guest connects without issue if I apply a Captive portal to the Guest network that is when I start getting issues, on connecting to the Guest network (Vlan 65), It will obtain an IP (10.81.65.26) from the Windows DHCP Server 10.81.16.10, but then will open a URL with the image below.

I assume that because I have set up the Virtual Controller IP that this is what it is attempting to connect to.  the client device is unable to ping anything on the network, it can ping it's self 10.81.65.26 but not it's own gateway 10.81.65.1

It has the correct IP, Subnet, and Gateway, it is visible as a connected client in the WebUI with the Role Internal CP, I ass that is because that it has yet to get the captive portal and have the accept box ticked.

I have configured two other networks Visitors and Visitors2 (Visitors - no CP, Personal WPA2) & (Visitors 2- CP Internal Acknowledged) both using the same VLAN (65) Visitors works fine, Visitors2 has the same issue.



------------------------------
Simon Harbinson
------------------------------

Are you using the internal captive portal or external one?
Please post the relevant bits of the config.

------------------------------
Michael Clarke (Aruba)
------------------------------

Original Message:
Sent: Jan 13, 2021 06:04 AM
From: Simon Harbinson
Subject: Captive Portal - Issue

can anyone help, I have an issue that I had last year I assumed was fixed but it seems that it may have resolved itself before I could find the issue, but now the problem is back.

SETUP:
We have one IAP (AP535) with an IP of 10.81.67.26 (DHCP Assigned) with a Virtual IP of 10.81.67.250.
We have 3 Networks setup, Staff, Chromebooks, and Guest, the networks Staff and Chromebooks work fine.

Guest if I use no security then guest connects without issue if I apply a Captive portal to the Guest network that is when I start getting issues, on connecting to the Guest network (Vlan 65), It will obtain an IP (10.81.65.26) from the Windows DHCP Server 10.81.16.10, but then will open a URL with the image below.

I assume that because I have set up the Virtual Controller IP that this is what it is attempting to connect to.  the client device is unable to ping anything on the network, it can ping it's self 10.81.65.26 but not it's own gateway 10.81.65.1

It has the correct IP, Subnet, and Gateway, it is visible as a connected client in the WebUI with the Role Internal CP, I ass that is because that it has yet to get the captive portal and have the accept box ticked.

I have configured two other networks Visitors and Visitors2 (Visitors - no CP, Personal WPA2) & (Visitors 2- CP Internal Acknowledged) both using the same VLAN (65) Visitors works fine, Visitors2 has the same issue.

------------------------------
Simon Harbinson
------------------------------

Hi Michael, 

We were using and internal captive portal with LDAP, I have tried an external one as well but same problem, was not sure what bit you wanted so I have sanitized the config and uploaded that. 

One odd thing to note is that the Guest network works fine if I don't use a captive portal, it seems to be the act of setting an CP causes it to fail.

Simon

------------------------------
Simon Harbinson
------------------------------

Original Message:
Sent: Jan 14, 2021 12:52 AM
From: Michael Clarke (Aruba)
Subject: Captive Portal - Issue

Are you using the internal captive portal or external one?
Please post the relevant bits of the config.

------------------------------
Michael Clarke (Aruba)

Original Message:
Sent: Jan 13, 2021 06:04 AM
From: Simon Harbinson
Subject: Captive Portal - Issue

can anyone help, I have an issue that I had last year I assumed was fixed but it seems that it may have resolved itself before I could find the issue, but now the problem is back.

SETUP:
We have one IAP (AP535) with an IP of 10.81.67.26 (DHCP Assigned) with a Virtual IP of 10.81.67.250.
We have 3 Networks setup, Staff, Chromebooks, and Guest, the networks Staff and Chromebooks work fine.

Guest if I use no security then guest connects without issue if I apply a Captive portal to the Guest network that is when I start getting issues, on connecting to the Guest network (Vlan 65), It will obtain an IP (10.81.65.26) from the Windows DHCP Server 10.81.16.10, but then will open a URL with the image below.

I assume that because I have set up the Virtual Controller IP that this is what it is attempting to connect to.  the client device is unable to ping anything on the network, it can ping it's self 10.81.65.26 but not it's own gateway 10.81.65.1

It has the correct IP, Subnet, and Gateway, it is visible as a connected client in the WebUI with the Role Internal CP, I ass that is because that it has yet to get the captive portal and have the accept box ticked.

I have configured two other networks Visitors and Visitors2 (Visitors - no CP, Personal WPA2) & (Visitors 2- CP Internal Acknowledged) both using the same VLAN (65) Visitors works fine, Visitors2 has the same issue.

------------------------------
Simon Harbinson
------------------------------

Hi Simon,

have you changed the factory default certificate to an official one? Most browser will not accept the factory default (self signed) certificate and you run into issues as described above. 

a little bot old, but still valid:
https://community.arubanetworks.com/browse/articles/blogviewer?blogkey=719538b4-7db9-402f-a998-d80c91cf0cc9

------------------------------
-------------------------------------------------------------------------------
Florian Baaske
-------------------------------------------------------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
-------------------------------------------------------------------------------
Also visit the AirHeads Youtube Channel:
https://www.youtube.com/channel/UCFJCnuXFGfEbwEzfcgU_ERQ
-------------------------------------------------------------------------------
Feel free to visit my personal Blog
https://www.flomain.de
------------------------------

Original Message:
Sent: Jan 13, 2021 06:04 AM
From: Simon Harbinson
Subject: Captive Portal - Issue

can anyone help, I have an issue that I had last year I assumed was fixed but it seems that it may have resolved itself before I could find the issue, but now the problem is back.

SETUP:
We have one IAP (AP535) with an IP of 10.81.67.26 (DHCP Assigned) with a Virtual IP of 10.81.67.250.
We have 3 Networks setup, Staff, Chromebooks, and Guest, the networks Staff and Chromebooks work fine.

Guest if I use no security then guest connects without issue if I apply a Captive portal to the Guest network that is when I start getting issues, on connecting to the Guest network (Vlan 65), It will obtain an IP (10.81.65.26) from the Windows DHCP Server 10.81.16.10, but then will open a URL with the image below.

I assume that because I have set up the Virtual Controller IP that this is what it is attempting to connect to.  the client device is unable to ping anything on the network, it can ping it's self 10.81.65.26 but not it's own gateway 10.81.65.1

It has the correct IP, Subnet, and Gateway, it is visible as a connected client in the WebUI with the Role Internal CP, I ass that is because that it has yet to get the captive portal and have the accept box ticked.

I have configured two other networks Visitors and Visitors2 (Visitors - no CP, Personal WPA2) & (Visitors 2- CP Internal Acknowledged) both using the same VLAN (65) Visitors works fine, Visitors2 has the same issue.

------------------------------
Simon Harbinson
------------------------------

Hi Florian

I don't have that installed yet its on the list but we had this working before Xmas problem is I don't think I saved the config on the last day and it was shutdown, I'm sure this issue is related to routing but i cannot see what I'm missing as I'm sure the IP for the master controller are the same, but for what ever reason now it will not route to it.

Simon

------------------------------
Simon Harbinson
------------------------------

Original Message:
Sent: Jan 14, 2021 12:57 AM
From: Florian Baaske
Subject: Captive Portal - Issue

Hi Simon,

have you changed the factory default certificate to an official one? Most browser will not accept the factory default (self signed) certificate and you run into issues as described above. 

a little bot old, but still valid:
https://community.arubanetworks.com/browse/articles/blogviewer?blogkey=719538b4-7db9-402f-a998-d80c91cf0cc9

------------------------------
-------------------------------------------------------------------------------
Florian Baaske
-------------------------------------------------------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
-------------------------------------------------------------------------------
Also visit the AirHeads Youtube Channel:
https://www.youtube.com/channel/UCFJCnuXFGfEbwEzfcgU_ERQ
-------------------------------------------------------------------------------
Feel free to visit my personal Blog
https://www.flomain.de

Original Message:
Sent: Jan 13, 2021 06:04 AM
From: Simon Harbinson
Subject: Captive Portal - Issue

can anyone help, I have an issue that I had last year I assumed was fixed but it seems that it may have resolved itself before I could find the issue, but now the problem is back.

SETUP:
We have one IAP (AP535) with an IP of 10.81.67.26 (DHCP Assigned) with a Virtual IP of 10.81.67.250.
We have 3 Networks setup, Staff, Chromebooks, and Guest, the networks Staff and Chromebooks work fine.

Guest if I use no security then guest connects without issue if I apply a Captive portal to the Guest network that is when I start getting issues, on connecting to the Guest network (Vlan 65), It will obtain an IP (10.81.65.26) from the Windows DHCP Server 10.81.16.10, but then will open a URL with the image below.

I assume that because I have set up the Virtual Controller IP that this is what it is attempting to connect to.  the client device is unable to ping anything on the network, it can ping it's self 10.81.65.26 but not it's own gateway 10.81.65.1

It has the correct IP, Subnet, and Gateway, it is visible as a connected client in the WebUI with the Role Internal CP, I ass that is because that it has yet to get the captive portal and have the accept box ticked.

I have configured two other networks Visitors and Visitors2 (Visitors - no CP, Personal WPA2) & (Visitors 2- CP Internal Acknowledged) both using the same VLAN (65) Visitors works fine, Visitors2 has the same issue.

------------------------------
Simon Harbinson
------------------------------

If you say, it is a routing problem, is the client able to reach the VC IP (theoretically from a routing point of view)?

I would also trie another client/browser to make sure it is not a certificate issue.

------------------------------
-------------------------------------------------------------------------------
Florian Baaske
-------------------------------------------------------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
-------------------------------------------------------------------------------
Also visit the AirHeads Youtube Channel:
https://www.youtube.com/channel/UCFJCnuXFGfEbwEzfcgU_ERQ
-------------------------------------------------------------------------------
Feel free to visit my personal Blog
https://www.flomain.de
------------------------------

Original Message:
Sent: Jan 14, 2021 03:46 AM
From: Simon Harbinson
Subject: Captive Portal - Issue

Hi Florian

I don't have that installed yet its on the list but we had this working before Xmas problem is I don't think I saved the config on the last day and it was shutdown, I'm sure this issue is related to routing but i cannot see what I'm missing as I'm sure the IP for the master controller are the same, but for what ever reason now it will not route to it.

Simon

------------------------------
Simon Harbinson

Original Message:
Sent: Jan 14, 2021 12:57 AM
From: Florian Baaske
Subject: Captive Portal - Issue

Hi Simon,

have you changed the factory default certificate to an official one? Most browser will not accept the factory default (self signed) certificate and you run into issues as described above. 

a little bot old, but still valid:
https://community.arubanetworks.com/browse/articles/blogviewer?blogkey=719538b4-7db9-402f-a998-d80c91cf0cc9

------------------------------
-------------------------------------------------------------------------------
Florian Baaske
-------------------------------------------------------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
-------------------------------------------------------------------------------
Also visit the AirHeads Youtube Channel:
https://www.youtube.com/channel/UCFJCnuXFGfEbwEzfcgU_ERQ
-------------------------------------------------------------------------------
Feel free to visit my personal Blog
https://www.flomain.de

Original Message:
Sent: Jan 13, 2021 06:04 AM
From: Simon Harbinson
Subject: Captive Portal - Issue

can anyone help, I have an issue that I had last year I assumed was fixed but it seems that it may have resolved itself before I could find the issue, but now the problem is back.

SETUP:
We have one IAP (AP535) with an IP of 10.81.67.26 (DHCP Assigned) with a Virtual IP of 10.81.67.250.
We have 3 Networks setup, Staff, Chromebooks, and Guest, the networks Staff and Chromebooks work fine.

Guest if I use no security then guest connects without issue if I apply a Captive portal to the Guest network that is when I start getting issues, on connecting to the Guest network (Vlan 65), It will obtain an IP (10.81.65.26) from the Windows DHCP Server 10.81.16.10, but then will open a URL with the image below.

I assume that because I have set up the Virtual Controller IP that this is what it is attempting to connect to.  the client device is unable to ping anything on the network, it can ping it's self 10.81.65.26 but not it's own gateway 10.81.65.1

It has the correct IP, Subnet, and Gateway, it is visible as a connected client in the WebUI with the Role Internal CP, I ass that is because that it has yet to get the captive portal and have the accept box ticked.

I have configured two other networks Visitors and Visitors2 (Visitors - no CP, Personal WPA2) & (Visitors 2- CP Internal Acknowledged) both using the same VLAN (65) Visitors works fine, Visitors2 has the same issue.

------------------------------
Simon Harbinson
------------------------------

Have you tried making the captive portal plain text http?

------------------------------
Michael Clarke (Aruba)
------------------------------

Original Message:
Sent: Jan 14, 2021 03:46 AM
From: Simon Harbinson
Subject: Captive Portal - Issue

Hi Florian

I don't have that installed yet its on the list but we had this working before Xmas problem is I don't think I saved the config on the last day and it was shutdown, I'm sure this issue is related to routing but i cannot see what I'm missing as I'm sure the IP for the master controller are the same, but for what ever reason now it will not route to it.

Simon

------------------------------
Simon Harbinson

Original Message:
Sent: Jan 14, 2021 12:57 AM
From: Florian Baaske
Subject: Captive Portal - Issue

Hi Simon,

have you changed the factory default certificate to an official one? Most browser will not accept the factory default (self signed) certificate and you run into issues as described above. 

a little bot old, but still valid:
https://community.arubanetworks.com/browse/articles/blogviewer?blogkey=719538b4-7db9-402f-a998-d80c91cf0cc9

------------------------------
-------------------------------------------------------------------------------
Florian Baaske
-------------------------------------------------------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
-------------------------------------------------------------------------------
Also visit the AirHeads Youtube Channel:
https://www.youtube.com/channel/UCFJCnuXFGfEbwEzfcgU_ERQ
-------------------------------------------------------------------------------
Feel free to visit my personal Blog
https://www.flomain.de

Original Message:
Sent: Jan 13, 2021 06:04 AM
From: Simon Harbinson
Subject: Captive Portal - Issue

can anyone help, I have an issue that I had last year I assumed was fixed but it seems that it may have resolved itself before I could find the issue, but now the problem is back.

SETUP:
We have one IAP (AP535) with an IP of 10.81.67.26 (DHCP Assigned) with a Virtual IP of 10.81.67.250.
We have 3 Networks setup, Staff, Chromebooks, and Guest, the networks Staff and Chromebooks work fine.

Guest if I use no security then guest connects without issue if I apply a Captive portal to the Guest network that is when I start getting issues, on connecting to the Guest network (Vlan 65), It will obtain an IP (10.81.65.26) from the Windows DHCP Server 10.81.16.10, but then will open a URL with the image below.

I assume that because I have set up the Virtual Controller IP that this is what it is attempting to connect to.  the client device is unable to ping anything on the network, it can ping it's self 10.81.65.26 but not it's own gateway 10.81.65.1

It has the correct IP, Subnet, and Gateway, it is visible as a connected client in the WebUI with the Role Internal CP, I ass that is because that it has yet to get the captive portal and have the accept box ticked.

I have configured two other networks Visitors and Visitors2 (Visitors - no CP, Personal WPA2) & (Visitors 2- CP Internal Acknowledged) both using the same VLAN (65) Visitors works fine, Visitors2 has the same issue.

------------------------------
Simon Harbinson
------------------------------