How to Prioritize Lan Over Wifi? Wired Priority Setup

Introduction

If you have ever asked, How to Prioritize Lan Over Wifi?, you are probably using a laptop or desktop that is connected to both a wired Ethernet cable and a wireless network at the same time. This setup is common in offices, home labs, gaming rooms, and hybrid workspaces. While having both connections available can provide redundancy, it can also create confusion when your operating system sends traffic over the slower or less stable Wi-Fi link instead of the wired LAN.

This guide explains How to Prioritize Lan Over Wifi? in a practical, step-by-step way. You will learn how operating systems choose a network, how to change interface metrics, how to adjust service order, how to use command-line tools, and how to verify that your wired connection is truly being used. The goal is not simply to make Ethernet “preferred” on paper, but to make sure real traffic, DNS queries, VPN tunnels, and application sessions use the wired path reliably.

Table of Contents

• Introduction
• What Does It Mean to Prioritize LAN Over Wi-Fi?
• Why Wired Priority Matters
• How Operating Systems Choose a Network
• How to Prioritize LAN Over Wi-Fi in Windows
• How to Prioritize LAN Over Wi-Fi on macOS
• How to Prioritize LAN Over Wi-Fi on Linux
• Router and Network-Level Considerations
• Docking Stations, VPNs, and Special Cases
• How to Verify LAN Is Actually Being Used
• Troubleshooting Common Issues
• Tips and Best Practices
• Comparison Table: Wired Priority Methods
• Frequently Asked Questions
• Conclusion

What Does It Mean to Prioritize LAN Over Wi-Fi?

When people search for How to Prioritize Lan Over Wifi?, they usually mean one of three things. First, they want their computer to use Ethernet for internet and local network traffic whenever it is plugged in. Second, they want Wi-Fi to remain available as a backup if the cable is disconnected. Third, they want applications to stop “sticking” to Wi-Fi after Ethernet becomes available.

Network priority is usually controlled by a value called an interface metric, route metric, or service order. A lower number generally means higher priority. For example, if Ethernet has a metric of 10 and Wi-Fi has a metric of 50, the operating system will usually prefer Ethernet for the default route. This does not necessarily disable Wi-Fi; it simply makes wired traffic the first choice.

It is important to understand that priority is not always a single switch. Modern systems use routing tables, DNS resolvers, VPN adapters, virtual switches, and application-level socket behavior. A good wired priority setup checks all of these layers instead of changing one setting and hoping for the best.

Why Wired Priority Matters

Wired Ethernet is usually more predictable than Wi-Fi. It is less affected by distance, walls, interference, neighboring networks, and radio congestion. For video calls, large file transfers, cloud backups, game streaming, and remote desktop sessions, a stable wired connection can make a noticeable difference.

Prioritizing LAN over Wi-Fi can also improve security. A wired connection is harder to intercept casually than wireless traffic, and it avoids risks associated with connecting to the wrong SSID. In shared environments, wired priority reduces the chance that your device silently uses a guest or public Wi-Fi network while Ethernet is available.

There are also performance reasons. Wi-Fi throughput can fluctuate even when signal strength looks good. Ethernet typically delivers consistent latency and fewer retransmissions. If your workflow depends on low latency, such as VoIP, trading platforms, live production tools, or remote engineering sessions, wired priority is worth configuring carefully.

How Operating Systems Choose a Network

Before changing settings, it helps to know why the system made its choice. Operating systems generally evaluate network interfaces using several factors:

• Link status: Is the cable connected and is the port up?
• Interface metric: Lower values usually win.
• Route metric: The default gateway with the lowest metric is preferred.
• Service order: On macOS, the order of network services matters.
• VPN state: VPN clients may install routes that override normal interface priority.
• DNS configuration: The active resolver can influence which interface is used for name resolution.
• Application behavior: Some programs bind to a specific adapter or remember a previous network.

Because of these layers, the answer to How to Prioritize Lan Over Wifi? is not always “change one setting.” A complete setup checks the adapter, route, DNS, VPN, and application behavior together.

How to Prioritize LAN Over Wi-Fi in Windows

