Skip to main content

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 examples3 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

执行摘要

对于企业场所——无论是零售连锁店、酒店集团、会议中心还是大型公共机构——宾客WiFi已经从一种可选便利设施演变为关键的数字接触点。宾客和访客现在期望以可靠、快速的连接为基础。然而,消费级路由器与正确部署的企业热点之间的运营和法律差距是巨大的。实施不当的网络会使企业资产面临横向移动攻击,产生GDPR和《计算机滥用法》下的责任,并浪费获取宝贵第一方数据的机会。

本指南为负责部署或升级公共WiFi服务的IT经理和网络架构师提供了一份务实的技术中立的蓝图。我们详细说明了交付安全、分段式热点所需的技术架构,特别关注VLAN设计、Captive Portal认证流程、带宽管理以及包括GDPR、PCI DSS和IEEE 802.1X在内的合规要求。我们还探讨了如何通过集成像 宾客WiFi 这样的托管平台,将原始连接转变为可操作的 WiFi分析 ,使场馆运营商能够了解客流模式、衡量停留时间并推动可衡量的营销投资回报率。


技术深入探讨:架构与分段

任何企业热点部署的基本原则是隔离。在网络堆栈的每一层,宾客流量必须在加密和逻辑上与公司数据分离。未能强制执行这种分离是公共WiFi部署中最常见且后果最严重的错误。

通过VLAN进行网络分段

部署一个宾客和销售点(POS)系统共享同一子网的扁平网络是一个灾难性的安全故障。企业部署利用虚拟局域网(VLAN)在管理型交换机级别对流量进行分段,无论物理拓扑如何,都强制实施逻辑边界。

标准的多租户部署通常至少定义两个VLAN:

VLAN 目的 典型ID 路由策略
公司 员工设备、POS终端、后台服务器 VLAN 10 完全内部访问
宾客 仅限公共互联网访问 VLAN 20 仅限互联网;无内部路由
IoT/楼宇 闭路电视、暖通空调、门禁控制 VLAN 30 隔离;无互联网

宾客VLAN上的流量通过统一威胁管理(UTM)防火墙直接路由到互联网,并配置严格的访问控制列表(ACL),丢弃任何发往内部子网的数据包。这种分段是PCI DSS要求1.3下的强制性控制,该要求规定持卡人数据环境必须与不受信任的网络隔离。对于在同一物理基础设施上运行支付终端的 零售酒店 运营商来说,这是不可协商的。

Captive Portal认证流程

当宾客设备与接入点(AP)关联时,它会通过DHCP获得一个IP地址。在此阶段,防火墙会阻止所有出站互联网流量。完整的认证序列如下:

  1. 关联: 设备连接到开放的SSID(或使用802.1X/EAP的安全OpenRoaming SSID)。
  2. DHCP分配: 宾客VLAN的DHCP服务器分配IP地址、默认网关和DNS服务器。
  3. 拦截: 当设备尝试HTTP请求(或操作系统通过已知URL触发Captive Portal探测)时,网络通过DNS重定向拦截该请求,并将用户路由到Captive Portal服务器。
  4. 认证: 用户会看到一个带品牌标识的启动页面。他们通过电子邮件、社交登录(OAuth)、短信验证码或像OpenRoaming这样的无缝身份提供者进行认证。
  5. 同意捕获: 向用户展示可接受使用政策(AUP),如果为营销目的收集数据,还需提供一个明确的选择同意复选框。
  6. 授权信号: 门户服务器通过RADIUS或REST API与无线局域网控制器或防火墙通信,授权设备的MAC地址或IP进行互联网访问。
  7. 授予访问: 防火墙规则动态更新,用户被重定向到他们预期的目的地。

architecture_overview.png

对于需要在宾客门户之外为员工设备提供企业级基于证书认证的环境,请参阅我们的指南 如何在iOS和macOS上使用802.1X设置企业WiFi (另提供葡萄牙语版本: Como Configurar WiFi Corporativo em iOS e macOS com 802.1X )。

无线标准与频率规划

