Long time guest portal page loading while use Agile Controller Campus V1R2
We use a WLAN solution with guest authentication with Portal, located at Huawei Agile Controller Campus (V1R2C10SPC400).
When the guest user connects to WiFi, an IP address is assigned to him via DHCP.
Then he tries to visit some web pages. The system redirects him to the Guest Portal.
The user inputs his credentials and click “Login” button.
We noticed that need to wait about 40-60 second before “Success page” will appear. But, at the same time, after the user clicks “Login” within one-second user passed authentication and can go any other web page. We tested different kind of devices: Windows PC, MacOS, Android and iOS phones. Situation reproduced at all devices.We also tried different web-browsers.
“Loading” for 40-60 seconds
- x
- convention：
- Emotion(0)
|
In fact authentication passes successfully. It means there is some problem with pushing “Success page” to guest user. 1. First, we recorded capture by Wireshark at Agile server side. 10.XX.245.40 – ip address of Agile server 10.XX.248.94, 10.XX.248.95, 10.XX.248.92, 10.XX.248.91 – real ip address of devices, added to Agile.
From capture we can see: Agile sends Portal REQ_Auth message to all devices. Agile need to wait some time to receive the response from all devices. But really at one moment only one device in use (guest user uses one AP, which belong to one active AC). 2. We have 4 AC6605 devices total. It divided to 2 VRRP HSB groups. Each group uses one virtual ip address. We added all 4 devices with real ip addresses to Agile. Really at one moment only one device in use (guest user uses one AP, which belong to one active AC).
1. Add only devices with virtual ip address in case of using VRRP HSB.
10.XX.248.90 – virtual ip address of group 1 ( AC1 +AC2)
10.XX.248.93 – virtual ip address of group 1 ( AC3 +AC4)
2. Add ac-ip parameter to url-template, in order Agile will send authentication packet to only one device.
url-template name portal_temp
url http://guestpage.ru:8080/portal
url-parameter ssid ssid ac-ip ac-ip user-mac mac-address redirect-url url
// redirect-url url- if need to redirect to native page, after successful authentication.
web-auth-server agile-portal
server-ip XXX
port 50200
shared-key cipher XXX
url-template portal_temp
source-ip 10.XX.248.90 // set this ip address according ip address, used at Agile under
Resource>Device> Device Management
After these modifications “Success page” is pushed to guest terminal very quickly, within 1-2 seconds. |
|
|
In fact authentication passes successfully. It means there is some problem with pushing “Success page” to guest user. 1. First, we recorded capture by Wireshark at Agile server side. 10.XX.245.40 – ip address of Agile server 10.XX.248.94, 10.XX.248.95, 10.XX.248.92, 10.XX.248.91 – real ip address of devices, added to Agile.
From capture we can see: Agile sends Portal REQ_Auth message to all devices. Agile need to wait some time to receive the response from all devices. But really at one moment only one device in use (guest user uses one AP, which belong to one active AC). 2. We have 4 AC6605 devices total. It divided to 2 VRRP HSB groups. Each group uses one virtual ip address. We added all 4 devices with real ip addresses to Agile. Really at one moment only one device in use (guest user uses one AP, which belong to one active AC).
1. Add only devices with virtual ip address in case of using VRRP HSB.
10.XX.248.90 – virtual ip address of group 1 ( AC1 +AC2)
10.XX.248.93 – virtual ip address of group 1 ( AC3 +AC4)
2. Add ac-ip parameter to url-template, in order Agile will send authentication packet to only one device.
url-template name portal_temp
url http://guestpage.ru:8080/portal
url-parameter ssid ssid ac-ip ac-ip user-mac mac-address redirect-url url
// redirect-url url- if need to redirect to native page, after successful authentication.
web-auth-server agile-portal
server-ip XXX
port 50200
shared-key cipher XXX
url-template portal_temp
source-ip 10.XX.248.90 // set this ip address according ip address, used at Agile under
Resource>Device> Device Management
After these modifications “Success page” is pushed to guest terminal very quickly, within 1-2 seconds. |
|
Comment
- Politically sensitive content
- Content concerning pornography, gambling, and drug abuse
- Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
