Aruba 專用的 Captive Portal
本權威技術參考指南旨在協助設定 Aruba Instant (IAP) 與 Aruba Central 託管的存取點,將訪客使用者重導向至 Purple 高轉換率且安全的外部 Captive Portal。本指南涵蓋逐步的訪客 SSID 設定、外部 Captive Portal 重導向、RADIUS 伺服器驗證與計費參數、Walled Garden 排除清單以及 WISPr 支援。
收聽此指南
查看播客逐字稿
📚 核心系列的一部分:多租戶 WiFi →
- Executive Summary
- Technical Deep-Dive
- The Captive Portal Redirect Flow
- RADIUS Authentication and Accounting Parameters
- The Walled Garden (Exception List) Architecture
- Implementation Guide
- Aruba Instant (IAP) Configuration (ArubaOS 8.x)
- Aruba Central Configuration (AOS-8 and AOS-10)
- Best Practices
- 1. Secure Certificate Management
- 2. Network Segmentation and Compliance
- 3. Optimising WISPr and Captive Portal Detection
- Troubleshooting & Risk Mitigation
- Captive Portal Troubleshooting Matrix
- ROI & Business Impact
- Operational Efficiency and Scalability
- Data Monetisation and Marketing ROI
- Cost-Benefit Analysis: Native Aruba vs. Purple Integration

Executive Summary
For enterprise wireless engineers, network architects, and venue operations directors, deploying a robust guest wireless infrastructure is no longer just about providing basic internet access. Modern venues require a solution that balances strict network security, regulatory compliance, and a high-converting guest experience. While HPE Aruba's native captive portal capabilities are highly reliable, they lack the sophisticated marketing data capture, global multi-site scalability, and real-time location and demographic analytics required by enterprise venues in hospitality, retail, and public sectors.
By integrating Purple directly with Aruba Instant (IAP) or Aruba Central managed access points, organisations can replace basic local splash pages with a secure, highly-scalable, global guest portal. This integration leverages standard network protocols, including Remote Authentication Dial-In User Service (RADIUS) and Wireless Internet Service Provider roaming (WISPr), to deliver seamless, secure, and brand-consistent onboarding. This technical reference guide provides the exact configuration parameters, architectural diagrams, and troubleshooting workflows required to successfully deploy Purple on Aruba infrastructure.
Technical Deep-Dive
The integration of Purple with Aruba wireless infrastructure relies on a standard external captive portal redirect and RADIUS authentication flow. This architecture ensures that user authentication and traffic accounting are handled securely in the cloud, while local access points enforce access control and quality of service (QoS) policies.
The Captive Portal Redirect Flow
When an unauthenticated client associates with the guest Service Set Identifier (SSID), the Aruba access point intercepts the client's initial HTTP request (typically TCP port 80) and performs a HTTP 302 redirect to Purple's cloud-hosted splash page.
+--------------+ +-----------------+ +------------------+ +------------------+
| Guest Device | | Aruba AP / AP | | Purple Captive | | Purple RADIUS |
| (Client) | | (Central/IAP) | | Portal (Cloud) | | Server (Cloud) |
+--------------+ +-----------------+ +------------------+ +------------------+
| | | |
|-- 1. Associates to SSID ---->| | |
| | | |
|-- 2. HTTP Request (TCP 80) ->| | |
| |-- 3. HTTP 302 Redirect ------>| |
|<-- 4. Presents Splash Page ----------------------------------| |
| | | |
|-- 5. Submits Login Form ------------------------------------>| |
| | |-- 6. RADIUS Access-Request --->|
| |<-- 7. RADIUS Access-Accept ------------------------------------|
| | (with Session Timeout) | |
|<-- 8. Internet Granted ------| | |
| | | |
| |-- 9. RADIUS Accounting Start --------------------------------->|
| |-- 10. RADIUS Accounting Interim (every 5 min) ---------------->|

