By Natthawut (Ton) Khamnuadi • June 2026 • Business Account Executive at Metronet, Wichita Falls, TX

Almost every business offers guest Wi-Fi now. Restaurants, salons, medical waiting rooms, retail stores, auto repair lobbies. Customers expect it. And honestly, it is good for business. People stay longer, leave better reviews, and come back more often when they can get online while they wait.

But here is the problem I see constantly when I walk into local businesses: the guest Wi-Fi password is taped to the counter, and it is the same network the POS system runs on. The same network where the office computers connect. The same network processing credit card transactions. That is two problems in one. First, a waiting room full of people streaming TikTok can choke out your card reader mid-transaction. Second, every one of those guest devices is sitting on the same network as your payment data, which is a real security risk.

I have spent over a decade in telecommunications, starting as a Tier 3 Network Technician at T-Mobile where I worked on everything from cellular tower infrastructure to LAN/WAN configurations to DNS and DHCP troubleshooting. I have seen network problems from every angle. And the guest Wi-Fi issue is one of the easiest to fix once you know what to do.

Why Your Current Setup Is Probably Wrong

Most small businesses have one router, one network name, and one password. Everything connects to it. The POS terminal, the office laptop, the security cameras, the smart TV in the lobby, and every customer who asks for the Wi-Fi password. All of it shares the same pool of bandwidth and the same network segment.

This creates two specific problems that cost you money.

Problem 1: Guests eat your bandwidth

A single person streaming video on their phone uses about 5-8 Mbps. Someone on a video call pulls 3-5 Mbps. Even casual scrolling through Instagram or TikTok uses 2-3 Mbps because of auto-playing video content. Now multiply that by a busy lunch rush at a restaurant, or a full waiting room at a medical clinic.

If you have 25 people connected and each one is using 3-4 Mbps on average, that is 75-100 Mbps of bandwidth going to guest devices. If your internet plan is 100 or even 200 Mbps, your POS system, your cloud-based scheduling software, and your VoIP phones are all fighting for what is left. That is why the card reader freezes during peak hours. It is not broken. It is starving for bandwidth.

Problem 2: It is a security risk

When a customer connects to your business Wi-Fi, their device is on the same network as your internal systems. That means a compromised phone, a laptop running malware, or even someone who knows what they are doing could potentially see traffic on your network, access shared folders, or probe your POS system.

This is not hypothetical. According to the Verizon 2024 Data Breach Investigations Report, 20% of breaches involved small and medium businesses, and network intrusion was one of the top attack patterns. An unsegmented network with guest access is one of the easiest ways in.

If your business processes credit cards, PCI DSS (Payment Card Industry Data Security Standard) explicitly requires that your cardholder data environment be segmented from untrusted networks. A guest Wi-Fi network that shares a VLAN with your payment terminal is, by definition, out of compliance. If you got audited or breached, that would matter a lot.

The Fix: A Separate Guest Network with Its Own VLAN

The solution is straightforward, and in most cases it does not require buying new equipment. You need two things: a separate SSID (that is the network name your customers see) and a separate VLAN (that is the behind-the-scenes isolation that keeps guest traffic walled off from your business systems).

What is a VLAN?

VLAN stands for Virtual Local Area Network. Think of it as drawing a line down the middle of your network. Devices on one side cannot see or talk to devices on the other side, even though they are all connected to the same physical router and access points. Your business computers and POS system live on VLAN 1. Your guest Wi-Fi lives on VLAN 2. They share the same internet connection but cannot interact with each other.

When I was doing Tier 3 network support at T-Mobile, VLAN configuration was a daily task for managing different types of traffic across enterprise networks. It is standard practice in any properly configured business network. The good news is that most business-class routers and access points made in the last five years support VLANs and multiple SSIDs out of the box. If you have a router from your internet provider or even a mid-range access point like a UniFi, TP-Link Omada, or similar, you almost certainly already have this capability. You just need to turn it on.

How to set it up (the general steps)

Every router interface is a little different, but the process follows the same pattern on nearly all business-grade equipment:

Step 1: Log into your router or access point admin panel. This is usually a web address like 192.168.1.1 or 10.0.0.1. If you do not know the login credentials, check the sticker on the device or contact whoever set it up.

Step 2: Create a new SSID. Name it something your customers will recognize, like "YourBusinessName-Guest" or "YourBusinessName-Free-WiFi." Keep it simple. Do not name it the same as your business network.

Step 3: Assign that SSID to a separate VLAN. Most router interfaces have a section for VLAN tagging or network segmentation. Assign your guest SSID to a different VLAN ID than your primary business network. Common practice is VLAN 1 for business and VLAN 10 or VLAN 100 for guests.

