IndexLayout.skipToMainContent
English (UK)
Pricing

How to Set Up a WiFi Hotspot for Your Business

This authoritative guide provides IT leaders, network architects, and venue operations directors with a practical, vendor-neutral blueprint for deploying secure, compliant, and business-enhancing guest WiFi hotspots. It covers critical architecture decisions—from VLAN segmentation and captive portal configuration to GDPR compliance and traffic shaping—and demonstrates how to transform network infrastructure from a cost centre into a revenue-driving analytics platform using Purple's Guest WiFi and analytics capabilities.

📖 9 min read📝 2,133 words🔧 2 worked examples❓ 3 practice questions📚 9 key definitions

Listen to this guide

View podcast transcript
Welcome back to the Enterprise Networking Briefing. I'm your host, and today we're tackling a deployment that almost every IT manager and venue operator faces at some point: setting up a business WiFi hotspot with a captive portal. If you're managing infrastructure for a retail chain, a hotel group, or a large public venue, you know that guest WiFi isn't just a nice to have anymore. It's a critical operational asset. But the gap between a consumer-grade router plugged into a wall and a secure, compliant, enterprise-grade hotspot is massive. Today, we're bridging that gap. We'll cover the architecture, the security mandates, and how to turn that network into a tangible business asset. Let's dive into the technical deep-dive. When we talk about deploying a managed WiFi hotspot, the first principle is isolation. Your guest network must be fundamentally segregated from your corporate environment. We achieve this through VLANs, that is, Virtual Local Area Networks. Your corporate traffic, point-of-sale systems, and back-office servers should sit on VLAN 10. Your guest traffic sits on VLAN 20. This segmentation isn't optional. If you process payments, it's a hard requirement for PCI DSS compliance. A breach on the guest network must never have a route to your payment card data environment. So, how does a user actually get online? That's where the captive portal comes in. When a guest device associates with your access point, the AP assigns it an IP address via DHCP. But at this stage, the firewall blocks all outbound internet traffic. When the user opens a browser, the network intercepts their HTTP request, usually via DNS redirection, and routes them to the captive portal server. This is the splash page. It's the gateway. Here, the user authenticates. They might use an email address, a social login, or a seamless identity provider like OpenRoaming. Once they authenticate and accept the terms of service, the captive portal server signals the firewall or the wireless LAN controller to authorise that specific MAC address or IP. The firewall rules update dynamically, and the user is granted internet access. Now, let's talk about the hardware layer. For enterprise deployments, you need managed access points, typically 802.11ax or WiFi 6. These should be PoE-enabled, meaning Power over Ethernet, allowing you to run a single cable for both data and power from your managed switch. You'll need a UTM, that is, a Unified Threat Management firewall, to handle the routing, security, and traffic shaping. And traffic shaping is crucial. You must implement bandwidth throttling. If you have a 1 Gigabit uplink and 500 guests, you cannot allow one user to consume 800 Megabits streaming 4K video. Implement per-user bandwidth limits, say, 5 Megabits per second down and 2 Megabits per second up, to ensure a consistent experience for everyone. Let's move on to implementation recommendations and common pitfalls. The biggest mistake we see is poor access point placement. Do not hide access points above metal ceiling tiles or behind thick concrete pillars. Wireless design requires a proper site survey. You need to account for attenuation, which is the loss of signal strength through physical barriers. Another major pitfall is ignoring compliance. If you're operating in the UK or the EU, GDPR is non-negotiable. Your captive portal must explicitly capture consent if you are collecting data for marketing purposes. You cannot pre-tick the consent box. Furthermore, you need to retain session logs, including MAC addresses, timestamps, and IP assignments, to comply with local law enforcement requests if illicit activity occurs on your network. This brings us to the business value. A properly deployed hotspot isn't just an IT cost centre. Platforms like Purple's Guest WiFi turn this infrastructure into an analytics engine. When users log in, you capture first-party data. You understand dwell times, return rates, and footfall patterns. This data can be piped directly into your CRM to trigger automated marketing campaigns. For instance, if a customer hasn't visited your retail store in 30 days, the system can automatically email them a discount code. Let's jump into a rapid-fire Q&A based on questions we frequently get from IT directors. Question one: Can we just use a pre-shared key, like a standard password, instead of a captive portal? Answer: You can, but you shouldn't. A pre-shared key provides zero visibility into who is on your network, it offers no legal protection via an Acceptable Use Policy, and it completely eliminates your ability to collect first-party data. Use a captive portal. Question two: What about MAC randomization on modern smartphones? Answer: iOS and Android now randomize MAC addresses to protect user privacy. This means you can't rely solely on MAC addresses for long-term user tracking. Your captive portal strategy must pivot to identity-based authentication, asking the user to log in via email or social accounts, so you can track the user profile rather than the hardware address. To summarize: First, segment your network using VLANs. Second, use a compliant captive portal to manage access and capture data. Third, implement traffic shaping to protect bandwidth. And fourth, ensure your access point placement is driven by a professional site survey. Setting up a business WiFi hotspot is a strategic infrastructure project. Done right, it secures your corporate assets, delights your guests, and provides invaluable data to your marketing teams. Thanks for joining this briefing. Until next time, keep your networks secure and your latency low.