企业部署应标准化使用802.11ax(WiFi 6)或802.11be(WiFi 7)接入点。WiFi 6引入了OFDMA(正交频分多址),通过允许单个AP在子信道上同时服务多个客户端而不是顺序服务,大幅提升了高密度环境中的性能。这在 医疗保健 机构、会议中心和体育场馆部署中尤为关键,因为在高峰时段可能有数百台设备连接到一个AP。

频段分配应遵循以下原则。2.4 GHz频段提供更远的范围和对墙壁更好的穿透能力,使其适用于老旧设备和大面积开放区域。然而,它只有三个不重叠的信道(1、6、11),在密集部署中极易受到同信道干扰。5 GHz频段提供超过24个不重叠信道和显著更高的吞吐量,但范围较小。现代企业无线控制器支持频段引导,该功能积极鼓励支持双频的设备连接到5 GHz,从而为老旧客户端释放2.4 GHz频谱。


实施指南:硬件、配置和部署

步骤1:ISP和上行链路规模确定

在选择硬件之前,计算所需的上行带宽。对于通用宾客网络,保守估计每个并发用户需要1-2 Mbps。对于预计有300个并发宾客的场所,建议至少使用500 Mbps对称光纤连接,1 Gbps连接则为增长提供余量。对于 交通 枢纽或大型活动场所,应考虑多个绑定上行链路或SD-WAN故障转移。

步骤2:接入点选择与布置

使用企业供应商的802.11ax管理型接入点。这些AP必须支持PoE+(以太网供电Plus,IEEE 802.3at),允许单根Cat6电缆同时从管理型交换机向AP传输数据和电力。这消除了在每个AP位置安装本地电源插座的需要,大幅降低安装成本。

AP的布置必须由专业的射频现场勘测来决定,而不是靠猜测。该勘测应考虑:

  • 衰减: 穿过混凝土墙、金属货架和玻璃隔断造成的信号损失。
  • 覆盖重叠: AP应重叠约15-20%,以确保无缝漫游且无死角。
  • 容量规划: 高密度区域(会议室、美食广场、大厅)需要更多发射功率较低的AP,以便在短距离内为许多客户端服务,而不是使用少量高功率AP。

步骤3:管理型交换机和VLAN配置

部署一台管理型二层/三层交换机,拥有足够的PoE+预算为所有AP供电。在所有上行链路和AP中继端口上配置802.1Q VLAN标记。连接POS终端或员工工作站的接入端口应作为未标记成员分配到公司VLAN。AP端口应配置为承载所有所需VLAN的中继端口,并由无线控制器将每个SSID映射到相应的VLAN。

步骤4:防火墙与流量整形

UTM防火墙是所有安全和带宽策略的执行点。关键配置包括:

  • VLAN路由规则: 允许宾客VLAN访问互联网;拒绝宾客VLAN访问所有内部子网。
  • 每用户带宽限制: 实施流量整形策略以限制个人吞吐量。标准起点是每用户5 Mbps下行/2 Mbps上行。这可防止单个用户流式传输4K视频而降低所有其他宾客的体验。
  • 应用控制: 在防火墙级别阻止点对点文件共享协议(BitTorrent、eDonkey)和其他高带宽或非法应用程序。
  • DNS过滤: 实施基于DNS的内容过滤,以阻止访问恶意域、钓鱼网站和不适当内容类别。有关此层的详细指南,请参阅 使用强大的DNS和安全保护您的网络

步骤5:Captive Portal配置

Captive Portal是部署中最显眼的组件,也是主要的数据捕获机制。配置门户时,请确保:

  • 启动页面通过HTTPS提供,并具有有效的、公众信任的SSL证书,以防止浏览器安全警告。
  • 认证选项至少包括电子邮件/密码和社交登录(Google、Facebook、Apple),以最大限度地提高转化率。
  • AUP清晰显示,并要求在授予访问权限前明确接受。
  • 营销通信的GDPR同意通过单独的、未勾选的选择加入复选框捕获。
  • 配置会话超时和重新认证间隔,以平衡用户便利性和安全性。

最佳实践与合规

compliance_checklist.png

GDPR与数据隐私

如果您为营销目的收集用户数据,根据英国GDPR和欧盟GDPR,必须获得明确、知情的同意。法律要求毫不含糊:禁止预先勾选的同意框;同意必须是自由给予、具体、知情且明确的;用户必须能够像给予同意一样轻松地撤回同意。您的Captive Portal必须清楚说明收集哪些数据、处理的法律依据、数据将如何使用以及保留多长时间。

会话日志与法律合规

在英国,《调查权力规范法》(RIPA)及相关立法可能要求场馆运营商保留连接日志——包括MAC地址、时间戳和IP分配——以便在网络发生非法活动时协助执法。请咨询您的法律顾问,以确定适用于您组织和管辖区的具体保留义务。

WPA3与加密标准

对于任何使用预共享密钥(例如员工网络)的SSID,强制使用WPA3-Personal(SAE)而不是WPA2。WPA3消除了WPA2四次握手中固有的离线字典攻击漏洞。对于使用802.1X基于证书认证的企业员工网络,采用192位模式的WPA3-Enterprise可提供最高级别的保证。有关保护无线基础设施物理和逻辑层的更多信息,请参阅 接入点安全:您的2026企业指南

应对MAC地址随机化

现代iOS(自iOS 14起)和Android(自Android 10起)设备默认使用MAC地址随机化,为每个WiFi网络生成唯一的随机MAC地址。这意味着MAC地址不再能够可靠地用于识别回头客或建立长期用户档案。正确的架构响应是在Captive Portal强制实施基于身份的认证——要求用户通过电子邮件或社交账户登录——这样,用户档案而非硬件标识符就成为持久的跟踪实体。


故障排除与风险缓解

即使设计良好的网络也会遇到运营问题。下表总结了最常见的故障模式及其推荐的缓解措施。

故障模式 根本原因 缓解措施
DHCP耗尽 子网太小或租约时间相对于客流量过长 使用/22或更大子网;将租约时间缩短至30-60分钟
同信道干扰 重叠覆盖区域内多个AP使用相同信道 在无线控制器上启用动态信道分配
Captive Portal SSL错误 门户服务器上的证书无效或自签名 部署有效的公共CA证书;使用Let's Encrypt
漫游缓慢 AP未共享客户端关联数据 在无线控制器上启用802.11r(快速BSS转换)
带宽饱和 未配置每用户流量整形 在防火墙上实施每用户QoS策略
宾客到公司的横向移动 扁平网络或ACL配置错误 审计VLAN ACL;对宾客VLAN进行渗透测试

ROI与业务影响

一个正确部署的热点超越了其作为IT基础设施的功能——它成为一个第一方数据引擎和直接的营销渠道。投资于托管宾客WiFi平台的商业案例在每个垂直领域都令人信服。

酒店业 ,宾客WiFi数据使酒店能够了解宾客在连接前后使用了哪些设施,个性化住中沟通,并通过自动化的离店后活动推动重复预订。一家拥有300间客房的酒店每天捕获200个电子邮件选择加入,每年可建立一个包含70,000个选择加入联系人的营销数据库——这是一笔重要的CRM资产。

零售业 ,WiFi分析提供客流热力图、各区域停留时间和重复访问率——这些数据以前只能通过昂贵的人工调查获得。零售商可以利用这些数据优化店面布局、衡量促销展示的影响,并在已知客户进入商店时触发忠诚度活动。

对于公共部门和 交通 运营商而言,价值主张在于运营效率:了解高峰拥堵时段、优化人员配置,以及为市民和乘客提供便捷的数字服务。

像Purple的 宾客WiFiWiFi分析 这样的平台提供了将原始网络连接到这些业务成果的托管基础设施层。正如Purple的战略扩张所证明的——包括最近进入新垂直领域的举措,如在宣布 教育副总裁Tim Peers加入团队 时所强调的那样——智能互联空间的价值正在所有经济领域迅速扩展。

从基本的互联网连接过渡到智能的、数据驱动的网络是现代企业WiFi部署的决定性特征。基础设施成本在很大程度上是固定的;随着营销数据库的增长和自动化工作流程的成熟,在托管平台层上的增量投资将带来复合回报。

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.