Step 4: Enable client isolation on the guest network. This prevents guest devices from seeing each other, not just from seeing your business devices. It is an extra layer of protection and most access points have a checkbox for it.

Step 5: Set a password or use a captive portal. You can set a simple WPA2 or WPA3 password for the guest network (and change it monthly), or you can use a captive portal that requires guests to accept terms of service before connecting. Either works. The captive portal looks more professional and gives you some legal cover.

Bandwidth Allocation: How Much to Give Guests

Setting up the separate network is only half the solution. You also need to control how much bandwidth the guest network can use. Without a cap, a handful of guests streaming Netflix could still drag down your business operations even though the networks are separated, because they are sharing the same internet pipe.

The math on guest bandwidth

Here is how I think about it when I sit down with a business owner. You need to estimate two numbers: how many guest devices will connect at peak times, and how much bandwidth each one needs for a decent experience.

For most businesses, comfortable guest Wi-Fi means people can check email, scroll social media, browse the web, and maybe stream a short video without buffering. That requires about 2-5 Mbps per device. You do not need to give every guest 50 Mbps. They are not downloading software updates in your lobby. They are killing time.

Here is what the numbers look like for common business types:

Restaurant (casual dining, 40-60 seats): Expect 15-25 connected devices during peak hours. At 3 Mbps average per device, that is 45-75 Mbps for guest Wi-Fi.

Medical waiting room (15-20 chairs): Expect 10-20 connected devices. People wait longer at medical offices, so usage tends to be higher per person. Budget 50-80 Mbps for guests.

Hair salon or barbershop (6-10 chairs): Expect 8-15 devices. Clients are there for 30-60 minutes and will stream music or video. Budget 30-50 Mbps.

Retail store: Lower device counts since people are walking around, not sitting. Expect 5-15 devices. Budget 20-40 Mbps.

Auto repair or service center: Waiting rooms can have 5-15 people sitting for 1-3 hours. They will stream video. Budget 40-60 Mbps.

Set a hard cap on the guest VLAN

Once you know how much bandwidth guests need, set a maximum bandwidth limit on the guest VLAN. Most business routers support this through QoS (Quality of Service) settings or bandwidth throttling per VLAN.

For example, if you have a 500 Mbps fiber connection, you might allocate 100 Mbps to the guest VLAN and reserve 400 Mbps for your business operations. Even if every seat in your restaurant is taken and every customer is on their phone, they will share that 100 Mbps among themselves. Your POS system, your kitchen display, your office computer, and your VoIP phones all have 400 Mbps that guests can never touch.

You can also set per-device limits. Capping each guest device at 5 Mbps or 10 Mbps prevents one person from hogging the entire guest allocation by downloading a massive file or running a speed test on repeat.

What does this mean for your internet plan?

Add your business needs and your guest needs together. If your business operations require 100 Mbps and your guest network needs 75 Mbps at peak, you need at least 175 Mbps of total bandwidth. I would round up to 200-300 Mbps to leave headroom.

When I managed a Spectrum store on Kemp Blvd here in Wichita Falls, I talked to business owners every day who were on plans that barely covered their own operations, let alone guest traffic. They would sign up for 100 Mbps thinking it was plenty, then wonder why the card reader was slow every afternoon. Once you account for guest Wi-Fi, you often need more bandwidth than you think.

If you are running a busy location with 20-30 guest devices at peak times, a 500 Mbps or 1 Gbps fiber plan starts to make real sense. The cost difference between 200 Mbps and 500 Mbps on a business fiber plan is often only $30-50 per month. That is worth it when the alternative is a frozen POS terminal during your busiest hours.

The Security Side: PCI Compliance and Network Segmentation

If your business accepts credit or debit cards, you are subject to PCI DSS requirements whether you know it or not. Your payment processor agreed to these standards on your behalf when you signed up, and if something goes wrong, the liability falls on you.

PCI DSS Requirement 1 specifically covers network segmentation. The standard says that systems handling cardholder data must be isolated from systems that do not. A guest Wi-Fi network is explicitly considered an "untrusted network." If your POS terminal and your guest Wi-Fi sit on the same VLAN with no segmentation, you are out of compliance.

What does that actually mean in practice? If a breach occurs and your payment processor or acquiring bank investigates, the first thing a forensic auditor looks at is your network topology. If they find that guest devices had network-level access to your POS system, you could be held liable for the breach, face fines ranging from $5,000 to $100,000 per month of non-compliance, and potentially lose the ability to process credit cards entirely.

I am not saying this to scare anyone. I am saying it because most business owners I talk to have no idea this requirement exists. They think PCI compliance is something their payment processor handles. The processor handles their side. Your network is your responsibility.

What proper segmentation looks like

A properly segmented network for a small business that processes cards and offers guest Wi-Fi should have at minimum two VLANs:

