如何在 Ruijie Networks 設備上設定訪客 WiFi 與 Captive Portals

How to Configure Guest WiFi and Captive Portals on Ruijie Networks A Purple Technical Briefing - Approximately 10 minutes INTRODUCTION AND CONTEXT - 1 minute Welcome to the Purple Technical Briefing. I am your host, and over the next ten minutes we are going to cover everything you need to know about configuring guest WiFi and captive portals on Ruijie Networks hardware. If you are an IT manager, network architect, or venue operations director at a hotel, retail chain, stadium, or conference centre, and you have Ruijie kit on-site or you are evaluating it, this briefing is for you. Ruijie Networks is one of the fastest-growing enterprise wireless vendors globally. Their RG-WS series controllers, Reyee EG gateways, and cloud-managed access points are now deployed across thousands of venues in Europe, the Middle East, Asia, and beyond. But getting guest WiFi right on Ruijie hardware - specifically the captive portal piece - requires understanding a few architectural decisions upfront. Get those decisions wrong and you end up with a portal that breaks on iOS, guests who cannot authenticate, and a network that is either too open or too locked down. Let us fix that. TECHNICAL DEEP-DIVE - 5 minutes First, the architecture. Ruijie gives you three distinct deployment models for guest WiFi, and choosing the right one depends on your scale and your management approach. Model one is the Ruijie Cloud or JaCS managed portal. This is the native, built-in option. You log into Ruijie Cloud, navigate to Device Config, then Basic, create or edit your guest SSID, enable the Authentication toggle, and select Captive Portal as the mode. Ruijie's JaCS platform, which is their hospitality-focused management system, supports Hotel and Other scenarios and gives you a drag-and-drop portal builder with login options including one-click access, voucher codes, and account-based login. This is the right choice for smaller deployments - a single hotel, a boutique retail site, or a conference centre that wants a quick, branded splash page without external dependencies. Model two is the external captive portal via WISPr and RADIUS. This is the enterprise-grade approach, and it is what you need when you want to integrate Ruijie with a third-party guest WiFi intelligence platform - like Purple. Here, you navigate to Auth and Account in the Ruijie interface, select Captive Portal, set the Policy Mode to External, and point the Portal Server URL at your external platform. You then configure a RADIUS server group with the credentials your platform provides. The WISPr protocol handles the redirect and authentication handshake between the Ruijie gateway and the external portal. This model scales across hundreds of sites, gives you centralised analytics, and lets you run GDPR-compliant data capture workflows. Model three is standalone AP mode. Ruijie's Reyee access points running ReyeeOS version 1.219 or later can run a local captive portal without a gateway, which is useful for temporary deployments or small sites without an EG router. Now, the critical piece that most guides skip: VLAN isolation. When you create a guest SSID on Ruijie, you have two forwarding options - NAT mode and VLAN mode. NAT mode is simpler. The gateway assigns guest devices addresses from a dedicated pool, typically 192.168.23.0 slash 24 by default, and all guest traffic is NATted to the internet. This works, but it gives you less control. VLAN mode is the right choice for any serious deployment. You assign the guest SSID to a dedicated VLAN - say VLAN 100 - and use ACLs on the gateway to block guest traffic from reaching your corporate VLAN. The CLI command pattern looks like this: you create an extended access list, deny IP traffic from your guest subnet to your corporate subnet, permit everything else, and apply that access list inbound on the guest BVI interface. This is the same principle you would apply on Cisco Meraki, HPE Aruba, or Ruckus - Ruijie just has its own CLI syntax. Security standards matter here. Ruijie supports WPA3-Personal and WPA2/WPA3 mixed mode on guest SSIDs. For a guest network where you want zero-friction access, you typically run an open SSID with captive portal authentication rather than a pre-shared key. The captive portal becomes your authentication layer. If you need stronger security - say for a healthcare or financial services environment - you can layer IEEE 802.1X on top, using EAP-TLS or PEAP with a RADIUS server for certificate-based or credential-based authentication. Ruijie's RG-WS series controllers support full 802.1X with dynamic VLAN assignment, meaning you can push different VLANs to different user groups based on RADIUS attributes. The walled garden - or allowlist - is another area that trips people up. Before a guest authenticates through the captive portal, their device can only reach domains you explicitly whitelist. At minimum, you need to allow your portal platform's domain and IP address, any social login providers you are using, and Apple's captive portal detection endpoint, which is captive.apple.com. Miss that last one and iOS devices will show a broken portal experience. You configure the allowlist in Ruijie Cloud under Auth and Account, then Allowlist. IMPLEMENTATION RECOMMENDATIONS AND PITFALLS - 2 minutes Let me give you the four decisions that determine whether your Ruijie guest WiFi deployment succeeds or fails. Decision one: native portal versus external platform. If you are running more than five sites, or if you need to capture first-party data for marketing, use an external platform. Purple, for example, operates as a hardware-agnostic cloud overlay across 80,000-plus live venues. You point your Ruijie gateway at Purple's portal URL, configure the RADIUS credentials, and you get centralised analytics, GDPR-compliant data capture, and CRM integrations - all without touching the Ruijie hardware again. Purple has processed 440 million logins in 2024 alone and holds ISO 27001 certification, so the compliance piece is handled. Decision two: NAT versus VLAN. Always use VLAN mode for production deployments. NAT mode is fine for a proof of concept, but VLAN mode gives you proper Layer 3 isolation, easier firewall policy management, and the ability to apply QoS policies per VLAN. Decision three: bandwidth management. Ruijie's EG gateways have built-in QoS controls. Set per-user download and upload limits on the guest SSID - typically two to five megabits per second download for a standard guest network. This prevents a single guest streaming 4K video from degrading the experience for everyone else. If you are using an external platform, disable Client Escape on the Ruijie side to ensure the platform's bandwidth controls take effect correctly. Decision four: session timeout and re-authentication. Set a sensible session timeout - eight to 24 hours for hospitality, shorter for retail or events. Ruijie lets you configure this per portal policy. Pair it with a post-login redirect URL so guests land on your venue's website or a promotional page after connecting. The most common pitfall I see is teams deploying a captive portal without testing it on iOS and Android simultaneously. Apple and Google both have captive portal detection mechanisms that behave differently. Test both before go-live. The second most common pitfall is forgetting to synchronise the portal configuration to the EG product in JaCS - there is an explicit Synchronise button you must click after creating or editing a portal, otherwise the gateway does not pick up the changes. RAPID-FIRE Q AND A - 1 minute Let me run through the questions I get asked most often. Can Ruijie APs run a captive portal without a gateway? Yes, on ReyeeOS 1.219 or later, but functionality is limited compared to gateway-based deployments. Does Ruijie support 802.1X for guest networks? Yes, the RG-WS series controllers support full 802.1X with dynamic VLAN assignment via RADIUS. Can I integrate Ruijie with Purple? Yes. Configure the external captive portal mode, point the portal URL at Purple's endpoint, set up the RADIUS server group with Purple's credentials, and add Purple's domains to the allowlist. Purple's hardware-agnostic architecture handles the rest. Does WPA3 work with captive portals? Yes. You run an open SSID for the captive portal flow. WPA3 applies to authenticated SSIDs. For guest networks, the portal itself is the authentication layer. SUMMARY AND NEXT STEPS - 1 minute To summarise: Ruijie Networks gives you a capable, flexible platform for guest WiFi and captive portal deployment. The three deployment models - native cloud portal, external RADIUS-based portal, and standalone AP - cover everything from a single-site boutique hotel to a multi-site retail chain. The key decisions are VLAN isolation over NAT, external platform for any multi-site or data-capture use case, and proper walled garden configuration to avoid iOS authentication failures. Your next steps: audit your current Ruijie firmware versions to confirm ReyeeOS compatibility, decide whether you need native or external portal management, and if you are running more than five sites or need analytics, speak to Purple about integrating their platform with your Ruijie infrastructure. You can find Purple's integration documentation and request a demo at purple.ai. Thanks for listening. We will see you in the next briefing.