header_image.png

Executive Summary

For enterprise venues—whether retail chains, hotel groups, conference centres, or large public-sector facilities—guest WiFi has evolved from a discretionary amenity into a critical digital touchpoint. Guests and visitors now arrive expecting reliable, fast connectivity as a baseline. However, the operational and legal gap between a consumer-grade router and a properly deployed enterprise hotspot is substantial. A poorly implemented network exposes corporate assets to lateral movement attacks, creates liability under GDPR and the Computer Misuse Act, and squanders the opportunity to capture valuable first-party data.

This guide provides a practical, vendor-neutral blueprint for IT managers and network architects tasked with deploying or upgrading a public WiFi service. We detail the technical architecture required to deliver a secure, segmented hotspot, with specific focus on VLAN design, captive portal authentication flows, bandwidth management, and compliance mandates including GDPR, PCI DSS, and IEEE 802.1X. We also explore how integrating a managed platform like Guest WiFi transforms raw connectivity into actionable WiFi Analytics , enabling venue operators to understand footfall patterns, measure dwell time, and drive measurable marketing ROI.

Technical Deep-Dive: Architecture and Segmentation

The foundational principle of any enterprise hotspot deployment is isolation. Guest traffic must be cryptographically and logically separated from corporate data at every layer of the network stack. Failing to enforce this separation is the single most common and most consequential mistake in public WiFi deployments.

Network Segmentation via VLANs

Deploying a flat network where guests and point-of-sale (POS) systems share the same subnet is a catastrophic security failure. Enterprise deployments utilise Virtual Local Area Networks (VLANs) to segment traffic at the managed switch level, enforcing logical boundaries regardless of physical topology.

A standard multi-tenant deployment will typically define at minimum two VLANs:

VLAN Purpose Typical ID Routing Policy
Corporate Staff devices, POS terminals, back-office servers VLAN 10 Full internal access
Guest Public internet access only VLAN 20 Internet-only; no internal routes
IoT/Building CCTV, HVAC, access control VLAN 30 Isolated; no internet

Traffic on the Guest VLAN is routed directly to the internet via a Unified Threat Management (UTM) firewall, with strict Access Control Lists (ACLs) configured to drop any packets destined for internal subnets. This segmentation is a mandatory control under PCI DSS Requirement 1.3, which mandates that cardholder data environments are isolated from untrusted networks. For Retail and Hospitality operators running payment terminals on the same physical infrastructure, this is non-negotiable.

The Captive Portal Authentication Flow

