How to Configure Guest WiFi and Captive Portals on Ruijie Networks

This technical guide details the configuration of guest WiFi and captive portals on Ruijie Networks hardware, covering both native cloud portals and external RADIUS integrations. It provides IT managers and network architects with actionable steps for VLAN isolation, walled garden setup, and third-party platform integration to drive analytics and revenue.

📖 6 min read📝 1,447 words🔧 2 worked examples❓ 3 practice questions📚 8 key definitions

Listen to this guide

View podcast transcript

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.

📚 Part of our core series: Captive Portal Guide →

Executive Summary

Configuring guest WiFi and Captive Portals on Ruijie Networks hardware requires a clear understanding of the platform architecture, particularly the choice between native cloud portals and external RADIUS integrations. This technical guide provides IT managers, network architects, and venue operations managers with the critical steps to deploy secure, isolated, and scalable guest networks using Ruijie RG-WS controllers and Reyee EG gateways. We cover the transition from simple NAT forwarding to robust VLAN isolation, configuring external Captive Portals via WISPr, and integrating third-party platforms like Purple to capture first-party data and drive revenue. Whether you manage a single hotel or a multi-site retail portfolio, this guide provides the practical, vendor-neutral configuration steps required to build a compliant and high-performing wireless network.

Technical Deep-Dive

Ruijie Networks offers a robust, professional wireless architecture that supports multiple deployment models for guest access. The core decision for any network architect is selecting the appropriate authentication flow and isolation strategy.

Captive Portal Deployment Models

Ruijie supports three distinct deployment models for Captive Portals, each suited to different operational needs:

Native Cloud Portal (Ruijie JaCS): The integrated Ruijie Cloud platform, particularly the JaCS hospitality interface, provides a drag-and-drop portal builder. This model is configured under "Device Config", where the SSID authentication is set to Captive Portal. It supports basic login options like one-click access and voucher codes. This is suitable for single locations that do not require deep analytics or external CRM integrations.
External Captive Portal (WISPr/RADIUS): For enterprise deployments, multi-site retail, and large public venues, the external portal model is mandatory. This approach uses the WISPr protocol to redirect guest traffic to a third-party platform such as Purple. Authentication occurs via an external RADIUS server group using PAP encryption. This model enables advanced data capture, GDPR compliance management, and seamless integration with existing marketing systems.
Standalone AP Portal: Ruijie Reyee Access Points running ReyeeOS 1.219 or higher support a localised Captive Portal without requiring an EG gateway. This is a fallback option for temporary deployments but does not offer the robust QoS and isolation capabilities of a controller-based architecture.

Network Isolation: NAT versus VLAN

The key architectural decision is how to isolate guest traffic from the corporate network. Ruijie offers two forwarding modes for guest SSIDs:

NAT Mode: The gateway assigns IP addresses from a dedicated pool (default 192.168.23.0/24) and performs Network Address Translation before routing traffic to the Internet. While simple to deploy, this method offers limited visibility and control over guest traffic at Layer 3.
VLAN Mode: The recommended enterprise standard. The guest SSID is mapped to a dedicated VLAN (e.g. VLAN 100). The Reyee EG gateway or RG-WS controller uses Access Control Lists (ACLs) to enforce strict isolation. An extended ACL must be configured to block IP traffic from the guest subnet to the corporate network while permitting outbound Internet access. This approach aligns with the principles of Enterprise WiFi Security: A Complete Guide for 2026 .

Walled Garden Configuration

Before a guest completes authentication via the Captive Portal, their device is in a restricted state. A walled garden (whitelist) must be configured to permit access to essential services. If you are leveraging an external platform, you must include the platform's domain, IP addresses, and authentication endpoints of any social login providers (such as Facebook or Google). Crucially, you must include captive.apple.com to ensure iOS devices trigger the Captive Portal's mini-browser correctly.

Implementation Guide

Deploying an external Captive Portal on Ruijie hardware requires precise configuration of the SSID, authentication policies, and network isolation layers. Follow these steps to integrate Ruijie with an external platform like Purple.

Step 1: Configure the Guest SSID and VLAN

Log in to the Ruijie Cloud or the local eWeb user interface of your controller.
Navigate to the Wireless settings and create a new SSID with a name suitable for your location.
Set the security mode to "Open". The Captive Portal serves as the authentication mechanism.
Assign the SSID to your designated Guest VLAN. Ensure that the corresponding VLAN interface on your EG gateway is configured with a DHCP range.

Step 2: Configure the External Captive Portal Policy

Navigate to the "Auth & Account" section.
Select Captive Portal under the "Authentication" menu.
Create a new policy and set the "Policy Mode" to "External".
Select the Guest SSID created in Step 1.
Enter the Portal Server URL provided by your external platform (e.g. the portal endpoint from Purple).
Configure the RADIUS server group with the IP addresses, ports (typically 1812 for authentication and 1813 for accounting), and the shared secrets provided by your platform.

