How to set route specific interface metrics under Mac OS X
UPDATE: I found a great answer to part of my problem here https://superuser.com/a/525592/169461. I was able to set priority for interface en1 (wifi). However, this is not specific enough, since it will now route all traffic through en1. I need to be able to set the metrics specifically for a route to my gateway and for a route to my NAS. So if you know how to do this on a Mac, please let me know.
OLD TITLE: Optimize routing on a machine with two ways to reach the gateway
I am trying to optimize the response time between my iMac, a NAS and a cablemodem. The iMac is situated in my office and connected to the internet through wifi to router 1 at 192.168.0.1 (Technicolor cablemodem) located in the living room.
The difficulty here is that I have a NAS at 192.168.0.100, which I want to be reachable at all times. It is also situated in the office, so I connected it to the the internet using an old Linksys router (router 2) with DD-WRT on it, using it as a wireless bridge. The address of that router is 192.168.0.2. Of course having an extra router in the office I also connected the iMac and the NAS to it using cables. This all works fine. The NAS is reachable through router 2 on interface en0*. The wireless connection is on en1. Here is the relevant output of netstat -nr.
*UPDATE2: please note that upon request I posted the complete routing table again. This is after I reversed priorities of en0 and en1 (see the UPDATE above). So now the NAS is reached through en1 and the default gateway through en1 as well. The point is still the same, how can I make OSX use the fastest interface for each route?
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.0.1 UGSc 75 0 en1
default 192.168.0.1 UGScI 1 0 en0
127 127.0.0.1 UCS 0 0 lo0
127.0.0.1 127.0.0.1 UH 5 285 lo0
169.254 link#5 UCS 1 0 en1
169.254 link#4 UCSI 0 0 en0
169.254.179.33 0:10:95:de:ad:7 UHLSW 0 0 en1 1171
192.168.0 link#5 UCS 2 0 en1
192.168.0 link#4 UCSI 3 0 en0
192.168.0.1/32 link#5 UCS 1 0 en1
192.168.0.1 link#4 UHLWIir 1 0 en0
192.168.0.1/32 link#4 UCSI 1 0 en0
192.168.0.1 cc:35:40:eb:57:e3 UHLWIir 77 24 en1 1089
192.168.0.11/32 link#5 UCS 1 0 en1
192.168.0.11 4:54:53:f:5d:a7 UHLWI 0 1 en0 1090
192.168.0.11 4:54:53:f:5d:a7 UHLWIi 22 2046 lo0
192.168.0.100 0:90:a9:b6:3c:5a UHLWI 0 0 en0 1184
192.168.0.100 58:6d:8f:d7:d3:3e UHLWIi 3 63 en1 1184
192.168.0.101/32 link#4 UCS 0 0 en0
192.168.0.255 ff:ff:ff:ff:ff:ff UHLWbI 0 1 en0
192.168.0.255 ff:ff:ff:ff:ff:ff UHLWbI 0 4 en1
UPDATE3: As suggested in the comments I tried to add a static route that is very specific and it works sometimes, it is just not persisted by Mac OS X: sudo route add 192.168.0.100/32 -iface en0. Which leads to the following entry in the routing table:
192.168.0.100/32 3c:7:54:34:5a:4b ULSc 0 0 en0
Output of ifconfig:
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV>
ether 3c:07:54:34:5a:4b
inet6 fe80::3e07:54ff:fe34:5a4b%en0 prefixlen 64 scopeid 0x4
inet 192.168.0.101 netmask 0xffffff00 broadcast 192.168.0.255
nd6 options=1<PERFORMNUD>
media: autoselect (1000baseT <full-duplex,flow-control>)
status: active
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 04:54:53:0f:5d:a7
inet6 fe80::654:53ff:fe0f:5da7%en1 prefixlen 64 scopeid 0x5
inet 192.168.0.11 netmask 0xffffff00 broadcast 192.168.0.255
nd6 options=1<PERFORMNUD>
media: autoselect
status: active
Now I noticed that the network on the iMac sometimes is sluggish to respond and there seem to be hiccups in the connection. Using ping I found out that this is at least partly due to long response times. there is a huge variation in response times:
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=67.161 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=86.217 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=5.536 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=26.307 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=47.608 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=67.585 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=89.349 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=8.408 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=30.391 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=51.700 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=72.978 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=94.858 ms
And all that while traceroute says:
1 192.168.0.1 (192.168.0.1) 36 bytes to 192.168.0.101 88.989 ms 1.824 ms 1.705 ms
So I suspect that some of the packages for the internet gateway are routed through the (slower) wireless bridge of router 2 on en0 and some are routed through en1, which is fast enough. Obviously my next step was to try and set a static route to the gateway by executing:
sudo route add -host 192.168.0.1 -iface en1
Which I thought would force any connection to the gateway to go through the wireless interface at en1. No such luck however: when I do this, I lose internet connectivity on the iMac, which is not even restored when I change the route back.
I am not an expert at setting routes manually, so the question is: What am I doing wrong here and what do I have to do to get the iMac to route all traffic (except packages to 192.168.0.2 and 192.168.0.100) through en1?
I guess one way would be to define different subnets, but I still want every machine to be reachable from anywhere. Also I am not sure how I would go about that. Other hints on optimizing traffic would also be appreciated.
Solution 1:
The simplest solution to this doesn't involve having to define (and find a way to persist) static routes.
I would recommend that you use a different subnet (over the same physical network) for storage.
Turn off DHCP on
en0on your Mac and set it to have a static IP on this new subnet onen0, with no gateway defined on that interface. Say, for example, 192.168.1.1 with subnet mask 255.255.255.0.Give the NAS an IP on this subnet too. Say, for example, 192.168.1.2 with subnet mask 255.255.255.0.
Any other device on the network that needs to reach the NAS can also have an IP on this subnet and will be able to communicate with it. No special routing is necessary. It can even have two IP adresses, one on the 0.0 net and one on the 1.0 net, as long as only one of them has a gateway assigned.
Your Mac will now have one route to the gateway (
en1, Wi-Fi) and one route to the NAS (en0, Ethernet).