When a guest device associates with an access point (AP), it receives an IP address via DHCP. At this stage, the firewall blocks all outbound internet traffic. The full authentication sequence proceeds as follows:

  1. Association: The device connects to the open SSID (or a secure OpenRoaming SSID using 802.1X/EAP).
  2. DHCP Assignment: The guest VLAN's DHCP server assigns an IP address, default gateway, and DNS server.
  3. Interception: When the device attempts an HTTP request (or the OS triggers a captive portal probe via a well-known URL), the network intercepts the request via DNS redirection and routes the user to the captive portal server.
  4. Authentication: The user is presented with a branded splash page. They authenticate via email, social login (OAuth), SMS OTP, or a seamless identity provider like OpenRoaming.
  5. Consent Capture: The user is presented with the Acceptable Use Policy (AUP) and, if data is being collected for marketing, an explicit opt-in consent checkbox.
  6. Authorisation Signal: The portal server communicates with the wireless LAN controller or firewall via RADIUS or a REST API, authorising the device's MAC address or IP for internet access.
  7. Access Granted: The firewall rules are updated dynamically, and the user is redirected to their intended destination.

architecture_overview.png

For environments requiring enterprise-grade certificate-based authentication for staff devices alongside the guest portal, refer to our guide on How to Set Up Enterprise WiFi on iOS and macOS with 802.1X (also available in Portuguese: Como Configurar WiFi Corporativo em iOS e macOS com 802.1X ).

Wireless Standards and Frequency Planning

Enterprise deployments should standardise on 802.11ax (WiFi 6) or 802.11be (WiFi 7) access points. WiFi 6 introduces OFDMA (Orthogonal Frequency Division Multiple Access), which dramatically improves performance in high-density environments by allowing a single AP to serve multiple clients simultaneously on sub-channels, rather than sequentially. This is particularly critical in Healthcare facilities, conference centres, and stadium deployments where hundreds of devices may associate with a single AP during peak periods.

Frequency band allocation should follow these principles. The 2.4 GHz band offers greater range and better penetration through walls, making it suitable for legacy devices and large open areas. However, it has only three non-overlapping channels (1, 6, 11), making it highly susceptible to co-channel interference in dense deployments. The 5 GHz band offers 24+ non-overlapping channels and significantly higher throughput, but with reduced range. Modern enterprise wireless controllers support Band Steering, which actively encourages capable dual-band devices to connect to 5 GHz, freeing up the 2.4 GHz spectrum for legacy clients.

Implementation Guide: Hardware, Configuration, and Deployment

Before selecting hardware, calculate your required uplink bandwidth. A conservative estimate for a general-purpose guest network is 1–2 Mbps per concurrent user. For a venue expecting 300 concurrent guests, a minimum 500 Mbps symmetric fibre connection is recommended, with a 1 Gbps connection providing headroom for growth. For Transport hubs or large event venues, multiple bonded uplinks or SD-WAN failover should be considered.

Step 2: Access Point Selection and Placement

Utilise 802.11ax managed access points from enterprise vendors. These APs must be PoE+ (Power over Ethernet Plus, IEEE 802.3at) capable, allowing a single Cat6 cable to carry both data and power from the managed switch to the AP. This eliminates the need for local power outlets at each AP location, dramatically reducing installation costs.

AP placement must be dictated by a professional RF site survey, not guesswork. The survey should account for:

  • Attenuation: Signal loss through concrete walls, metal shelving, and glass partitions.
  • Coverage Overlap: APs should overlap by approximately 15–20% to ensure seamless roaming without dead zones.
  • Capacity Planning: High-density areas (conference rooms, food courts, lobbies) require more APs with lower transmit power to serve many clients at short range, rather than fewer APs with high power.

Step 3: Managed Switch and VLAN Configuration

Deploy a managed Layer 2/3 switch with sufficient PoE+ budget to power all APs. Configure 802.1Q VLAN tagging on all uplink and AP trunk ports. Access ports connecting to POS terminals or staff workstations should be assigned to the corporate VLAN as untagged members. AP ports should be configured as trunk ports carrying all required VLANs, with the wireless controller mapping each SSID to its corresponding VLAN.