RADIUS Authentication and Accounting Parameters
Once the guest submits their credentials or completes a social login on the Purple splash page, the Purple portal backend communicates with the local Aruba access point or controller to initiate RADIUS authentication. The Aruba AP acts as the Network Access Server (NAS) and sends a RADIUS Access-Request to Purple's cloud RADIUS servers on UDP port 1812.
To ensure accurate session tracking, policy enforcement, and reporting, the following RADIUS attributes must be exchanged:
| Attribute Name | Attribute ID | Description | Practical Context |
|---|---|---|---|
| NAS-IP-Address | 4 | The management IP address of the Aruba virtual controller or AP. | Identifies the physical hardware originating the authentication request. |
| Calling-Station-Id | 31 | The MAC address of the client device (typically formatted as XX-XX-XX-XX-XX-XX). |
Used by Purple to track unique devices and enforce MAC caching for returning guests. |
| Called-Station-Id | 30 | The MAC address of the AP radio (BSSID) combined with the SSID name (formatted as MAC:SSID). |
Crucial for Purple to identify the exact physical venue and specific SSID the user is connecting to. |
| Acct-Session-Id | 44 | A unique identifier generated by the AP for each client session. | Links authentication events with subsequent accounting start, interim, and stop records. |
| Acct-Status-Type | 40 | Indicates the type of accounting record: Start (1), Stop (2), or Interim-Update (3). |
Enables real-time tracking of active sessions and accurate dwell-time calculations. |
| Acct-Interim-Interval | 85 | Specifies the frequency (in seconds) of interim accounting updates sent by the AP. | Must be set to 300 seconds (5 minutes) to ensure Purple's analytics dashboard displays accurate real-time data. |
The Walled Garden (Exception List) Architecture
Before a user is authenticated, the Aruba AP restricts all traffic except for destinations explicitly defined in the Walled Garden (or exception list). Because Purple's portal is cloud-hosted and relies on external identity providers (such as Google, Facebook, and Apple) for social authentication, the AP must allow unauthenticated clients to resolve DNS and communicate with these external domains.
If any required domain is omitted from the walled garden, the guest will experience a blank page, broken CSS, missing images, or a complete timeout during the login flow.

