My problem involves a High Sierra Mac Pro, a NAS and an old house. Things are like this: Mac Pro and NAS sit close together, and are connected via bonded Ethernet through a switch allowing for ultra-fast transfer speed between the two.

Being in an old house, the switch itself is connected to the main router only via a PowerLine interface. While this actually brings web surfing to the Mac Pro's Ethernet, the truth is that for this purpose only WiFi is way faster (about 10x).

For the sake of this example let's assume the web router is, Mac is and NAS is; wifi is en2 and ethernet is bond0. I need my Mac to route all traffic through en2, except for traffic directed to which should go through bond0 only.

I tried moving Ethernet on top of service order stack and removing its IPV4 Gateway, but my Mac still keeps connecting to the NAS via WiFi even though Ethernet comes first.

I understand I would need some kind of static route to do this, but after reading a lot of (contradictory) posts I'm still not sure how to exactly accomplish this...

Can someone help me? What sort of code should I type in Terminal to create this static route and make sure it's still there after reboot?

Thank you.

  • There’s a few ways to skin this cat, by a couple of questions. Does your NAS need Internet access? Are there other users that need to access the NAS from the network? What brand NAS? The “best” answer will likely be “Apple agnostic” and more appropriate on another site, but let’s work it anyway so we can get you a solution
    – Allan
    Commented May 8, 2020 at 18:00
  • Hi @Allan, yes, my NAS requires internet access to enable remote backups, and I need others in the net to reach it (I'd prefer to keep everything under the same subnet, if possible). The NAS itself is a Synology. Commented May 10, 2020 at 14:29
  • See my answer. Already addressed and even provided a diagram.
    – Allan
    Commented May 10, 2020 at 14:37

2 Answers 2


I tried moving Ethernet on top of service order stack and removing its IPV4 Gateway, but my Mac still keeps connecting to the NAS via WiFi even though Ethernet comes first.

Service order priority is great for different networks (i.e. home and work via VPN or work network and lab network). If you're multi-homing to the same network (WiFi and Ethernet both connect to home), the priority doesn't matter. Routes are determined by what gets advertised first, the least amount of latency, etc. As you said, your WiFi is about 10x faster; it makes sense that the traffic will try to go through what it thinks is the fastest.

Set a static route for the host

You can set a static route for an individual host and ensure that all traffic bound for that host goes through a particular interface (gateway). The route command takes the following syntax:

% sudo route add -host <target host IP> <IP of network adapter>

So, in your case, using 0.3 as the NAS and 0.55 as your bonded interface, it would be as follows:

% sudo route add -host

All traffic would be to that one host (NAS) would be routed though the bonded interface while everything else would go through WiFi.

The problem with this is that it's only temporary. You'll need to rerun this command every time you boot and quite possibly can get overridden (see next section). To automate it, you'll need to put this into a script (call it setroute.sh for example) and have it executed with launchd. See the following posts on how to accomplish this:

Create a different subnet

This is my preferred solution because the NAS will be on it's own network isolated from the rest of the traffic by default. You won't have to tell it where to go or what traffic to prioritize because it will already know that. In addition RIP (Route Information Protocol) advertising packets can't override any static routes you may have put in. Yes, your router can tell your Mac how to get to hosts automatically and this may conflict with what you want.

enter image description here

WiFi Network ->   ← 254 hosts max
NAS Network  ->   ← 6 hosts max

So, on your Mac, you'll have two network connections: (WiFi) and (Bonded Connection) to the switch (or directly to the NAS). The NAS,, will have it's connection to the same Ethernet switch that your Mac is connected to. All traffic destined for the NAS will have no choice but to go through the bonded Ethernet while all other traffic will go via WiFi.

  • Hi @Allan, I passed the last few days trying to wrap your answer into a viable solution. I can CONFIRM the sudo route add -host [destination IP] [interface IP] command works just fine per se. I still can't find a way to have it executed at startup. I tried with a .sh script which gets executed as expected, but the route doesn't appear. If I execute the .sh script manually, there it is inside the routing table. I'm banging my head into the wall :-D Commented May 14, 2020 at 15:51
  • How are you running it? LaunchDaemon or LaunchAgent? Its possible, networking isn't up yet
    – Allan
    Commented May 15, 2020 at 4:23
  • Launch agent via plist. As to your suggestion, the script tests and echoes the interfaces' status, and interfaces are up. Moreover, the script itself is executed every 30secs or so: the logging works (so I can check that the script is actually executed even after login), it's only the "route add" line that doesn't. Until I fire it manually, in which case it works (so the syntax is correct). Maybe it has to do with permissions? Commented May 15, 2020 at 6:46
  • Post the script and plist to pastebin so I can see what it’s doing.
    – Allan
    Commented May 15, 2020 at 9:41
  • Script file is here: pastebin.com/Cfheu4zq . The script resides in /usr/local/bin/ and has the following permissions as per ls -l: -rwxr-xr-x 1 root wheel 618 14 Mag 17:45 static-routes.sh. The plist file is here: pastebin.com/6HaTdVbX . The plist resides in /Library/LaunchAgents/ Commented May 15, 2020 at 11:49

TL;DR: if your static route doesn't work, but you have Wifi+Ethernet on your Mac, and 2 Ethernet ports on your NAS, you can configure one port on the NAS and the Ethernet port of your Mac to be on a different subnet than your wifi/router one (192.168.100.x vs 192.168.0.x: it doesn't really matter as long as they're different). The second port of your NAS can still be connected to the router via DHCP, to ensure remote sync processes keep working.

Ok everyone, this is for future reference for people in my same situation (a Mac with at least one Ethernet port and WiFi + a NAS with two ethernet ports).

One way you could accomplish the task of routing all traffic towards the NAS through one specific interface (in my case, Ethernet) and all the rest through WiFi could be as follows:

On the MAC:

  1. Configure WiFi for web surfing (usually, DHCP or a static address inside the router subnet). E.g.: if your router is, your Mac's WiFi card could be assigned Subnet mask will be, and obviously the Gateway will be your router's address.
  2. Turn DHCP off for your Ethernet port and manually configure its address inside a different subnet from the one where the router is. E.g.: you could set it to -say-, subnet mask always, leave "Gateway" blank (and check that DNS too is blank).
  3. Make sure the Ethernet addresses are advertised first by placing Ethernet on top of WiFi in the Services Order panel (click the gear button below the network services)

Link your Mac to your NAS via a cable (or through a switch), and let's set the NAS this way: (remember that for this to work the NAS has to have two Ethernet ports, not one)

  1. Link one of the NAS Ethernet ports to your WAN network (the one with internet access). Set this interface as DHCP in the Network settings of the NAS. This will assign the NAS and address in the same pool of the router, and the Mac's (let's say
  2. Link the second Ethernet interface to your Mac's Ethernet, directly or via a switch (note that both connections coming from the NAS can run through the same switch and still work)
  3. In your NAS' control panel turn DHCP off for this second interface (you don't want the router to talk to it!) and manually configure it to another address in the same pool of your Mac's Ethernet IP. In this example, it could be, Subnet mask, Gateway (your Mac's address).

YMMV depending on your NAS, or on your Mac's OS, but as far as I'm concerned I can testify that now on my MacOs 10.13.6 all "standard" traffic is correctly routed through WiFi, while the NAS (and the NAS only) is receiving full-speed traffic directly from the Ethernet connection.

This trick has one "downside", in that it will project not one but two NAS instances on the network (one is 192.168.0.x, the other 192.168.100.x), so obviously you'll have to make sure that you instruct your Finder to see the "correct" (Ethernet) NAS. If you keep addressing the other IP, its traffic will still be routed through WiFi. As to the management console (usually reachable via web browser), it will keep working flawlessly on both addresses.

This is only one possible solution. The other route (no pun intended), via script + static route, would possibly be more elegant and streamlined, but it requires some scripting and it's seemingly harder to achieve. I'll post it anyway as soon as I'll get it to work.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .