UniFi-SonicWall VLAN Configuration

$30-250 USD

Posted about 2 hours ago

•

Ends in 6 days

$30-250 USD

Paid on delivery

I want my UniFi switches and access points to pass three clearly separated VLANs—staff, guest Wi-Fi, and office devices—through to a SonicWall firewall. The end goal is for staff and office devices to communicate as normal, while anyone on the guest Wi-Fi SSID sees nothing but the open internet; no visibility or reachability to staff workstations, servers, printers, or any other internal resources. Current gear: several UniFi 8- and 24-port PoE switches, a mix of UniFi UAP AC access points, and a SonicWall TZ series firewall already in place. Firmware on everything is current, and the UniFi Controller is cloud-hosted. Scope of work • Define VLAN IDs for staff, guest, and office devices inside UniFi Controller and on the SonicWall. • Tag and trunk the appropriate switch ports, then assign the wireless SSIDs to the correct VLANs. • Build matching sub-interfaces/routing rules on the SonicWall, including DHCP scopes. • Apply SonicWall firewall rules to ensure the guest network is restricted to “Internet only, no LAN.” • Verify end-to-end: devices in each VLAN receive correct IPs, can access intended resources, and cannot cross into other VLANs. • Provide a short hand-off document outlining the final topology, VLAN IDs, and any core rules you created. I will supply remote access to the UniFi Controller and SonicWall management interface. Once the VLAN segregation and guest isolation test cleanly, the job is done.

Project ID: 40807964

About the project

24 proposals

Open for bidding

Remote project

Active 39 mins ago

Place your bid

Bid amount Email address

Benefits of bidding on Freelancer

Set your budget and timeframe

It's free to sign up and bid on jobs

24 freelancers are bidding on average $122 USD for this job

User Avatar
Flag of PAKISTAN

Designing and securing multi-VLAN networks across Ubiquiti wireless infrastructure and SonicWall firewalls is directly aligned with my 10+ years of experience as a network and cybersecurity engineer. I have worked with Ubiquiti wireless and switching environments, along with SonicWall security platforms, and can apply best-practice routing, trunking, DHCP, and firewall segmentation to your setup. My background in network administration, routing, switching, wireless, and network security matches the full scope of this project. I can configure the UniFi Controller, SSID-to-VLAN assignments, tagged switch uplinks, SonicWall sub-interfaces and DHCP scopes, then validate that staff and office devices communicate appropriately while guest Wi-Fi remains limited to internet access without visibility of internal resources. I will also provide the requested concise topology and rules hand-off document. I am available to take ownership of the configuration and verification and would be glad to deliver a clean, secure UniFi–SonicWall VLAN implementation.

User Avatar
Flag of INDIA

Your UniFi–SonicWall VLAN project requires careful cloud-managed configuration and reliable end-to-end validation, and my cloud computing background supports work across remotely administered infrastructure. I can configure the three network segments in the UniFi Controller and SonicWall, align VLAN tagging and trunks, and ensure the guest SSID is separated from internal resources. I will focus on the specific security outcome you need: staff and office devices retaining intended communication while guest Wi-Fi is limited to internet access through appropriate firewall rules and DHCP scopes. I can also provide a concise hand-off document covering the final topology, VLAN IDs, and core rules, with verification of addressing, access, and isolation across the UniFi switches, access points, and SonicWall. Choose me to deliver a clean, documented VLAN configuration with guest isolation properly tested end to end.

User Avatar
Flag of PHILIPPINES

It is important that your VLAN tagging and SonicWall policies match up. You may have configured things to look correct in the UniFi system, but if you don’t make sure the trunk ports, firewalls and inter-VLAN policies match up the config will be incomplete. I would set up the 3 VLANs on the UNiFi Controller and SonicWall. Assign each SSID to it’s required VLAN. Check DHCP and Routing settings for all networks. The guest network will need specific rules to deny all internal subnets. Allow access to the internet. Ensure the order of the rules are correct so that there isn’t a general allow rule that could override the guest network. Test your connectivity between all VLANs. Try to connect to internal devices from the guest Wi-Fi. Document your final VLAN configuration, port assignments, DHCP ranges and firewall rules so that it will be an easy setup to manage going forward.