VLAN 1 (Business): POS terminals, office computers, printers, security cameras, VoIP phones. Only authorized devices with known MAC addresses should be on this network. WPA3-Enterprise with unique credentials per device is ideal, but WPA3-Personal with a strong password that you do not share publicly will work for most small businesses.

VLAN 2 (Guest): Customer devices only. Bandwidth-capped, client-isolated, with no routing to VLAN 1. A simple password posted in the store or a captive portal splash page. This network can see the internet but cannot see anything else on your local network.

Some businesses add a third VLAN for IoT devices like smart thermostats, smart TVs, and connected security systems. These devices are notoriously insecure and should not sit on the same network as your POS system either. But two VLANs (business and guest) is the minimum to be compliant and protected.

Common Mistakes I See

After years of walking into businesses and looking at their network setups, these are the mistakes I see most often.

Using the ISP-provided residential router

Some businesses are running on a consumer-grade router that their internet provider dropped off. These routers are designed for a household of 5-10 devices, not a business with 30-50 connections including guest traffic. They overheat, they drop connections, and most of them do not support VLANs or multiple SSIDs properly. If you are running a business, you need a business-class router or access point. A good one costs $150-400, and it will last you years.

Sharing the business Wi-Fi password with everyone

I have walked into businesses where the Wi-Fi password is written on a whiteboard, printed on the receipt, or taped to the front door. And it is the same network the POS runs on. Every person who has ever connected to that network has had access to the business network. Former employees, delivery drivers, every customer who has been in the building. Change the business network password regularly and never share it publicly. The guest network password is the one you post.

Not setting bandwidth limits

Even businesses that have a separate guest SSID often skip the bandwidth cap. Without it, guest traffic is unlimited. Three teenagers streaming 4K video in your waiting room can use 45 Mbps by themselves. Set a per-device cap (5-10 Mbps is reasonable) and a total cap on the guest VLAN.

Never changing the guest password

If your guest password has been "Welcome123" since 2019, every device that has ever connected can auto-reconnect and use your bandwidth. Change it monthly. Some businesses change it weekly and print it on a small card at the register. That works well.

Assuming the IT person set it up correctly

I have seen setups where someone created a second SSID but did not actually assign it to a separate VLAN. On the surface it looks like two networks, but behind the scenes all traffic is on the same network segment. The SSID name is cosmetic. The VLAN assignment is what actually creates the separation. If you are not sure whether your setup is properly segmented, it is worth having someone verify it.

A Quick Checklist

Here is a simple list to check your guest Wi-Fi setup against. If you can say yes to all of these, you are in good shape.

1. Separate SSID. Your guest network has its own name that is different from your business network.

2. Separate VLAN. The guest SSID is assigned to a different VLAN than your business devices. Not just a different name, but actually isolated at the network level.

3. Bandwidth cap. The guest VLAN has a maximum bandwidth allocation so it cannot consume your entire internet connection.

4. Per-device limit. Individual guest devices are capped at 5-10 Mbps so one user cannot hog the guest allocation.

5. Client isolation. Guest devices cannot see or communicate with other guest devices on the network.

6. No routing to business VLAN. There is no route between the guest VLAN and your business VLAN. Guest devices cannot reach your POS, printers, or file shares.

7. Regular password changes. The guest network password is changed at least monthly.

8. Enough total bandwidth. Your internet plan covers both your business needs and the guest allocation with room to spare. If your business needs 100 Mbps and guests need 75 Mbps, your plan should be at least 250 Mbps to give yourself headroom.

This Is Usually Not a Big Project

I want to be clear about something: for most businesses, setting up a proper guest network is not a major expense or a complicated project. If you already have a business-class router or access point, it is a configuration change. Someone who knows what they are doing can set up the VLAN, create the guest SSID, configure bandwidth limits, and test it in about 30-60 minutes.

You do not need to run new cables. You do not need a second internet connection. You do not need to buy a second router (although a dedicated access point in a large space can help with coverage). The hardware you have can almost certainly do this. It just needs to be configured correctly.

When I ran my own business hauling oversize loads across all 50 states, I learned the hard way that the things that seem small are the ones that cost you the most when you ignore them. A tire blowout you could have prevented with a $20 inspection. A permit you forgot to pull that costs you a $500 fine. Guest Wi-Fi on your business network is the same kind of thing. It works fine until it does not, and then it costs you.

Let Me Take a Look at Your Setup

If you are not sure whether your guest Wi-Fi is set up correctly, or if you do not have one yet and want to do it right the first time, I am happy to help. I work with businesses here in Wichita Falls every day, and I can take a look at your current network, your bandwidth, and your equipment to figure out exactly what you need. No cost, no commitment. I can help you figure out the right setup for your space.

Schedule a Free Conversation