How to Add an Ethernet Switch to Starlink for Multiple Wired Devices

Independent owner's guide: Starlink Tips is not part of Starlink. Results vary with location, hardware, obstructions, Wi-Fi and network conditions.

A network switch is the simplest way to give several wired devices a place on your Starlink network. It can connect a television, games console, desktop computer, printer, camera recorder or NAS without buying another internet plan or turning every device into a separate router.

The important detail is where the switch sits. A switch adds Ethernet ports; it does not replace the router, provide Wi-Fi, solve CGNAT or improve the signal from the dish.

What you need

• A Starlink kit with a usable Ethernet or LAN output. Depending on the kit, that may be a built-in router port, an official Ethernet Adapter or a kit-specific Ethernet cable. Check Starlink's current router specifications before ordering cables or adapters.
• An unmanaged Gigabit Ethernet switch with enough ports for the devices you want to wire, plus one port for the uplink from the router.
• Cat5e or better Ethernet patch cables long enough to reach the switch and each device.
• One phone or computer already connected to your Starlink network for testing.

An unmanaged switch is the right choice for most homes because it adds ports without introducing another configuration screen. A managed switch is useful only when you already understand features such as VLANs, tagged uplinks and loop protection.

Do not assume that a PoE switch can power a Starlink dish or router. Ethernet ports and Power over Ethernet are different things. Use the power supplies and cables specified for your hardware unless the equipment documentation explicitly supports the required PoE standard and power budget.

Choose the correct layout

Your layout depends on which device is doing the routing and handing out local IP addresses.

Starlink router remains the main router

This is the least disruptive option when you only need more wired ports:

Use a LAN or Ethernet output from the Starlink router, not the cable or port that connects to the dish. If your kit needs an Ethernet Adapter, install that first and connect the switch to the adapter's Ethernet output.

Your own router is the main router

If your Starlink hardware is in bypass mode, the third-party router should receive the Starlink connection on its WAN port. The switch then connects to a LAN port on that router:

Do not put the switch between the Starlink output and the third-party router's WAN port. The switch belongs on the LAN side, after the router has provided routing, DHCP and firewall protection. Starlink's bypass-mode guidance notes that bypass disables the Starlink router's Wi-Fi features, so have the replacement router ready before enabling it.

A second router is being used as an access point

If you keep the Starlink router as the main router and use another router only for extra Wi-Fi, configure the second device as an access point or bridge if its manufacturer supports that mode. Connect the switch downstream of the device that is meant to serve the wired clients, following that device's LAN or uplink instructions.

The finished network should have one clear router and one DHCP service. Two devices both acting as full routers can create double NAT, split device discovery and make printers, cameras and file shares harder to reach.

Step-by-step setup

1. Identify the router that should own the network

Write down which device is connected to the Starlink dish and which device should provide local addresses. In a simple Starlink-only setup, that is the Starlink router. In a bypass setup, it is your third-party router.

If you are unsure, connect one computer directly to the intended router first and confirm that it can browse the internet before adding the switch.

2. Place and power the switch

Put the switch somewhere dry and ventilated, close enough that the uplink cable does not need to be stretched or sharply bent. Connect its supplied power adapter. Leave room to see the link lights while you test.

Do not place the switch outdoors or in a wet dish-side enclosure unless the switch is specifically rated for that environment.

3. Connect the uplink

Use one Ethernet cable from a LAN port on the main router, Ethernet Adapter or access point to any normal port on the switch. Most unmanaged switches do not have a special uplink port. If your switch labels one port as uplink, use it for the router connection.

Never connect the switch to the Starlink terminal cable, and do not connect two switch ports back into the same network unless you have deliberately configured and tested loop protection.

4. Connect the wired devices

Connect the TV, console, computer, printer, camera recorder or NAS to the remaining switch ports. Leave one port free if you expect to add another device soon. Use short cables where possible and label both ends of long runs.

The switch does not need a separate Starlink login. It simply passes local network traffic between the router and the wired devices.

5. Confirm that one device provides addresses

On each device, leave IP settings on automatic unless you have a specific network design. Check that the device receives:

• A private IP address
• The same local subnet as your Starlink Wi-Fi devices
• A default gateway belonging to the intended router
• A usable DNS server

If devices receive no address, check the router path before changing random settings. A switch normally does not provide DHCP.

6. Test one device at a time

Start with one computer or laptop:

1. Confirm the Ethernet link light on the switch is on.
2. Open a website and run one speed test.
3. Compare the result with a nearby Wi-Fi device.
4. Open the Starlink app and confirm the connection is healthy.
5. Add the next device only after the first one works.

Then test local services. Print a test page, open the NAS dashboard or view a camera recorder from a device on the same default network. A successful internet test does not prove that local discovery is working.

Practical limits to expect

All devices share the switch's uplink to the router. A Gigabit switch can carry local traffic between compatible wired devices at high speed, but several large transfers can still compete for the single uplink. Starlink's internet capacity, upload speed and busy-period congestion remain separate limits.

A switch also does not:

• Remove Starlink CGNAT
• Create a public or static IP address
• Make inbound port forwarding work
• Repair a damaged cable
• Improve dish obstructions or satellite coverage
• Turn a guest network into a trusted local network

Keep printers, NAS devices and other equipment that must communicate with one another on the intended default network. Starlink's guest mode is designed to restrict local communication, so a device on Guest may not be able to discover a device on your main network.

Troubleshooting

The switch has power, but no link light appears: Try another switch port and cable. Confirm that the upstream cable is connected to a LAN or Ethernet output, not a router WAN port or the Starlink terminal cable.

Devices connect to Ethernet but have no internet: Check which router is connected upstream. In bypass mode, the third-party router must be ready to obtain the Starlink WAN connection and provide LAN addresses. If you added a second router, check whether it is in access-point mode or accidentally running a second DHCP service.

The internet works, but the printer or NAS is invisible: Confirm that both devices are on the same default network and subnet. Guest isolation, a second router or a device firewall can block local discovery even when web browsing works.

The connection is slower than expected: Test with one wired device first, then check the cable category, switch link speed and router uplink. Pause large downloads, uploads or backups while comparing results. A switch cannot increase Starlink's available bandwidth.

The Starlink app says the terminal is unreachable after adding a third-party router: Starlink says some third-party routers may need a static route to the terminal's 192.168.100.0/24 network. Follow your router's documentation and the Starlink app guidance for third-party routers. Do not guess at routes if you are not sure which device is acting as the WAN router.

The network becomes unstable after rearranging cables: Look for a loop. A loop can occur when the same switch or access point is connected to the network by two paths without loop protection. Disconnect the extra path, restore the simple router-to-switch layout and retest.

Finished setup checklist

• [ ] The switch is connected to a LAN-side Ethernet output.
• [ ] The Starlink terminal cable is not being used as a switch uplink.
• [ ] Only one device is providing routing and DHCP.
• [ ] The switch has no accidental second connection back into the same network.
• [ ] Wired devices receive automatic IP settings in the intended subnet.
• [ ] Local services such as printing or NAS access work where required.
• [ ] Guest-network isolation is understood before placing devices on Guest.
• [ ] PoE is not being used unless the hardware documentation explicitly supports it.
• [ ] The switch and cables are protected from moisture, heat and sharp bends.

For the wider hardware decision, see the Starlink Ethernet Adapter and bypass-mode guide. For a more security-focused wired setup, see How to Connect a NAS or Home Server to Starlink Safely.