Windows is one of the most common places where users need wired priority. It often assigns metrics automatically, and those automatic values can change when networks reconnect. The following methods give you more control.

Using Interface Metric Settings

The most user-friendly method is to set a manual interface metric for Ethernet and Wi-Fi. This tells Windows to prefer Ethernet when both are connected.

1. Open Settings and go to Network & Internet.
2. Select Advanced network settings.
3. Open More network adapter options.
4. Right-click your Ethernet adapter and choose Properties.
5. Select Internet Protocol Version 4 (TCP/IPv4), then click Properties.
6. Click Advanced.
7. Uncheck Automatic metric.
8. Set the interface metric for Ethernet to a low number, such as 10.
9. Repeat the process for Wi-Fi, but use a higher number, such as 50.
10. Repeat for IPv6 if your network uses IPv6.

After applying these settings, Windows should prefer the wired connection for default routing. You may need to disconnect and reconnect one or both adapters, or restart the computer, before the change is fully reflected.

Using PowerShell or Command Prompt

For administrators, scripts, or repeatable setups, PowerShell is faster. First, list your interfaces:

Get-NetIPInterface | Sort-Object InterfaceMetric

Then set metrics for Ethernet and Wi-Fi. Use the actual interface alias shown on your system:

Set-NetIPInterface -InterfaceAlias "Ethernet" -InterfaceMetric 10
Set-NetIPInterface -InterfaceAlias "Wi-Fi" -InterfaceMetric 50

If you prefer Command Prompt, you can use netsh:

netsh interface ipv4 set interface "Ethernet" metric=10
netsh interface ipv4 set interface "Wi-Fi" metric=50

These commands are useful when you manage multiple machines or want to document a standard configuration. Always verify the interface names first, because Windows may label adapters differently, especially with USB Ethernet docks or VPN virtual adapters.

Advanced Windows Network Binding

Older Windows versions exposed a “Bindings” order dialog, but modern Windows relies more heavily on interface metrics and routing. Still, in some enterprise environments, you may need to review virtual adapters from Hyper-V, Docker Desktop, WSL, or VPN clients. These adapters can create routes with unexpected metrics.

If Ethernet is configured correctly but traffic still uses Wi-Fi, inspect the routing table:

route print

Look for the default route, shown as 0.0.0.0. The interface with the lowest metric for that route should be Ethernet. If a VPN adapter has a lower metric, adjust the VPN client settings or disconnect the VPN temporarily to test.

How to Prioritize LAN Over Wi-Fi on macOS

macOS uses service order to decide which network interface is preferred. If Ethernet is listed above Wi-Fi, macOS should use the wired connection when it is active.

Changing Network Service Order

On modern macOS, the setting is usually found in System Settings:

1. Open System Settings.
2. Go to Network.
3. Click the action menu or More options button, depending on your macOS version.
4. Choose Set Service Order.
5. Drag Ethernet above Wi-Fi.
6. Click OK or Apply.

This method is simple and effective for most users. If Ethernet is connected and has a valid IP address, macOS should route default traffic through it.

Terminal Commands for macOS Network Priority

Administrators can use networksetup to manage service order. First, list services:

networksetup -listnetworkserviceorder

Then set the desired order. The exact command depends on your service names, but a typical example looks like this:

networksetup -ordernetworkservices "Ethernet" "Wi-Fi"

You may need to include additional services, such as VPN or Thunderbolt Ethernet, in the correct order. After making changes, verify with:

route get default

This shows the default gateway and interface. If the interface is your Ethernet adapter, the priority setup is working.

How to Prioritize LAN Over Wi-Fi on Linux

Linux gives you very granular control, but the exact steps depend on whether you use NetworkManager, systemd-networkd, netplan, or manual configuration. The common concept is the route metric: lower is preferred.

Using NetworkManager

NetworkManager is common on desktop Linux distributions. You can set route metrics for wired and wireless connections using nmcli:

nmcli connection modify "Wired connection 1" ipv4.route-metric 100
nmcli connection modify "Wi-Fi" ipv4.route-metric 600
nmcli connection up "Wired connection 1"
nmcli connection up "Wi-Fi"