Implementation Guide
Deploying Purple on Aruba wireless infrastructure can be achieved via Aruba Instant (IAP) running ArubaOS 8.x (on-premises virtual-controller mode) or Aruba Central (cloud-managed AOS-8 or AOS-10).
Aruba Instant (IAP) Configuration (ArubaOS 8.x)
Step 1: Configure RADIUS Servers
- Log in to the Aruba Instant AP virtual controller web interface.
- Navigate to Security > Authentication Server and click New.
- Configure the Primary RADIUS Server with the following parameters:
- Name:
Purple_Primary - IP Address:
34.94.146.135 - Auth Port:
1812 - Acct Port:
1813 - Shared Key: [Provided in your Purple Venue Dashboard]
- Name:
- Click OK to save.
- Click New again to configure the Secondary RADIUS Server:
- Name:
Purple_Secondary - IP Address:
34.94.183.201 - Auth Port:
1812 - Acct Port:
1813 - Shared Key: [Provided in your Purple Venue Dashboard]
- Name:
- Click OK to save.
Step 2: Create the Captive Portal Profile
- Navigate to Security > Captive Portal and click New.
- Configure the profile with the following settings:
- Name:
Purple_Portal - Type:
External - IP or Hostname:
portal.venuewifi.com - URL:
/ - Port:
443 - Use HTTPS:
Enabled - Redirect URL:
https://portal.venuewifi.com - WISPr:
Enabled(Crucial for auto-triggering the portal on iOS and Android devices)
- Name:
- Click OK to save.
Step 3: Configure the Walled Garden Whitelist
- In the Security > Captive Portal menu, select your newly created
Purple_Portalprofile. - Under the Walled Garden section, click the link to open the whitelist configuration.
- Add the following core Purple domains:
*.purple.ai*.cloudfront.net*.venuewifi.com
- If social login is enabled, add the respective domains (e.g.,
*.google.com,*.facebook.com,*.apple.com). - Click Save.
Step 4: Create and Configure the Guest SSID
- Navigate to Network > New to start the WLAN wizard.
- On the WLAN Settings tab:
- Name (SSID):
Guest-WiFi - Primary Usage:
Guest - Click Next.
- Name (SSID):
- On the VLAN tab, configure IP and VLAN assignment according to your network architecture (typically Client IP assignment: Network Assigned on a dedicated guest VLAN). Click Next.
- On the Security tab:
- Splash Page Type:
External - Captive Portal Profile: Select
Purple_Portal - Auth Server 1: Select
Purple_Primary - Auth Server 2: Select
Purple_Secondary - Reauth Interval:
1440(24 hours, or as per venue policy) - Accounting:
Enabled - Accounting Interval:
5minutes
- Splash Page Type:
- Click Next to proceed to the Access tab. Ensure the default guest rule allows DHCP and DNS pre-authentication, then click Finish.
Aruba Central Configuration (AOS-8 and AOS-10)
Aruba Central AOS-8
- Navigate to Devices under the Manage section of your group in Aruba Central.
- Click Config (gear icon) on the top right, then go to the WLANs tab and click + Add SSID.
- In Step 1: General, enter the SSID name (e.g.,
Guest-WiFi) and click Next. - In Step 2: VLANs, configure your guest VLAN mapping and click Next.
- In Step 3: Security:
- Set Security Level to
Visitors. - Set Type to
External Captive Portal. - Ensure Key Management is set to
Open(do not use Enhanced Open/OWE for standard guest portals as it can cause client compatibility issues). - Click the + icon next to Captive Portal Profile to add a new profile:
- Name:
Purple_Central_Portal - IP or Hostname:
portal.venuewifi.com - URL:
/ - Port:
443 - Redirect URL:
https://portal.venuewifi.com - Use HTTPS:
True - Captive Portal Failure:
Deny Internet(Recommended for security compliance)
- Name:
- Click Save.
- Click the + icon next to Primary Server and Secondary Server to add the Purple RADIUS servers using the IPs
34.94.146.135and34.94.183.201respectively, with ports1812(Auth) and1813(Acct). - Expand Advanced Settings, scroll to Accounting, select
Use authentication servers, and set Accounting Interval to5minutes.
- Set Security Level to
- Scroll down to the Walled Garden section, click + Add, and input the required Purple and social login domains.
- Click Save Settings.
Aruba Central AOS-10
In AOS-10, the walled garden configuration moves from the WLAN Security tab to Access Rules.
- Follow the same SSID and RADIUS configuration steps as AOS-8 above.
- In the SSID wizard, navigate to the Access tab.
- Click + Add Role and create a pre-authentication role named
Purple_Pre_Auth. - In the rules editor for this role, configure explicit Allow rules for DNS, DHCP, and the required walled garden domains (e.g.,
*.purple.ai,*.venuewifi.com). - Scroll down to Assign Pre-Authentication Role, enable the option, and select
Purple_Pre_Authfrom the dropdown. - The post-authorisation role (typically matching the SSID name) should remain configured with
Allow any to all destinationsor your specific corporate access policies. - Click Save Settings.
Best Practices
To ensure maximum performance, security, and compliance, network architects must adhere to the following industry standards and vendor-neutral best practices when deploying captive portals on Aruba and Purple.
1. Secure Certificate Management
Aruba access points must present a valid, trusted SSL/TLS certificate during the captive portal redirect flow.
- Avoid Self-Signed Certificates: If the AP presents a self-signed certificate, modern browsers will display a highly visible "Your connection is not private" warning, severely damaging guest trust and reducing conversion rates.
- Deploy a Trusted CA Certificate: Upload a wildcard certificate from a globally recognised Certificate Authority (CA) to your Aruba Central global settings or Instant virtual controllers. Ensure that the intermediate and root certificates are combined into a single file to complete the trust chain.
2. Network Segmentation and Compliance
Guest traffic must be kept entirely separate from corporate and administrative traffic to mitigate security risks and ensure compliance with industry standards.
- VLAN Isolation: Map the guest SSID to a dedicated, non-routable VLAN. Use Access Control Lists (ACLs) on the upstream core switch or firewall to prevent any routing between the guest VLAN and internal corporate subnets.
- PCI DSS Compliance: If your venue processes card payments (e.g., retail point-of-sale), network segmentation is a mandatory requirement under PCI DSS Requirement 1.2 [3]. Guest WiFi must be physically or logically isolated from the Cardholder Data Environment (CDE).
- GDPR and Data Privacy: Ensure that the Purple portal is configured to display explicit, un-ticked consent checkboxes for marketing opt-ins, meeting the strict requirements of the General Data Protection Regulation (GDPR) [4].
3. Optimising WISPr and Captive Portal Detection
Modern mobile operating systems use active probing to detect captive portals immediately upon association.
- Enable WISPr: Always ensure that WISPr support is enabled in your Aruba captive portal profile. This protocol passes XML-formatted metadata to the client operating system, allowing iOS (Captive Network Assistant) and Android (Captive Portal Login) to gracefully launch the login screen in a dedicated browser window.
- Prevent "Enhanced Open" (OWE) Issues: While Opportunistic Wireless Encryption (OWE) provides encryption on open networks, many legacy client devices do not support it. For public guest networks, stick to standard Open key management to maximise device compatibility.
Troubleshooting & Risk Mitigation
Even with meticulous planning, captive portal deployments can encounter common failure modes. The following troubleshooting matrix provides immediate, actionable steps for wireless engineers.
Captive Portal Troubleshooting Matrix
| Symptom | Probable Cause | Diagnostic Steps | Actionable Solution |
|---|---|---|---|
| Guest associates but the splash page does not load (Timeout/Blank Page). | Missing or incomplete Walled Garden configuration. | Attempt to ping portal.venuewifi.com from a wired device on the same VLAN. Check if the device is trying to load external resources (e.g., social login scripts) that are blocked. |
Explicitly add *.purple.ai, *.venuewifi.com, and *.cloudfront.net to the Aruba walled garden. Verify that DNS resolution is allowed in the pre-auth role. |
| Guest is redirected but browser displays an SSL/TLS Certificate Warning. | The Aruba AP is presenting an untrusted or self-signed certificate for the local redirect page. | Inspect the browser certificate details to see which certificate is being presented. | Upload a valid, trusted SSL certificate signed by a public CA to the Aruba virtual controller or Central global settings. |
| Guest completes the login form but is not granted internet access (Redirect Loop). | RADIUS communication failure between the Aruba AP and Purple servers. | Check the Aruba virtual controller logs for RADIUS timeouts or access-rejects. Run show auth-survivability or check firewall logs. |
Verify that outbound UDP ports 1812 (Auth) and 1813 (Acct) are open on your perimeter firewall. Ensure the RADIUS shared secret matches exactly on both Purple and Aruba. |
| The captive portal does not auto-popup on iOS or Android devices. | WISPr is disabled, or the AP is blocking the operating system's captive portal detection URLs. | Verify if the device can access the internet without logging in, or if it remains connected with "No Internet" and no popup. | Enable WISPr in the Aruba captive portal profile. Ensure that captive portal detection URLs (e.g., captive.apple.com, connectivitycheck.gstatic.com) are not blocked by custom pre-auth ACLs. |
| Real-time dwell-time analytics are inaccurate or missing in Purple. | RADIUS Accounting is disabled or the accounting interval is set too high. | Check the AP configuration to see if accounting is enabled and inspect the interval. | Enable RADIUS Accounting on the Aruba SSID. Set the Accounting Interval to exactly 5 minutes (300 seconds) to ensure regular session updates. |
ROI & Business Impact
Transitioning from a basic, local captive portal to an enterprise-grade WiFi intelligence platform like Purple delivers measurable business outcomes across operations, marketing, and network management.
Operational Efficiency and Scalability
Managing individual local captive portals across hundreds of retail stores, hotels, or public venues is an administrative bottleneck. Purple provides a centralised, cloud-managed console that allows IT teams to deploy, update, and audit captive portal configurations globally with a single click. This reduces configuration drift, ensures consistent branding, and slashes administrative overhead by up to 60%.
Data Monetisation and Marketing ROI
For industries like Retail and Hospitality, guest WiFi is a powerful channel for customer acquisition and engagement. Purple replaces anonymous connections with rich demographic profiles.
- Direct Integration: Purple integrates with CRM and marketing automation platforms to trigger real-time, context-aware campaigns. For example, a retail venue can trigger a personalised discount SMS the moment a loyalty customer connects to the guest WiFi.
- Measurable Footfall Analytics: By analysing RADIUS accounting data and BSSID associations, Purple provides highly accurate dwell-time, return-rate, and path-analysis reporting. This data enables venue operations directors to optimise staffing levels, evaluate window display effectiveness, and measure the direct ROI of marketing campaigns.
Cost-Benefit Analysis: Native Aruba vs. Purple Integration
| Feature / Metric | Native Aruba Local Portal | Aruba + Purple Integration | Business Impact |
|---|---|---|---|
| Centralised Multi-Site Management | Limited. Requires individual configuration per virtual controller or complex Central group mapping. | Fully Centralised. Manage thousands of venues and SSIDs from a single cloud dashboard. | Reduces IT overhead and eliminates configuration drift across distributed estates. |
| Data Capture & Compliance | Basic form capture. No built-in GDPR/CCPA consent validation workflows. | Enterprise-grade. Automated, legally-compliant consent tracking with real-time API sync to CRMs. | Mitigates legal risk and ensures compliance with global privacy regulations [4]. |
| Social Authentication | Requires custom external web development and manual API maintenance. | Out-of-the-box support for Google, Facebook, Apple, Microsoft, LinkedIn, and SMS. | Increases conversion rates by up to 40% through friction-free login options. |
| Analytics & Reporting | Basic session logs (IP, MAC, connect time). No demographic or behaviour tracking. | Rich analytics: age, gender, dwell-time, return rates, heatmaps, and cross-venue roaming. | Drives marketing ROI and provides actionable business intelligence for operations. |
關鍵定義
Captive Portal
在向新連接 Wi-Fi 網路的使用者授予更廣泛的網路資源存取權限之前,向其顯示的網頁。
用於收集訪客數據、強制執行服務條款,並展示品牌行銷內容。
RADIUS (Remote Authentication Dial-In User Service)
一種網路協定,為連接和使用網路服務的使用者提供集中式的驗證、授權和計費 (AAA) 管理。
Purple 作為外部 RADIUS 伺服器,負責驗證訪客身分並追蹤其工作階段持續時間。
WISPr (Wireless Internet Service Provider roaming)
一種草案協定,使獨立的無線網際網路服務供應商能夠允許使用者使用通用的登入入口網站漫遊到彼此的網路。
在 Aruba AP 上啟用 WISPr 可讓現代智慧型手機自動偵測 Captive Portal,並在系統原生視窗中顯示 Splash 頁面。
Walled Garden
一組受限制的網站或網域,允許未經驗證的使用者在完成 Captive Portal 登入流程之前進行存取。
對於允許訪客在通過驗證之前載入 Splash 頁面資產(CSS、JS、圖片)並存取社群登入提供商(Google、Facebook)至關重要。
BSSID (Basic Service Set Identifier)
特定 SSID 的無線存取點無線介面的 MAC 位址。
在 RADIUS Called-Station-Id 屬性中傳送,允許 Purple 將使用者的物理位置對應到特定的 AP。
NAS-IP-Address
發起 RADIUS 請求的網路存取伺服器(Aruba AP 或控制器)的 IP 位址。
用於 RADIUS 封包中,以識別是哪一個實體硬體正在請求驗證。
RadSec
一種透過 TCP 使用傳輸層安全性協定 (TLS) 來確保 RADIUS 交易安全的協定。
用於在本地 AP 與 Purple 的雲端之間傳輸不受信任的公用網路時,加密 RADIUS 驗證和計費流量。
Enhanced Open (OWE)
Wi-Fi Certified Easy Connect 的延伸功能,可在不需輸入密碼的情況下,對開放式網路上的無線傳輸進行加密。
可能會與較舊的訪客裝置產生相容性問題;建議公用 Captive Portal 使用標準的 Open 安全性。
範例
企業無線工程師正在擁有 150 家門市的全國連鎖零售商中部署顧客 WiFi。每家門市配備 3-5 台透過 Aruba Central 管理的 Aruba Instant AP。行銷團隊要求提供具有 Facebook 和 Google 社群登入選項的品牌化 Captive Portal,而合規團隊則要求顧客流量必須與門市的銷售點系統 (PoS) 網路完全隔離。應如何進行架構設計與設定?
- 網路分割:將 Aruba AP 上的顧客 SSID 對應至 VLAN 100。將本地交換器連接埠設定為 Trunk 連接埠並允許 VLAN 100。在門市的閘道器防火牆上,為 VLAN 100 設定 DHCP 範圍與僅限出站的 NAT 策略。在防火牆上套用 ACL,以捨棄所有從 VLAN 100 傳送到 PoS VLAN (VLAN 10) 的流量。
- Aruba Central 中的 RADIUS 與 Portal 設定:在 VLAN 100 上建立名為「Store-Guest」的新 SSID。將安全性設定為「Visitors」,並將 Splash Page 設定為「External Captive Portal」。新增 Purple 的主要 RADIUS 伺服器 (34.94.146.135) 與次要伺服器 (34.94.183.201),連接埠為 1812/1813。啟用 RADIUS Accounting,間隔時間為 5 分鐘。
- Walled Garden:在 Aruba Central 中設定 Walled Garden,使其包含:.purple.ai、.venuewifi.com、.cloudfront.net (用於 Purple 核心),以及社群登入網域:.google.com、.googleapis.com、.gstatic.com (用於 Google) 和 .facebook.com、.fbcdn.net、connect.facebook.net (用於 Facebook)。
- 測試:將測試裝置連線至「Store-Guest」,確認 DHCP 在 VLAN 100 上分配了 IP,確認瀏覽器透過 HTTPS 重新導向至 Purple portal,完成 Facebook 登入,並驗證已授予網際網路存取權限,同時內部 PoS 資源仍完全無法存取。
一個擁有 50,000 個座位的體育場館正在 AOS-10 上運行 Aruba Central,並配備高密度 AP-555 存取點。在活動高峰期,數千名使用者嘗試同時連線至顧客 WiFi。IT 總監擔心 Captive Portal 重新導向對虛擬控制器的效能影響,並希望確保驗證程序儘可能快速且具備彈性。應套用哪些進階設定?
- 預先驗證角色 (AOS-10):在 AOS-10 中,設定名為「Stadium-Pre-Auth」的專用預先驗證角色。套用允許 DHCP (UDP 67-68)、DNS (UDP 53) 以及流向 Purple Walled Garden 網域的出站流量的 ACL。在 SSID 設定中將此角色指派為「Pre-Authentication Role」。這會將封包過濾工作從中央控制器卸載到各個 AP,從而分散負載。
- RADIUS 負載平衡:在 Aruba Central 中,啟用跨主要和次要 Purple RADIUS 伺服器的 RADIUS 負載平衡。這能在高峰連入期間平均分配驗證負載。
- 伺服器卸載:在 Captive Portal Profile 設定中啟用「Server Offload」。這可防止非瀏覽器用戶端應用程式(如背景行動應用程式、系統更新或 IoT 裝置)重複重新導向至外部 Captive Portal,從而節省 AP CPU 週期和 WAN 頻寬。
- Captive Portal 失敗策略:將「Captive Portal Failure」設定為「Deny Internet」。雖然「Allow Internet」看似對客戶友好,但在極端網路事件期間,這可能會導致不受控制的開放存取,從而繞過安全控制並耗盡 DHCP 位址池。
練習題
Q1. 網路工程師在 Aruba Instant AP 叢集上設定了新的訪客 SSID。測試時,他們連線到該 SSID,但瀏覽器顯示逾時錯誤,而不是出現 Purple 品牌形象的 splash page。此問題最可能的起因是什麼?應採取哪些疑難排解步驟?
提示:思考在驗證之前,用戶端裝置需要什麼才能連線到雲端託管的 splash page。
查看標準答案
最可能的起因是遺失或不完整的 Walled Garden 設定,或是 DNS 解析問題。在驗證之前,AP 會阻擋除白名單網域以外的所有流量。如果 Purple 網域(.purple.ai、.venuewifi.com、*.cloudfront.net)不在 walled garden 中,用戶端就無法載入 splash page。疑難排解步驟:1. 確認用戶端裝置已透過 DHCP 取得有效的 IP 位址和 DNS 伺服器。2. 嘗試從同一 VLAN 上的有線裝置解析「portal.venuewifi.com」,以確認 DNS 正常運作。3. 檢查 Aruba AP 設定,確保 Walled Garden 白名單已啟用且包含所有必要的 Purple 網域。4. 確認預先驗證角色允許傳送 DNS 流量(UDP 連接埠 53)至 DNS 伺服器。
Q2. 在大型會議中心部署 Purple 訪客 WiFi 期間,IT 團隊回報訪客裝置連線成功,但每隔 15 分鐘就會被要求重新登入。預期的行為是讓訪客保持登入狀態 24 小時。應檢查哪些 Aruba 和 Purple 設定參數來解決此問題?
提示:查看控制工作階段生命週期和重新驗證間隔的參數。
查看標準答案
此問題是由工作階段逾時或重新驗證間隔設定不一致所引起的。若要解決此問題:1. 檢查 Aruba SSID 安全性索引標籤上的「Reauth Interval」(重新驗證間隔);應將其設定為 1440 分鐘(24 小時),而非 15 分鐘。2. 檢查 Purple RADIUS 伺服器在 Access-Accept 訊息中傳回的「Session Timeout」屬性。如果 Purple 設定的工作階段生命週期較短,將會強制進行重新驗證。3. 確保在 Aruba SSID 上啟用了 MAC 驗證。這可讓 AP 在 24 小時的視窗內,自動透過訪客的 MAC 位址與 Purple 的資料庫進行驗證,而無需再次向訪客顯示 splash page。
Q3. 某公共部門機構正使用 AOS-10 上的 Aruba Central 在多個圖書館部署訪客 WiFi。安全性原則規定所有訪客流量都必須進行空中加密,但圖書館館長希望提供無縫、無障礙的登入體驗。無線架構師如何利用 Aruba 和 Purple 同時滿足這兩項需求?
提示:考慮 Open、OWE (Enhanced Open) 以及 WPA2/WPA3-Enterprise 之間的差異,以及它們如何與 Captive Portal 互動。
查看標準答案
為了同時實現空中加密和無縫的 Captive Portal 體驗,架構師應部署「Enhanced Open」(機會性無線加密 - OWE),如果需要相容舊型裝置,則使用過渡模式。Enhanced Open 無需預先共用金鑰即可加密用戶端與 AP 之間的無線連線,保護訪客免受被動竊聽。1. 在 Aruba Central 中設定訪客 SSID,將安全性層級(Security Level)設為「Visitors」,金鑰管理(Key Management)設為「Enhanced Open」。2. 啟用「OWE Transition Mode」並將其與標準 Open 訪客 SSID 關聯,以支援不支援 WPA3 OWE 的舊型裝置。3. 照常設定指向 Purple 的 External Captive Portal 設定檔。此組合可確保現代裝置自動獲得加密的無線傳輸,同時仍能重導向至 Purple splash page 以進行資料收集和合規性確認。
繼續閱讀本系列
Cisco WLC and Catalyst Integration with Purple WiFi: Step-by-Step Guest Access Guide
本權威指南詳細介紹 Cisco Catalyst 9800 WLC 與 Purple WiFi 的逐步整合。內容涵蓋用於訪客 Captive Portal 的外部網頁驗證、用於員工安全存取的 802.1X EAP-TLS,以及用於多租戶動態 VLAN 隔離的 Cisco iPSK。
CommScope Ruckus 與 Purple WiFi 整合:安裝與設定指南
本技術參考指南為 CommScope Ruckus 架構與 Purple WiFi 的整合提供了權威的設定指南。其中詳細介紹了使用 Guest WiFi Captive Portal、透過 802.1X 的安全員工 WiFi,以及使用 Ruckus Dynamic PSK 的多租戶網路隔離的逐步部署步驟。
Allied Telesis 基地台與 Purple WiFi 整合
本指南提供將 Allied Telesis TQ 系列基地台與 Purple WiFi 整合的完整設定指南。內容涵蓋外部 Captive Portal 重新導向、802.1X RADIUS 驗證,以及使用私有預共用金鑰 (PPSK) 進行動態 VLAN 導向,以實現安全的多租戶部署。