Community-driven coverage of elementary OS — news, guides & forums
Dark abstract low-poly geometric landscape with layered triangular facets in deep navy, charcoal, and muted teal, illuminated by a soft electric-blue glow near the horizon

News roundups, tutorials, application guides, and forums — built by users, for users of the elegant Linux distribution.

elementary weekly
#20
Latest roundup · 18 Apr 2015
Freya Release
Final
Covered in weekly #19 & #20
Forum Topics
Active
Installation, customization & more

elementary OS NetworkManager Wi-Fi and Ethernet priorities

elementary OS's Network Manager, normally presented as NetworkManager, controls wired and wireless interfaces, saved profiles, IP addresses, DNS and routing. It runs as a background system service, so the desktop can present one simple network icon while the full connection configuration remains available through system settings and nmcli.

On a computer with both Wi-Fi and Ethernet, “preferred” can mean two separate choices: which profile should activate automatically, and which active interface should carry the default route. NetworkManager manages both decisions. Aligning them gives predictable behaviour without unplugging cables or repeatedly editing connections.

How NetworkManager makes connection choices

NetworkManager treats a physical interface, such as wlp2s0 or enp3s0, as a device and a saved set of credentials and addresses as a connection profile. Each Wi-Fi network and each wired arrangement can have its own profile, including autoconnect behaviour, DNS settings, routes and security details.

A device is simply the hardware connection available to the computer. A profile describes how NetworkManager should use that device, including whether to activate it automatically, which authentication to use and whether it should provide a default internet route. Keeping those ideas separate makes troubleshooting much easier.

When several profiles are eligible, NetworkManager considers their autoconnect order and its device-specific rules. An Ethernet lead in the wall does not by itself guarantee that internet traffic will follow Ethernet while Wi-Fi remains connected. The panel icon reports service state, not every routing decision, so two interfaces can appear connected while only one carries ordinary traffic.

Inspect saved profiles and live devices

In elementary OS, open Settings and choose Network to review active connections and create or edit profiles. Depending on the release and desktop layout, the connection editor sits behind the network status area. It exposes common options, while exact autoconnort and route fields may be easier to manage through nmcli.

Run nmcli connection show for saved profiles and nmcli device status for live devices. The first command displays names such as “Home Wi-Fi” and “Wired connection 1”. Those names are labels, so use the exact label displayed by your system when modifying a profile.

nmcli connection show --active shows which profiles NetworkManager believes are running. This is the best starting point for diagnosis, although it does not reveal which default route the kernel selected. Adding nmcli connection show "Home Wi-Fi" displays the complete settings for one profile, including its autoconnort priority, route metric and DNS configuration.

Set the autoconnort order

The connection.autoconnect-priority property controls the order in which eligible profiles are activated. Its behaviour can feel reversed: NetworkManager treats a lower numerical value as earlier in the activation queue. Give the wanted Ethernet profile 10 and the fallback Wi-Fi profile 100, for example.

After confirming the profile names, an Ethernet-first arrangement begins with nmcli connection modify "Home Ethernet" connection.autoconnect yes connection.autoconnect-priority 10. Set the fallback with nmcli connection modify "Home Wi-Fi" connection.autoconnect yes connection.autoconnect-priority 100. Reconnect or reactivate both profiles afterwards to test the ordering.

A value of 0 is often sufficient when no special ordering is needed, while higher values can place a fallback later. An unavailable SSID, missing cable or disabled “Connect automatically” option can still make an otherwise preferred profile impossible to activate. The connection editor is useful for checking those basic switches even when commands handle the precise priority values.

Control the default route with metrics

Autoconnect order determines what starts, but route metrics determine which path wins when both devices remain active. The lower ipv4.route-metric or ipv6.route-metric is preferred for otherwise equal routes. This is the key control when Ethernet and Wi-Fi lead towards different gateways.

For Ethernet-first traffic, run nmcli connection modify "Home Ethernet" ipv4.route-metric 10 ipv6.route-metric 10 and give the Wi-Fi profile a larger value, such as 100. Setting both address families prevents IPv6 traffic from taking a different path from IPv4. For Wi-Fi-first traffic, reverse those values: use 10 for the Wi-Fi profile and 100 for Ethernet.

Route metrics do not measure speed. Assigning 10 to a weak wireless link deliberately makes it win over a wired route with a larger metric. If the desired path should lose when it becomes unreliable, the profile needs a policy or connection sequence that responds to that change rather than relying on the metric alone.

