Get One Month of Starlink FreeSPECIAL OFFER: GET A FREE MONTH OF STARLINK >
Ethernet cables and networking equipment for Starlink accessories

How to Set Up UniFi With Starlink: Bypass Mode, VLANs and Troubleshooting

Equipment & Accessories

Back to Equipment & Accessories

If you already use UniFi for Wi-Fi, switching your Starlink network to a UniFi gateway can give you clearer VLANs, firewall rules and device visibility. The important part is keeping one device in charge of routing and DHCP.

This guide covers Starlink kits that expose Ethernet and UniFi Cloud Gateways or Dream Machines that can act as the network gateway. UniFi access points or switches alone do not replace the router.

Before you start

Have these ready:

  • Your Starlink kit type and the correct Ethernet path for it.
  • A UniFi gateway with a working WAN port.
  • A laptop or phone for the Starlink app and UniFi Network.
  • A backup of the UniFi configuration if this is an existing network.
  • A record of the current Starlink Wi-Fi name and password in case you need to roll back.

The cable path varies by kit. Some Standard Actuated kits need the Starlink Ethernet Adapter. Starlink Standard has Ethernet on the power supply. Starlink Mini uses a USB-C to Ethernet adapter, while some Performance and Enterprise kits expose Ethernet from the power supply. Do not force a connector or assume every Starlink router has the same ports.

Choose the routing layout

For a clean UniFi network, use this layout:

unknown node

The UniFi gateway should be the only device doing local routing, DHCP and firewalling. Do not connect a Starlink LAN port to a UniFi LAN port while also connecting Starlink Ethernet to the UniFi WAN; that can create a loop or an accidental second path.

If your kit has an external power supply with native Ethernet, connect that Ethernet output to the UniFi WAN. Starlink says bypass mode is generally not needed on those kits because the power supply can act as the modem. If the Starlink router is the device providing Wi-Fi and routing, use Bypass Mode so UniFi can manage the network instead.

Connect Starlink to the UniFi WAN

  1. Power down the Starlink and UniFi gateway before moving cables.
  2. Connect the dish or Starlink power supply using the kit-specific Ethernet path.
  3. Plug the Starlink Ethernet cable into the UniFi gateway WAN port, not a LAN port.
  4. Connect your UniFi switch and access points to UniFi LAN ports.
  5. Leave the Starlink router Wi-Fi off once the UniFi network is working, unless you intentionally need it as a temporary separate network.

Restore power to Starlink first and wait until the Starlink app reports that the service is online. Then power the UniFi gateway and allow it a few minutes to request a WAN address.

Enable Bypass Mode when your kit needs it

On supported Starlink routers, open the Starlink app and look under Settings for Bypass Mode. Read the warning, then enable it. This turns off the built-in Starlink Wi-Fi so the third-party UniFi gateway manages the network.

Bypass Mode is not identical across every kit. Some kits use the Ethernet Adapter, some have Ethernet on the power supply, and older hardware may be replaced rather than bypassed. On supported routers, leaving Bypass Mode normally requires a manual factory reset, which can remove the router's saved settings. Treat that as a rollback step, not as a casual troubleshooting button.

Configure the UniFi WAN

In UniFi Network, open the Internet or WAN settings for the port connected to Starlink.

Use:

  • IPv4 connection: DHCP or Auto
  • PPPoE: off unless your service provider specifically requires it
  • Static IP: off unless Starlink or another upstream provider has assigned one
  • VLAN tagging: leave blank unless your service documentation explicitly requires it
  • DNS: keep the default while testing; change it later only if you have a reason

Apply the settings and confirm that the WAN interface receives an address. A Starlink connection may still sit behind provider CGNAT, so a WAN address does not automatically mean that inbound port forwarding will work.

The first verification should be simple: connect a laptop to a UniFi LAN port, confirm it receives a local address from UniFi, open a few websites, and run a speed and latency test. Test over Ethernet before judging the Wi-Fi configuration.

Build the internal UniFi networks

Start with one working LAN before adding segmentation. After that, create separate networks only where they solve a real problem.

A practical small setup is:

  • Main: laptops, phones and trusted household devices
  • IoT: plugs, televisions and devices that do not need access to your computers
  • Guest: visitors and short-term devices

In UniFi Network, go to Settings > Networks and create a virtual network for each segment. Give each one a distinct subnet and VLAN ID, enable DHCP on the UniFi gateway, then assign Wi-Fi networks and switch ports to the intended segment.

For example:

  • Main: VLAN 10, 192.168.10.0/24
  • IoT: VLAN 20, 192.168.20.0/24
  • Guest: VLAN 30, 192.168.30.0/24

The exact numbers do not matter; consistency does. UniFi creates and routes these VLANs behind the Starlink connection. Starlink does not need to know about the internal VLAN IDs.

Keep inter-VLAN access blocked by default. Add narrow allow rules only when you know the destination and port. If a printer, smart-home hub or camera recorder needs to be discovered from another VLAN, configure the required mDNS or firewall exception deliberately instead of opening every network to every other network.

On UniFi switches, use the correct port profile: an access-style profile for a single-purpose device and a trunk-style profile for an access point carrying several SSIDs. If a VLAN client cannot get an address, inspect the entire path from the gateway to the switch and access point. One untagged or missing VLAN on an uplink can make an otherwise correct network look offline.

Verify the finished setup

Run this short checklist:

  1. The UniFi WAN shows an address and the gateway reports internet access.
  2. A wired laptop receives a Main-network address from UniFi.
  3. Devices on each SSID receive addresses from the expected subnet.
  4. Guest devices can reach the internet but cannot reach Main devices.
  5. IoT devices can reach only the services they need.
  6. The Starlink app still shows dish and service health, or you have followed the kit-specific support steps if it reports the router as unreachable.
  7. There is no second Ethernet path between Starlink LAN and UniFi LAN.
  8. UniFi backups and the Starlink account login are available before you make further changes.

Troubleshoot in the right order

UniFi WAN has no address: check the cable path, confirm the cable is in the WAN port, verify the correct adapter for your kit, and confirm the WAN is set to DHCP. Reboot the Starlink equipment first, then the UniFi gateway.

Internet works but the Starlink app says the router is unreachable: treat that as a management-path issue, not proof that the internet is down. Check the Starlink support instructions for your exact kit before adding routes or changing firewall rules.

You still have double NAT: confirm that Bypass Mode is enabled when your kit requires it, that UniFi is the only local DHCP server, and that Starlink LAN is not also connected to UniFi LAN.

A VLAN client has no internet: verify the VLAN exists on the gateway, DHCP is enabled, the SSID or switch port has the correct network profile, and every uplink carries the VLAN tag.

Local discovery stopped working: isolation is doing its job, but the rule may be too broad. Permit only the required mDNS or service traffic between the specific VLANs, then test again.

Safe rollback

If the migration fails, return to one simple path: Starlink to the UniFi WAN, one UniFi LAN, and no VLANs. Restore the UniFi backup if needed. If you enabled Bypass Mode on a kit that requires a reset to leave it, plan for a manual factory reset and reconfiguration rather than repeatedly power-cycling the equipment.

Sources