Step 3: Implement Walled Garden

Locate the configuration for the "Allowlist" within the "Auth & Account" section.
Add the required domains and IP addresses for your external platform.
Add the domains for any social identity providers you intend to use.
Ensure that standard domains for Captive Portal detection are allowed.

Step 4: Enforce ACL Isolation

Connect to the command-line interface (CLI) of your Ruijie gateway or controller to configure the isolation ACL. This step ensures that guests cannot access internal resources.

Ruijie(config)# access-list extended 107
Ruijie(config-ext-nacl)# deny ip 192.168.100.0 0.0.0.255 192.168.10.0 0.0.0.255
Ruijie(config-ext-nacl)# permit ip any any
Ruijie(config-ext-nacl)# exit
Ruijie(config)# interface BVI 100
Ruijie(config-if-BVI 100)# access-group 107 in

Best Practices

To ensure a reliable and secure guest Wi-Fi experience, adhere to these industry-standard best practices:

Leverage external authentication for scalability: If you manage multiple locations or require detailed Guest WiFi analytics, bypass the native portal and utilise an external RADIUS integration. Platforms like Purple provide hardware-agnostic management, allowing you to standardise the guest experience across Ruijie, Cisco Meraki, HPE Aruba, and Ruckus hardware.
Implement tiered bandwidth: Utilise the QoS capabilities of the Ruijie EG gateway to enforce per-user bandwidth limits. Offer a free basic tier (e.g. 5 Mbps) and integrate a payment gateway through your external portal to offer a premium, high-speed paid tier. This creates a direct revenue stream from your infrastructure.
Synchronise configurations: If you are using the Ruijie JaCS platform, you must explicitly click the "Synchronise" button after modifying a Captive Portal policy. Otherwise, the EG gateway will not receive the updated configuration, leading to inconsistent portal behaviour.
Adhere to privacy regulations: Ensure your Captive Portal includes explicit opt-ins with conscious consent for marketing communications. When using Purple, the platform automatically handles GDPR and CCPA compliance, providing a secure data privacy layer. For detailed requirements, refer to The Network Administrator’s Guide to GDPR and Guest Data Privacy Compliance .

Troubleshooting & Risk Mitigation

Even with careful configuration, issues can arise during Captive Portal deployments. Here are the most common failure scenarios and how to resolve them:

iOS devices fail to display the portal: This is almost always a Walled Garden issue. Apple devices check captive.apple.com to determine if they are behind a portal. If this domain is blocked, the device assumes it has full internet access and will not launch the Captive Network Assistant. Verify your allowlist configuration.
Guests cannot authenticate via RADIUS: Double-check the RADIUS shared secret and port configurations on the Ruijie gateway. Ensure that the gateway's public IP address is correctly registered on your external platform. Utilise Ruijie's diagnostic tools to verify RADIUS reachability.
Bandwidth limits are ignored: If you are utilising an external platform to enforce bandwidth tiers, you must disable the "Client Escape" feature on the Ruijie gateway. If Client Escape is active, the gateway may bypass the QoS instructions from the external platform.
Guest traffic enters the corporate network: Verify your ACL configuration. Ensure that the extended access list is applied inbound on the correct VLAN or BVI interface. Test isolation by connecting a device to the guest SSID and attempting to ping a known internal IP address.

ROI & Business Value

Deploying a robust Captive Portal on Ruijie hardware transforms guest WiFi from a cost centre into a measurable business asset. By integrating an external WiFi Analytics platform like Purple, venues can achieve significant returns.

First-party data capture: The Captive Portal acts as the primary data capture point. By offering free WiFi in exchange for an email address or social login, venues build a rich database of customer profiles. This data feeds targeted marketing campaigns and increases customer lifetime value.
Operational efficiency: Centralised cloud management via Ruijie Cloud and Purple reduces the time spent by IT teams troubleshooting local network issues. Because the overlay is hardware-agnostic, you can upgrade or swap out access points without needing to rebuild your entire analytics stack.
Direct revenue generation: Implementing tiered bandwidth models allows venues to monetise the network directly. For example, AGS Airports implemented a tiered WiFi strategy, achieving an 842% return on investment.
Enhanced visitor experience: A seamless, branded login process improves customer satisfaction. In sectors like hospitality and retail , reliable connectivity is a baseline expectation; a secure deployment reinforces brand trust.

Key Definitions

Captive Portal

A web page that a user of a public access network is obliged to view and interact with before access is granted.

The primary mechanism for authenticating guests and capturing first-party data on a Ruijie wireless network.

RADIUS

Remote Authentication Dial-In User Service. A networking protocol that provides centralised Authentication, Authorisation, and Accounting management.

Used to securely connect Ruijie gateways to external platforms like Purple for guest authentication.

Walled Garden

An allowlist of domains and IP addresses that a guest device can access before completing the captive portal authentication.