Step 4: Firewall and Traffic Shaping

The UTM firewall is the enforcement point for all security and bandwidth policies. Key configurations include:

  • VLAN Routing Rules: Permit Guest VLAN to internet; deny Guest VLAN to all internal subnets.
  • Per-User Bandwidth Limits: Implement traffic shaping policies to cap individual throughput. A standard starting point is 5 Mbps down / 2 Mbps up per user. This prevents a single user streaming 4K video from degrading the experience for all other guests.
  • Application Control: Block peer-to-peer file sharing protocols (BitTorrent, eDonkey) and other high-bandwidth or illicit applications at the firewall level.
  • DNS Filtering: Implement DNS-based content filtering to block access to malicious domains, phishing sites, and inappropriate content categories. For a detailed guide to this layer, see Protect Your Network with Strong DNS and Security .

Step 5: Captive Portal Configuration

The captive portal is the most visible component of the deployment and the primary data-capture mechanism. When configuring the portal, ensure:

  • The splash page is served over HTTPS with a valid, publicly trusted SSL certificate to prevent browser security warnings.

  • Authentication options include at minimum email/password and social login (Google, Facebook, Apple) to maximise conversion rates.

  • The AUP is clearly displayed and requires explicit acceptance before access is granted.

  • GDPR consent for marketing communications is captured via a separate, un-ticked opt-in checkbox.

  • Session timeout and re-authentication intervals are configured to balance user convenience with security.

Best Practices and Compliance

compliance_checklist.png

GDPR and Data Privacy

If you collect user data for marketing purposes, explicit, informed consent is mandatory under UK GDPR and EU GDPR. The legal requirements are unambiguous: pre-ticked consent boxes are prohibited; consent must be freely given, specific, informed, and unambiguous; and users must be able to withdraw consent as easily as they gave it. Your captive portal must clearly state what data is collected, the legal basis for processing, how it will be used, and how long it will be retained.

In the UK, the Regulation of Investigatory Powers Act (RIPA) and associated legislation may require venue operators to retain connection logs—including MAC addresses, timestamps, and IP assignments—to assist law enforcement in the event of illegal activity on the network. Consult your legal counsel to determine the specific retention obligations applicable to your organisation and jurisdiction.

WPA3 and Encryption Standards

For any SSID that uses a pre-shared key (e.g., a staff network), mandate WPA3-Personal (SAE) rather than WPA2. WPA3 eliminates the offline dictionary attack vulnerability inherent in WPA2's 4-way handshake. For enterprise staff networks using 802.1X certificate-based authentication, WPA3-Enterprise with 192-bit mode provides the highest level of assurance. For more on securing the physical and logical layers of your wireless infrastructure, see Access Point Security: Your 2026 Enterprise Guide .

Addressing MAC Randomization

Modern iOS (since iOS 14) and Android (since Android 10) devices utilise MAC randomisation by default, generating a unique random MAC address for each WiFi network. This means that MAC addresses can no longer be reliably used to identify returning visitors or build long-term user profiles. The correct architectural response is to mandate identity-based authentication at the captive portal—requiring users to log in via email or a social account—so that the user profile, rather than the hardware identifier, becomes the persistent tracking entity.

Troubleshooting & Risk Mitigation

Even well-designed networks encounter operational issues. The following table summarises the most common failure modes and their recommended mitigations.

Failure Mode Root Cause Mitigation
DHCP Exhaustion Subnet too small or lease time too long for footfall volume Use /22 or larger subnet; reduce lease time to 30–60 minutes
Co-Channel Interference Multiple APs on same channel in overlapping coverage areas Enable dynamic channel assignment on wireless controller
Captive Portal SSL Errors Invalid or self-signed certificate on portal server Deploy a valid public CA certificate; use Let's Encrypt
Slow Roaming APs not sharing client association data Enable 802.11r (Fast BSS Transition) on wireless controller
Bandwidth Saturation No per-user traffic shaping configured Implement per-user QoS policies on firewall
Guest-to-Corporate Lateral Movement Flat network or misconfigured ACLs Audit VLAN ACLs; run penetration test on guest VLAN

ROI & Business Impact

A properly deployed hotspot transcends its function as IT infrastructure—it becomes a first-party data engine and a direct marketing channel. The business case for investing in a managed guest WiFi platform is compelling across every vertical.

In Hospitality , guest WiFi data enables hotels to understand which amenities guests use before and after connecting, personalise in-stay communications, and drive repeat bookings through automated post-stay campaigns. A 300-room hotel capturing 200 email opt-ins per day builds a marketing database of 70,000 opted-in contacts per year—a significant CRM asset.

In Retail , WiFi analytics provide footfall heatmaps, dwell time by zone, and repeat visit rates—data that was previously only available through expensive manual surveys. Retailers can use this data to optimise store layouts, measure the impact of promotional displays, and trigger loyalty campaigns when a known customer enters the store.

For public-sector and Transport operators, the value proposition is operational efficiency: understanding peak congestion periods, optimising staffing, and providing accessible digital services to citizens and passengers.

Platforms like Purple's Guest WiFi and WiFi Analytics provide the managed infrastructure layer that connects the raw network to these business outcomes. As Purple's strategic expansion demonstrates—including recent moves into new verticals as highlighted in the announcement of VP Education Tim Peers joining the team —the value of intelligent connected spaces is expanding rapidly across all sectors of the economy.

The transition from a basic internet connection to an intelligent, data-driven network is the defining characteristic of a modern enterprise WiFi deployment. The infrastructure cost is largely fixed; the incremental investment in a managed platform layer delivers compounding returns as the marketing database grows and automation workflows mature.

Key Definitions

Captive Portal

A web page that a user of a public access network is obliged to view and interact with before internet access is granted. It intercepts HTTP traffic via DNS redirection and presents a splash page for authentication and consent capture.

The primary mechanism for enforcing Acceptable Use Policies, authenticating users, and capturing first-party marketing data on guest WiFi networks.

VLAN (Virtual Local Area Network)

A logical subnetwork that groups a collection of devices from different physical LANs, enforced at the managed switch level via 802.1Q tagging.

Essential for isolating guest WiFi traffic from sensitive corporate networks. A mandatory control for PCI DSS compliance in any venue that processes payment card data.

Traffic Shaping (QoS)

The control of network traffic to optimize or guarantee performance by limiting the bandwidth available to individual users or application types.

Used to prevent a small number of heavy users from consuming the majority of the available uplink bandwidth, ensuring a consistent baseline experience for all concurrent guests.

MAC Randomization

A privacy feature in modern operating systems (iOS 14+, Android 10+) that generates a unique random MAC address when connecting to different WiFi networks, preventing persistent hardware-based tracking.

Forces venue operators to use identity-based captive portal logins rather than hardware address tracking to identify and re-engage returning visitors.

DHCP Exhaustion

A network failure condition where the DHCP server has assigned all available IP addresses in its configured pool, preventing new devices from obtaining an IP address and connecting to the network.

A common and easily preventable failure in high-footfall venues with undersized subnets or excessively long DHCP lease times.

Band Steering

A wireless controller feature that detects dual-band capable client devices and actively encourages or forces them to connect to the 5 GHz band rather than the more congested 2.4 GHz band.

Improves overall network performance in high-density deployments by distributing clients across the available spectrum and reducing co-channel interference on the 2.4 GHz band.

OpenRoaming

A Wireless Broadband Alliance (WBA) federation standard that enables automatic, secure WiFi connections across participating networks using 802.1X/EAP authentication, without requiring users to interact with a captive portal.

Provides a seamless, cellular-like connectivity experience for users of participating identity providers. Purple operates as an identity provider within the OpenRoaming federation under its Connect licence.

PCI DSS (Payment Card Industry Data Security Standard)

A set of security standards mandated by the major card schemes (Visa, Mastercard, Amex) requiring any organisation that accepts, processes, stores, or transmits payment card data to maintain a secure, segmented network environment.

Directly relevant to any retail or hospitality WiFi deployment where payment terminals share physical network infrastructure with guest access points. Requirement 1.3 mandates strict isolation of the cardholder data environment from untrusted networks.

UTM Firewall (Unified Threat Management)

A network security appliance that combines multiple security functions—including stateful packet inspection, intrusion prevention, application control, DNS filtering, and VPN—into a single managed platform.

The central enforcement point for VLAN routing rules, per-user bandwidth policies, and content filtering in an enterprise guest WiFi deployment.

Worked Examples

A 200-room hotel is upgrading its guest WiFi. During peak evening hours, guests complain about slow speeds and dropped connections, despite the hotel having a 1 Gbps symmetric fiber uplink. Investigation reveals the current setup uses a single flat /24 subnet for both staff and guests, with no traffic shaping configured. The hotel also wants to start capturing guest email addresses for a post-stay marketing programme.

Phase 1 — Network Redesign:

  1. Implement VLAN segmentation. Move all staff devices, POS terminals, and the property management system to VLAN 10 (/24 subnet). Move guests to VLAN 20 with a /22 subnet (1,022 usable IPs) to accommodate peak occupancy with multiple devices per guest.
  2. Configure the UTM firewall with strict ACLs: Guest VLAN 20 has internet access only; all routes to VLAN 10 are explicitly denied.

Phase 2 — Performance Optimisation: 3. Configure per-user bandwidth limits of 10 Mbps down / 5 Mbps up on the firewall. This ensures the 1 Gbps pipe is distributed fairly among 400+ concurrent devices. 4. Enable Band Steering on the wireless controller to push capable devices to the less congested 5 GHz band. 5. Reduce DHCP lease time from the default 24 hours to 2 hours to prevent IP exhaustion during peak check-in periods.

Phase 3 — Captive Portal and Data Capture: 6. Deploy a branded captive portal (e.g., via Purple Guest WiFi) requiring email authentication. 7. Configure the splash page with an explicit, un-ticked GDPR opt-in checkbox for the post-stay marketing programme. 8. Integrate the portal's API with the hotel's CRM to sync authenticated guest profiles and trigger automated post-stay email sequences.

Examiner's Commentary: The flat /24 subnet was causing two compounding issues: a security vulnerability (guests could potentially enumerate and attack staff devices on the same subnet) and DHCP exhaustion (only 254 IPs available for potentially 400+ guest devices across a 200-room hotel). The solution correctly addresses the logical architecture, bandwidth management, and the marketing data capture objective simultaneously. The GDPR opt-in configuration is critical—pre-ticking the box would render the consent legally invalid.

A 50-store retail chain wants to use their free guest WiFi to build their marketing database. They currently use a WPA2 pre-shared key (password printed on receipts) across all stores and have zero visibility into who is connecting or how long they stay. The marketing team wants to send weekly promotional emails to WiFi users, and the IT team is concerned about PCI DSS compliance given that payment terminals are on the same physical switches.

Step 1 — Remove the Pre-Shared Key: Transition the guest SSID to an open network (no password) that immediately redirects to a captive portal. This eliminates the shared secret vulnerability and enables per-user authentication.

Step 2 — VLAN Segmentation for PCI DSS: Create a dedicated Guest VLAN (e.g., VLAN 20) on all managed switches. Assign POS terminals to the existing Corporate VLAN (VLAN 10). Configure ACLs on the firewall to enforce hard isolation between the two VLANs. Document this segmentation as part of the PCI DSS network diagram.

Step 3 — Captive Portal with GDPR-Compliant Consent: Deploy a managed captive portal platform. Configure the splash page to require authentication via Email, Google, or Facebook. Include a clearly worded, un-ticked opt-in checkbox: 'I agree to receive promotional emails from [Brand Name]. You can unsubscribe at any time.'