User Avatar
Flag of COLOMBIA

Your project’s wireless VLAN separation aligns directly with my Wireless expertise and strong background in system integration and troubleshooting. As a Senior Electronics Engineer with over 8 years of experience delivering and validating complex technical systems, I can work across the UniFi wireless environment and SonicWall configuration to support reliable separation between staff, office devices, and guest access. I understand the importance of more than simply assigning SSIDs: VLAN tagging, trunk paths, DHCP, routing, and firewall policy must work together so staff and office users retain intended connectivity while guest Wi-Fi remains internet-only. My experience carrying projects through implementation, testing, validation, and documentation is well suited to your end-to-end verification requirements and hand-off document. I am ready to take ownership of the configuration and validation, and I would welcome the opportunity to complete this UniFi–SonicWall VLAN segregation securely and cleanly.

User Avatar
Flag of UNITED ARAB EMIRATES

Your UniFi SonicWall VLAN project requires careful network administration and security, and my nearly 20 years in technology supported by a Bachelor’s degree in Computer Science and expertise in Cisco, network administration, and network security—provide a strong foundation for this work. I am ready to take ownership of the configuration and validation, and I would be glad to deliver a clean, secure handoff for your UniFi and SonicWall environment.

User Avatar
Flag of THAILAND

I’ve configured segmented UniFi and SonicWall networks with tagged switch uplinks, isolated guest SSIDs, DHCP scopes, and firewall policies for multi-device offices. For this project, the key is aligning VLAN IDs and trunk membership across UniFi and SonicWall sub-interfaces, because one mismatch can break DHCP or isolation. I’ll define staff, guest, and office networks in the cloud controller, assign AP SSIDs and switch ports correctly, and configure matching SonicWall interfaces, scopes, routing, and access rules. I’ll validate addressing and intended staff/office connectivity, then confirm guest clients have internet access only with no internal reachability. You’ll receive a concise hand-off document covering topology, VLAN IDs, port roles, and core firewall rules. Thanks, Kittipong

User Avatar
Flag of SLOVAKIA

I can configure this UniFi-to-SonicWall VLAN segregation end to end. Plan: define staff/guest/office VLAN IDs, set UniFi switch ports as trunks (tagged VLANs) to the SonicWall and APs, assign each SSID to its VLAN in the controller . On SonicWall, create matching VLAN sub-interfaces with DHCP scopes per VLAN . Then firewall rules: guest zone gets WAN access only, with an explicit Deny to LAN/RFC1918 placed correctly in the rule order . I'll verify each VLAN gets correct IPs, staff/office communicate, and guest cannot reach any internal resource, then hand over topology and rule documentation. What are your planned VLAN IDs and subnets, or should I propose a scheme?

User Avatar
Flag of UKRAINE

Hello, Your UniFi wireless environment needs dependable VLAN separation so guest traffic reaches only the internet, and my experience with wireless communication and industrial control systems gives me a strong foundation for working across connected hardware and networked equipment. I can configure the three VLANs in the UniFi Controller and SonicWall, assign the relevant SSIDs, establish tagged switch paths, and apply the firewall segmentation required to prevent guest access to staff and office resources. My 10+ years in electronics, embedded systems, automation, commissioning, troubleshooting, and system integration are directly relevant to careful end-to-end validation across your switches, access points, and firewall. I will also provide the requested hand-off document covering the final topology, VLAN IDs, and core rules. Choose me for a practical, test-focused configuration and clear documentation. Thanks!

User Avatar
Flag of UNITED STATES

Hi there, hope you are doing well. My name is Dominique from Scottsdale, AZ. I went through your project description and understood what you want. I have been working as a Sr. Software engineer and enough qualified in System Admin, Cloud Computing, Network Administration and I have completed similar projects before. I would love to connect in chat to discuss details Best regards, Dominique Coleman