Essential for allowing social login providers and captive portal detection mechanisms (like Apple's CNA) to function.

VLAN Isolation

The practice of assigning guest traffic to a separate Virtual Local Area Network and using Access Control Lists to prevent communication with internal corporate networks.

The standard security posture for enterprise guest WiFi deployments on Ruijie hardware.

WISPr

Wireless Internet Service Provider roaming. A protocol that allows users to roam between different wireless providers, often used to handle the redirect to external captive portals.

The underlying mechanism Ruijie uses when the captive portal policy is set to External mode.

Ruijie JaCS

Ruijie's cloud management platform specifically tailored for hospitality and hotel scenarios, offering native captive portal building tools.

Used for managing single-site deployments that do not require external data capture platforms.

Reyee EG Gateway

Ruijie's line of enterprise security routers that handle routing, firewall policies, and captive portal redirection for the wireless network.

The central hardware component where ACLs and RADIUS configurations are applied in a Ruijie deployment.

Client Escape

A feature on Ruijie gateways that, if enabled, can allow clients to bypass certain QoS or portal restrictions.

Must be disabled when using an external platform to enforce tiered bandwidth limits.

Worked Examples

A 200-room hotel deploying Ruijie RG-AP access points and an EG gateway needs to provide free guest WiFi while capturing email addresses for their marketing database. They also require strict isolation from their property management system (PMS) network.

The IT team configures a new Open SSID assigned to VLAN 100. On the EG gateway, they configure an extended ACL to deny traffic from VLAN 100 to the PMS VLAN, applying it inbound on the guest interface. They set the captive portal policy to External mode, pointing the Portal Server URL to Purple's platform. They configure the RADIUS server group with Purple's credentials and add Purple's domains to the allowlist. The Purple platform handles the branded splash page and email capture workflow.

Examiner's Commentary: This approach correctly uses VLAN isolation instead of basic NAT, ensuring security for the PMS. By leveraging an external portal via RADIUS, the hotel gains GDPR-compliant data capture capabilities that the native Ruijie portal cannot provide at an enterprise level.

A retail chain with 50 locations is rolling out Ruijie hardware. Customers report that when they connect to the guest WiFi on their iPhones, the login screen does not appear automatically, forcing them to open a browser manually.

The network administrator logs into Ruijie Cloud, navigates to Auth & Account, and opens the Allowlist configuration. They add 'captive.apple.com' to the walled garden list and synchronise the configuration to all EG gateways across the estate.

Examiner's Commentary: This resolves the classic Captive Network Assistant (CNA) failure. iOS devices require access to specific Apple endpoints to trigger the automatic portal pop-up. Adding this to the walled garden is a mandatory step for any captive portal deployment.

Practice Questions

Q1. You are deploying Ruijie WiFi across a stadium. You need to capture fan data for marketing and enforce a 5 Mbps bandwidth limit per user. Should you use the native Ruijie portal or an external platform, and how do you enforce the bandwidth?

Hint: Consider the scale of the deployment and the data capture requirements.

View model answer

You must use an external platform like Purple for the data capture and marketing integration. To enforce the bandwidth, configure the QoS settings on the Ruijie EG gateway for the guest SSID, and ensure the Client Escape feature is disabled so the external platform's policies are respected.

Q2. A client complains that their guest network is insecure because the SSID is set to 'Open'. They ask you to implement a pre-shared key (WPA2-Personal) alongside the captive portal. How do you advise them?

Hint: Consider the user experience and the purpose of the captive portal.

View model answer

Advise the client that for public guest networks, adding a pre-shared key introduces unnecessary friction without significantly improving security, as the key must be shared publicly anyway. The captive portal itself serves as the authentication and authorisation layer. For true security, WPA3-Enterprise with 802.1X should be used, but this is rarely suitable for public guest access.

Q3. After configuring a new external captive portal policy on Ruijie Cloud and pointing it to Purple, guests are still seeing the default Ruijie login page. What is the most likely cause?

Hint: Think about the configuration deployment process in the Ruijie interface.

View model answer

The administrator likely saved the configuration in Ruijie Cloud but failed to click the Synchronise button. The configuration has not been pushed down to the local EG gateway, so it is still serving the default local portal.

Continue reading in this series

Captive portal for Ruijie: set it up with Purple guest WiFi

How Purple's cloud guest WiFi sits on top of Ruijie RG Series access points using web authentication and RADIUS, configured from the command line, and where to find the exact setup steps.

Captive portal for Ruijie: set it up with Purple guest WiFi

How Purple's cloud guest WiFi sits on top of Ruijie RG Series access points using web authentication and RADIUS, configured from the command line, and where to find the exact setup steps.

Designing B2B Captive Portals: Collecting Registered Name and Company Data

This guide provides IT managers and venue operators with a vendor-neutral technical framework for designing B2B captive portals. It details how to structure registration fields to capture registered name and company data, ensuring high completion rates while maintaining GDPR compliance and building account-level intelligence.