For IPv6, set ipv6.route-metric as well. The exact connection names may differ, so list them first:

nmcli connection show

Some desktop environments also provide a GUI where you can set the metric under IPv4 or IPv6 settings. Look for a field labeled Route metric or Default route metric.

Route Metrics on Linux

To inspect the routing table, use:

ip route show

You may see something like:

default via 192.168.1.1 dev eth0 proto dhcp metric 100
default via 192.168.1.1 dev wlan0 proto dhcp metric 600

In this example, eth0 is preferred because its metric is lower. If both routes appear but the wrong one is used, check whether a VPN, container network, or policy routing rule is overriding the default table.

For persistent configuration, use netplan, systemd-networkd, or NetworkManager profiles rather than temporary ip route commands. Temporary routes disappear after reboot or network restart.

Router and Network-Level Considerations

A router cannot directly force your laptop to prefer Ethernet over Wi-Fi, because that decision happens on the client. However, network-level settings can still matter. If both interfaces connect to the same network, the router may see two IP addresses for one device. Some routers handle this gracefully, while others may log duplicate MAC or IP warnings.

You can improve the experience by:

• Using DHCP reservations for both Ethernet and Wi-Fi MAC addresses.
• Assigning clear hostnames, such as laptop-eth and laptop-wifi.
• Applying QoS rules to prioritize wired traffic if your router supports device-based policies.
• Disabling Wi-Fi on the client when Ethernet is the only intended path.

If your wired and wireless networks are on different VLANs or subnets, routing and firewall rules become more important. In that case, the client’s interface metric still matters, but DNS, split tunneling, and firewall policies may also determine which path is used.

Docking Stations, VPNs, and Special Cases

Docking stations can make wired priority more complicated because the Ethernet adapter may appear and disappear when you dock or undock. If the adapter name changes, your manual metric might not apply automatically. Use stable identifiers where possible, or configure the dock’s Ethernet profile to inherit the same metric.

VPNs are another common source of confusion. A VPN client may install a default route with a very low metric, causing all traffic to leave through the VPN interface even when you only wanted LAN priority. Check the VPN client’s split tunneling settings. If you want normal internet traffic to use Ethernet and only corporate resources to use the VPN, configure split tunneling accordingly.

Other special cases include:

• Hyper-V virtual switches on Windows.
• Docker and container networking.
• WSL virtual adapters.
• USB Ethernet adapters with generic drivers.
• Thunderbolt or USB-C docks.
• Multiple Wi-Fi profiles with different metrics.

When troubleshooting, simplify the environment. Disconnect VPNs, disable virtual adapters temporarily, and test with only Ethernet and Wi-Fi connected.

How to Verify LAN Is Actually Being Used

Changing a setting is only half the job. You should verify that the wired connection is actually carrying traffic. Here are reliable checks.

On Windows, run:

route print
ipconfig /all

Confirm that the default route points to the Ethernet interface and that the Ethernet adapter has a valid IP address.

On macOS, run:

route get default
ifconfig

On Linux, run:

ip route show
ip -br addr

You can also test at the application level. Visit an IP-checking website, run a speed test, or transfer a file to a local server. Then disconnect Ethernet briefly and observe whether the connection drops or switches to Wi-Fi. Reconnect Ethernet and confirm that traffic returns to the wired path.

For DNS, use tools such as nslookup, dig, or Resolve-DnsName. If DNS still resolves through Wi-Fi, your system may be using a Wi-Fi DNS server despite routing traffic over Ethernet.

Troubleshooting Common Issues

If your setup does not work as expected, the issue is usually one of the following:

• Automatic metric is still enabled: Windows may override your manual value after reconnecting.
• Wrong adapter name: Your script or GUI change may have targeted the wrong interface.
• IPv6 is not configured: Traffic may use IPv6 over Wi-Fi even if IPv4 uses Ethernet.
• VPN override: VPN routes can have lower metrics than Ethernet.
• Virtual adapters: Hyper-V, Docker, or WSL may create competing routes.
• Cached application sessions: Some apps keep using the interface they started on.
• Driver or firmware issues: Ethernet may report “connected” but fail to pass traffic.