User Avatar
Flag of UNITED STATES

Hi, one thing worth settling before I touch a port: your cloud controller reaches the switches and APs over whatever network they sit on today, so that management subnet has to stay untagged on every uplink while the new VLANs go on as tagged. Get the order wrong and devices drop out of adoption mid-change, and a remote job becomes a site visit. What I'd build: X0 stays as the existing LAN, with VLAN sub-interfaces for staff, guest and office devices, each with its own DHCP scope on the TZ. Guest gets its own zone with Public security type, so the default rule toward LAN is already deny, then I add explicit denies to every internal zone and the SonicWall's own management, leaving only DNS and outbound internet. Client isolation goes on the guest SSID as well, so guests can't see each other. The handoff note will cover the VLAN and subnet table, which switch ports are trunks, SSID to VLAN mapping, every rule I added, and the test results from each VLAN. Send over controller and SonicWall access when ready. Do your printers and servers use static IPs, and should staff to office devices be fully open or limited to printing and file shares? Thanks, Daniel

User Avatar
Flag of SOUTH AFRICA

Hey, Just finished a similar VLAN segregation for a university network—separating staff, guest Wi‑Fi, and IoT devices on UniFi switches/APs with a SonicWall firewall, ensuring zero inter‑VLAN leakage while keeping full LAN access for staff and office gear. We’re the perfect fit. I specialize in UniFi Controller VLAN setups, precise switch trunking, SSID‑to‑VLAN mapping, SonicWall sub‑interface routing, DHCP scope configuration, and strict firewall rule creation for “Internet‑only” guest access. I’ll validate connectivity, deliver a concise hand‑off document, and confirm all devices get correct IPs and isolation. Multiple 5‑star reviews on complex network and firewall projects. Let’s hop on a quick chat; if not, I’ll offer a free consultation and a solid plan. Chris | Lead Developer | Novatech

User Avatar
Flag of PAKISTAN

Hello, I understand the objective is to establish three properly segmented VLANs across your UniFi infrastructure and SonicWall firewall, while ensuring staff and office devices retain their required connectivity and guest Wi-Fi has internet access only. The configuration needs coordinated VLAN tagging, switch trunking, SSID assignments, DHCP scopes, and SonicWall access rules, followed by end-to-end testing to verify that guest devices cannot reach internal networks. My background includes cloud infrastructure, server deployment, and technical troubleshooting, but I should be transparent that I don't have verifiable hands-on experience configuring UniFi and SonicWall networks in production. I would not want to misrepresent myself as a dedicated network administrator. Also a quick question, would you consider a technical implementation partner working alongside a UniFi and SonicWall networking specialist for this configuration? Best Regards, Naseem.

User Avatar
Flag of ECUADOR

Hi, Primary risk is improper VLAN tagging or trunk configuration on UniFi switches causing guest leakage into internal LAN or DHCP scope overlap on the SonicWall. I will eliminate that by defining distinct VLAN IDs, creating SonicWall subinterfaces with nonoverlapping DHCP scopes, and verifying tags on every trunk and access port. I have implemented VLAN segregation and guest isolation on UniFi + third party firewalls in multiple office deployments, including multi-switch PoE environments with UAP AC access points. Those projects required configuring cloud-hosted UniFi Controller networks, tagging trunk ports, assigning SSIDs to VLANs, and building firewall rules that allow Internet only for guests while preserving staff and office device communication. I also produce concise hand-off documents for operators. I will start by auditing the current UniFi Controller network settings and SonicWall interface layout, then create VLAN IDs and subinterfaces on the SonicWall, configure DHCP scopes, tag/trunk switch ports, and assign SSIDs to VLANs. I will finish with targeted firewall rules on the SonicWall to enforce guest isolation and perform end-to-end verification with test clients. - Do you have preferred VLAN IDs or should I propose a numbering plan during the audit? - When can you provide remote access to the UniFi Controller and SonicWall management interface for an initial audit? Open to a quick chat if you want to dig into the details. sergiom17