To keep Wi-Fi connected for a local network while preventing it from carrying default internet traffic, add ipv4.never-default yes ipv6.never-default yes to the Wi-Fi profile. Use this only when another interface can provide the internet, since Wi-Fi will stop working as an automatic fallback. Custom routes can also override simple metric comparisons, so check the full route table when a profile behaves unexpectedly.

Configure Ethernet for Australian NBN services

Australian fixed-line services add a useful distinction between the access network and the home network. Depending on the address, NBN access can use FTTP, FTTN, FTTC, HFC or fixed wireless. An Ethernet wall socket may lead to a router, while the NBN Connection Box or optical network terminal may be positioned elsewhere in the building.

Retail providers including Telstra, Optus and Aussie Broadband sell services over infrastructure operated by NBN Co, with plan speed, contract and data conditions shaped by the provider and access type. Connecting by Ethernet to a Telstra Smart Wi-Fi or Optus gateway creates a wired local hop, but that gateway still shares its NBN uplink with the household's Wi-Fi clients.

Create a dedicated Ethernet profile for the wired LAN and apply the priority and metric settings described above. If the Ethernet port connects directly to a bridge or ONT instead of a router, the ISP may require bridge mode and particular addressing. Use the provider's settings rather than copying a generic profile, as a working home-router configuration will not necessarily suit a direct NBN connection.

Choose Wi-Fi when it makes more sense

Wi-Fi should lead when the cable is unavailable, the machine moves between locations or the wired port is slow. A nearby 5 GHz or Wi-Fi 6 access point can outperform an old Ethernet run, and a modern Australian home office may have its router in a better position than a wall jack.

Change the Wi-Fi profile to priority and metric 10 while moving Ethernet to 100 if that matches the intended path. Keep WPA2 or WPA3 security enabled, and select the intended SSID deliberately. A stronger preference for one saved network cannot repair a weak signal or congested channel.

Brick walls, concrete floors and long suburban yards often weaken Wi-Fi, whereas a wired run to a nearby desk remains predictable. In a flat in Melbourne or Sydney, a wall jack may belong to the building operator rather than the resident's router. Confirm the port's ownership, network isolation and address assignment before creating a profile, or an apparently preferred Ethernet link may bypass expected local services.

Mobile broadband can be useful where fixed wireless or NBN is the only fixed-line option. Australian plans vary: many fixed-line NBN products are uncapped, while some mobile and fixed-wireless offers include a data allowance. Those commercial differences do not alter NetworkManager's settings, but they influence whether tethering is a sensible routine backup.

Verify the route and recover from faults

Start with nmcli device status and ip route. Look for the default via line and compare its dev and metric values; the expected interface should have the lower metric. Repeat with ip -6 route when using IPv6, since a separate IPv6 default route can send some traffic elsewhere.

Test reachability with a small packet count, such as ping -c 4 1.1.1.1, and check name resolution separately with getent hosts linux.org. Some networks block ICMP, so a failed ping does not by itself prove that the gateway or DNS is broken. Compare the results before and after changing profiles.

For troubleshooting, journalctl -u NetworkManager -b --no-pager shows service events, while nmcli radio wifi off and nmcli radio wifi on can test whether stale wireless state is interfering. Reactivate an edited profile with nmcli connection up "Home Ethernet", then inspect the routes again.

If the fixed-line service is down, USB tethering from a phone can provide temporary access; an Android device guide can help prepare the handset for that role. Keep the USB option and a hotspot profile available, but check how corporate VPNs, DNS overrides and captive portals behave before they become the only route online.

Reliable prioritisation comes from separating activation order from route preference. Set the desired profile to activate earlier, give its routes the lower metric, and confirm the result in the live routing table rather than relying on an icon or a list of connected devices.

The lasting rule is simple: make the intended path win both when connections start and when the kernel chooses the default route, then verify IPv4 and IPv6.

Browse the News Archive
Latest Updates

From the elementary weekly series

Low-poly faceted abstract render in dark charcoal and electric blue tones, suggesting a news bulletin or announcement
elementary news

elementary weekly #20

The first week with the final Freya release — community reactions, tips, and early impressions gathered in one roundup.

Abstract low-poly geometric scene in midnight blue and soft cyan, conveying a live broadcast or event atmosphere
elementary news

elementary SPECIAL

A live Hangouts event with the elementary OS founders, held on 11 April 2015, discussing the Freya final release.

Low-poly faceted render in deep navy and muted teal with subtle amber highlights, suggesting a tutorial or guide
Tips and Tricks

Timeshift Guide

How to use Timeshift — the intuitive system restore utility for elementary OS — to recover from configuration mishaps.

Explore

Topics & Resources

Dive into guides, application recommendations, and community discussions covering every aspect of elementary OS.