A practical troubleshooting sequence is:

1. Disconnect Wi-Fi temporarily and confirm Ethernet works alone.
2. Reconnect Wi-Fi and check the routing table.
3. Restart the network service or reboot.
4. Clear temporary routes and test again.
5. Check VPN and virtual adapter routes.
6. Update network drivers and dock firmware.

Do not disable Wi-Fi permanently unless you truly do not need it. Keeping Wi-Fi available as a backup is often the best balance of performance and reliability.

Tips and Best Practices

The following practices make a wired priority setup more reliable:

• Use a clear metric gap, such as Ethernet 10 and Wi-Fi 50, rather than values that are too close.
• Configure both IPv4 and IPv6.
• Document your standard settings for each operating system.
• Test after operating system updates, because updates can reset network settings.
• Keep Ethernet drivers and dock firmware current.
• Use quality cables and ports; a bad cable can make Wi-Fi look “preferred” by failure.
• Verify with routing tables, not just speed tests.
• Use split tunneling carefully with VPNs.
• Avoid changing too many settings at once; test one change at a time.
• Keep Wi-Fi enabled for failover, but make Ethernet the primary path.

If you manage a team, consider creating a small internal checklist for wired priority. This reduces repeated support tickets and makes troubleshooting easier when a laptop moves between desks, docks, and meeting rooms.

Comparison Table: Wired Priority Methods

Platform	Primary Method	Typical Setting	Best For	Caution
Windows	Interface metric	Ethernet 10, Wi-Fi 50	Most users and admins	Automatic metric may reset after reconnect
macOS	Service order	Ethernet above Wi-Fi	Simple desktop setup	Service names must be correct in Terminal
Linux	Route metric	Ethernet 100, Wi-Fi 600	Advanced control	Persistence depends on network manager
Router or VPN	QoS and split tunneling	Prioritize wired device or VPN routes	Shared or managed networks	Cannot fully control client interface choice

Frequently Asked Questions

Will prioritizing LAN disable Wi-Fi?

No. In most setups, Wi-Fi remains connected and available. The operating system simply prefers Ethernet for default traffic. If Ethernet is unplugged, Wi-Fi can take over as a backup.

Can Ethernet and Wi-Fi connect to the same network?

Yes. Many devices connect to the same router through both interfaces. This is useful for redundancy, but it can create two IP addresses for one device. Use clear hostnames and DHCP reservations to keep things manageable.

Why does nothing change after I set the metric?

The most common reasons are that automatic metric is still enabled, the wrong adapter was changed, IPv6 is not configured, or a VPN has a lower route metric. Restart networking or reboot, then check the routing table.

What is the best metric value?

There is no universal best value. A common approach is Ethernet 10 and Wi-Fi 50 on Windows, or Ethernet 100 and Wi-Fi 600 on Linux. The important part is that Ethernet is lower and there is enough separation between values.

How does a VPN affect wired priority?

A VPN can install its own default route and override your normal interface priority. If this happens, adjust the VPN client’s split tunneling settings or temporarily disconnect the VPN while testing.

How do I know if LAN is actually being used?

Check the default route in your routing table and confirm it points to the Ethernet interface. You can also run a speed test, transfer a file, or use network monitoring tools to see which adapter carries the traffic.

Conclusion

If you came here wondering How to Prioritize Lan Over Wifi?, the short answer is to lower the metric or service order of Ethernet and raise the priority value of Wi-Fi, then verify the routing table. On Windows, use interface metrics or PowerShell. On macOS, use service order. On Linux, use route metrics through NetworkManager or your preferred network configuration system. For managed environments, also review VPNs, virtual adapters, and router-level policies.

A reliable setup is not just about making Ethernet “first” in a settings panel. It is about confirming that real traffic, DNS, and application sessions use the wired path. With the steps in this guide, you can create a stable, predictable wired priority configuration while keeping Wi-Fi available as a dependable backup.