Step 4 — CRM Integration and Automation: Connect the portal's API to the retailer's CRM (e.g., Salesforce, Klaviyo). Sync authenticated user profiles, visit timestamps, and store location data. Configure an automated welcome email triggered on first connection, and a re-engagement campaign triggered when a known user has not connected for 30 days.

Examiner's Commentary: This scenario illustrates the dual value of a captive portal: it solves a compliance problem (PCI DSS segmentation) and creates a business asset (marketing database) simultaneously. The critical insight is that identity-based authentication via the portal overcomes the MAC randomization problem—even if a guest's device presents a different MAC address on their next visit, their email login ties the session to the same user profile, enabling accurate repeat visit tracking.

Practice Questions

Q1. Your marketing team wants to collect guest email addresses via the new WiFi hotspot. They suggest setting the DHCP lease time to 24 hours so guests do not have to log in repeatedly during the day. Your venue sees 3,000 unique visitors per day. Your guest subnet is a /23 (510 usable IPs). What is the architectural flaw in this request, and how do you resolve it while still meeting the marketing team's requirement?

Hint: Consider the relationship between the number of daily visitors, the subnet size, and the lease duration. Then think about how to separate the network-layer concern from the application-layer concern.

View model answer

The architectural flaw is that a 24-hour lease time on a /23 subnet with 3,000 daily visitors will cause rapid DHCP exhaustion. Once 510 devices have connected, no new devices will receive an IP address for up to 24 hours. The solution is twofold: First, expand the subnet to at least a /21 (2,046 IPs) to accommodate peak concurrent devices. Second, reduce the DHCP lease time to 30–60 minutes to recycle IP addresses as guests leave the venue. To satisfy the marketing team's requirement that guests do not have to re-authenticate repeatedly, configure the captive portal controller to remember authenticated MAC addresses (or user identity tokens) for 24 hours. This allows a returning device to obtain a new IP via DHCP but bypass the splash page, delivering the seamless experience the marketing team wants without breaking the network.

Q2. A retail client wants to implement a captive portal but is concerned about the cost of replacing their existing unmanaged switches. They ask if they can run the guest WiFi on the same physical unmanaged switches as their Point of Sale terminals, with the guest network simply using a different SSID.

Hint: VLAN enforcement requires managed switch hardware. Consider what happens to traffic on an unmanaged switch.

View model answer

This configuration is not acceptable from a security or compliance standpoint. Unmanaged switches do not support 802.1Q VLAN tagging, meaning all traffic on the switch—regardless of SSID—is on the same broadcast domain. A guest device on the 'guest' SSID would be able to reach POS terminals on the same switch, violating PCI DSS Requirement 1.3. The client must replace unmanaged switches with managed Layer 2 switches that support 802.1Q VLAN tagging. The capital cost of managed switches is modest compared to the liability exposure of a PCI DSS breach or the fines associated with a data compromise.

Q3. You are deploying access points in a high-density conference centre that hosts events with up to 1,500 concurrent WiFi users. You notice significant latency and packet loss on the 2.4 GHz spectrum during events, even though the 5 GHz spectrum appears underutilised. How should you configure the wireless controller to address this, and what additional hardware consideration should you make?

Hint: Think about how to move capable devices off the congested frequency band, and consider the relationship between AP transmit power and client density.

View model answer

Enable Band Steering on the wireless controller. This feature detects if a client device is capable of connecting to the 5 GHz band and actively encourages or forces the device to associate there, freeing up the 2.4 GHz band for legacy devices. Additionally, reduce the transmit power on all APs. Counter-intuitively, in high-density deployments, lower transmit power improves performance by reducing co-channel interference between adjacent APs and encouraging clients to associate with the nearest AP rather than a distant one at high signal strength. Consider deploying additional APs at lower power rather than fewer APs at high power. Also enable 802.11r (Fast BSS Transition) to enable seamless roaming as users move through the venue.