User Avatar
Flag of CANADA

⭐⭐⭐Hello, I can configure the three VLANs across your UniFi gear and SonicWall TZ, and I want to flag the one design decision that determines whether guest isolation actually holds. I would define staff, guest, and office VLAN IDs consistently in UniFi and SonicWall, trunk the switch uplinks carrying all three tagged, set access ports to the correct native VLAN, and map each SSID to its VLAN. On the SonicWall I would create matching sub-interfaces with DHCP scopes and routing, then build guest rules as a zone pair that denies guest-to-LAN and guest-to-other-VLAN in both directions while allowing guest-to-WAN — the direction matters because a one-way deny still lets internal hosts reach guest devices. I would also keep guest-to-SonicWall-management blocked and confirm UniFi's own guest policies aren't set to override the SonicWall rules, since two isolation mechanisms running together is a common cause of confusing results. Verification would test DHCP assignment per VLAN, intended access for staff and office, and a full isolation check from a guest client — ping and port attempts against internal hosts, plus a scan for any reachable internal service. Hand-off includes the final topology, VLAN IDs, and the core rules created. Remote access to the cloud-hosted controller and SonicWall is fine, and I am ready to start. Best Regards

User Avatar
Flag of IRELAND

This is squarely what we do day to day. I run a small MSP in Ireland and regularly deploy UniFi switching and Wi-Fi behind SonicWall TZ firewalls, including exactly this staff / devices / guest split. How I'd approach it: • Agree a VLAN and IP plan with you first (e.g. 10 Staff, 20 Office Devices, 30 Guest), then build matching VLAN sub-interfaces on the SonicWall with their own zones and DHCP scopes • Create the networks in UniFi, apply port profiles to trunk uplinks and set access ports, and map each SSID to its VLAN • Put Guest in its own zone with rules allowing Internet only and denying all access to LAN, servers, printers and the firewall's management. Client isolation is also enabled on the guest SSID • Leave switch and AP management on the existing network so nothing drops off the cloud controller during the change • Test from a device on each VLAN (addressing, intended access, blocked cross-VLAN traffic) and hand over a short document with the topology, VLAN IDs, scopes and rules I can do this remotely with minimal disruption, ideally in an agreed out-of-hours window.

User Avatar
Flag of BANGLADESH

I really want to work with you. Please don't ignore me. First off, I really appreciate how clearly and thoroughly you structured your scope of work—it's rare and refreshing to work with a client who outlines their network requirements so precisely down to the sub-interface and rule level. This is a textbook 802.1Q Router-on-a-Stick setup between the SonicWall TZ and your UniFi gear. Here is how I will handle the implementation: 1. SonicWall TZ Configuration: Build the virtual sub-interfaces (e.g., on X0), map them to proper zones (trusted LAN for Staff/Office and Guest/DMZ for Wi-Fi), configure dedicated DHCP scopes, and apply strict access rules so Guest traffic can only reach the WAN while blocking RFC1918 internal subnets and SonicWall management access. 2. UniFi Controller Setup: Define the networks as "Third-Party Gateway / VLAN-only", configure proper trunk profiles for the switch-to-firewall and switch-to-AP links, and assign wired ports and SSIDs to their respective VLANs. I’ll make sure the native management VLAN remains untouched so the cloud controller and devices never lose connectivity during the transition. 3. Validation & Hand-off: Conduct end-to-end tests (DHCP lease verification, cross-VLAN communication between Staff and Office, and complete Guest isolation). Once verified, I’ll deliver a neat, one-page hand-off summary outlining the VLAN IDs, subnets, and active firewall policies. Nazez Masud

内容来自 Freelancer News,版权归原作者所有。

阅读原文 ↗

把喜欢的内容,留在你的新标签页。

打开我的订阅