Question: Q: How do I add a static route (permanent) to Yosemite?
In previous Mac OS X releases, I was able to add a permanent static route to my system, following this article:
Based on some research, here’s a way to add permanent static routes to Mac OS X Lion (and problably other OS Xs too).
The principe is that we create a bash script which is run on every boot and sets static routes.
First of all, you have to be a local admin.
Open a terminal and change to the StartupItems directory
Then create a new directory with root priviledges, e.g. AddRoutes and change into it
sudo mkdir ./AddRoutes cd ./AddRoutes
Now you have to create and edit the bash script
sudo touch ./AddRoutes sudo nano ./AddRoutes
Paste the following Lines into the bash script and adapt it for your network
When you finished with the script, save it.
Then create the corresponding plist.
sudo touch StartupParameters.plist sudo nano StartupParameters.plist
When you created the plist file, paste the following lines into it.
When you finished the plist file, save it.
Finally we have to set the access rights
sudo chmod 755 /Library/StartupItems/AddRoutes/*
At the end we have to reboot and now your permanent static routes are set.
You can verify with the following
But now with Yosemite, this doesn’t working. Especially the point when executed this line in the :
in the startup script. Something has been changed in the latest OS. Any ideas, how to solve this OR another way to add a permanent static route?
Mac Pro, OS X Yosemite (10.10)
Posted on Oct 30, 2014 11:33 AM
Helpful answers
In a nutshell. I’d create a LaunchDaemon plist file that invokes a shell script containing
your list of «sudo /sbin/route add » commands. I’d place this plist file in
then, I’d either reboot to test or run
sudo launchctl load
command to tell launchd about the new plist file
If all this seems familiar, great — if not you have some reading to do.
Oct 30, 2014 1:48 PM
Startup Items have been deprecated for many years, and may not work at all in Yosemite.
Oct 30, 2014 8:24 PM
There’s more to the conversation
Loading page content
Page content loaded
I have not done what you request. However, if I were you I’d start by reading up on «Launch Daemons and Agents»
Oct 30, 2014 1:29 PM
In a nutshell. I’d create a LaunchDaemon plist file that invokes a shell script containing
your list of «sudo /sbin/route add » commands. I’d place this plist file in
then, I’d either reboot to test or run
sudo launchctl load
command to tell launchd about the new plist file
If all this seems familiar, great — if not you have some reading to do.
Oct 30, 2014 1:48 PM
Startup Items have been deprecated for many years, and may not work at all in Yosemite.
Oct 30, 2014 8:24 PM
Can someone show me an example off a LaunchDaemon plist file for adding permanently add static routes?
Mar 13, 2015 1:35 AM
is there some other method? like for 10.9 system with rc.local file?
Jul 13, 2015 2:33 AM
Copy this file to /Library/LaunchDaemons/local.username.routes.plist
The 10.1.1.0/24 is the network you want routed, and the 192.168.1.1 is the gateway you will use (usually a second NIC without an existing gateway).
Load the new plist.
$ sudo launchctl load local.username.routes
Start the new plist without rebooting.
$ sudo launchctl start local.username.routes
Prove your normal traffic is unaffected (should return your normal gateway).
Prove your static route is working (should return the gateway you entered above).
$ route get 10.1.1.100
Nov 20, 2015 4:57 PM
So, I’m in the situation where I would like the route to be present the instant the user logs in. I have my plist file:
and I put it in /Library/LaunchDaemons and rebooted. I sat at the machine, and the moment the login window appears, I logged in, opened a terminal, issued the netstat -nr command and did not see the route. I repeatedly issued netstat -nr and waited about a minute before the route appeared.
So I tried moving it to /Library/LaunchAgents, thinking that maybe it would load quicker. and it does load a little quicker, but not significantly quicker.
I need this route to be active the INSTANT a user logs on. And the user may not be an admin, so a login script with sudo won’t work. Any ideas on how to flag the script as high-priority and get it to execute in a more timely fashion?
Dec 3, 2015 9:57 AM
Question: Q: How do I add a static route (permanent) to Yosemite? More Less
Источник
A permanent static route for Macintosh OS X (10.4.7)
I have set up OpenVPN on our pribvate network, but our special setup requires manually adding a static entry to the routing table of computers that we want to access from the outside via our VPN server. In SuSE Linux this is a nobrainer as Yast provides a section where to add static routing information. On MacOS X the command line works, but upon reboot the route is lost:
route add 10.8.0.0/24 192.168.0.2
Check what the route is for a specific IP:
route get 10.8.0.1
The same command has a different syntax on Linux though:
route add -net 10.8.0.0 netmask 255.255.255.0 gw 192.16
8.0.2
In order to preserve the routing information over a reboot I created the folder AddRoutes in /Library/StartupItems. Inside this folder there have to be two files: AddRoutes and StartupParameters.plist . The content of these files is the following:
AddRoutes:
#!/bin/sh
# Set up static routing tables
. /etc/rc.common
StartService ()
<
ConsoleMessage «Adding Static Routing Tables»
route add -net 10.8.0.0/24 192.168.0.2
>
StopService ()
<
return 0
>
RestartService ()
<
return 0
>
RunService «$1»
StartupParameters.plist:
<
Description = «Add static routing tables»;
Provides = («AddRoutes»);
Requires = («Network»);
OrderPreference = «None»;
>
These files need to be readable and executable by everybody for MacOS X 10.4.7. However, MacOSX might wipe these files with each system upgrade (at least from Mountain Lion to Mavericks my settings disappeared completely). After recreating them, I got the error message «Insecure Startup Item disabled» at boot and I needed to give the directory and the files the following permissions to make the error to disappear:
drwxr-xr-x 4 root wheel 136 Aug 6 22:44 AddRoutes
-rwxr-xr-x 1 root wheel 238 Aug 6 22:43 AddRoutes
-rwxr-xr-x 1 root wheel 123 Aug 6 22:44 StartupParameters.plist
However, the route does not get added in Mavericks by this procedure and I could not find any information how to do this.
Источник
HOWTO quickly add a route in Mac OSX
Adding a route manually can be necessary sometimes. When on Linux, I know the command by head:
On the Mac the command is similar, but a bit different 🙂 Just as a note to myself and anyone else interested:
This sets up a route to the 10.67.0.0/16 net through gateway 192.168.120.254. First one on Linux, second one on Mac OSX.
Rate this:
Share this:
Like this:
Related
26 responses to HOWTO quickly add a route in Mac OSX
Hi
I have connected my Mac to a Linux box directly using a cable (no home router involved).
In Mac, I am setting a static IP address to 10.10.11.13 with subnet mask 255.255.255.0 and in Linux 10.10.11.16 with same mask. My Mac has two NICs (2nd one is connected to router and WWW). How can I add a route in Mac so all the traffic intended for the Linux box goes through first NIC? I am interested in waking the Linux machine up using something like:
$ wakeonlan -i 10.10.11.16 00:AA:BB:XX:XX
Is this routing possible?
Since you have the Mac and the Linux box in the same subnet (10.10.11.x) and have a subnet of /24 you do not need a route to be able to talk to each other. The mac wil automatically use the correct interface due to the netmask being used.
If you have a specific error message, please post it and I will have a look. From the info I have now I’d say this just works. The first thing that comes to mind when you’d encounter a problem is the cable connection. Did you use a cross-cable? Are the LEDs turned on?
My mac mini is connected to the web through wifi (192.168.17.x). I don’t have control over the wifi net. I started playing with a router and connected it to the wired interface en0. I have a hard time connecting to 192.168.1.1 which is the routers default address. I set en0 manually to 192.168.1.10. I tried adding a route, but no go. Can you help?
Did you already solve this issue? It does sound like a routing or netmask issue. If you tell a little more I might be able to help.
Hi Remi, I have the exact same basic question as Hamid although for a different purpose, i.e. How to route traffic destined for a specific ip through a specific interface when everything is on the same subnet. In my case I would like to use my mac’s wifi interface to connect to a network share as it is faster than using an ethernet cable for file transfers, but keep the rest of the traffic prioritised according to the order the interfaces are listed in Network system preferences.
I forgot to mention that I would like to be able to fallback to the ethernet interface if the wifi interface is disabled, thanks.
I figured that you can do this with an ip address using ‘sudo route add -host 192.168.1.2 -interface en1’ but that doesn’t work as the network share is accessed using it’s hostname myshare.local. Trying to route add -host myshare.local does not seem to work as although netstat -r shows a single entry for 192.168.1.2 assigned to en1, myshare.local only has an entry assigned to en0 😦
Hi Leo,
Connecting to the same network multiple times, with the same ip addressing is confusing the OS and might give mixed results. The quick and dirty way to solve this, is to add another ip address to your server (say 10.0.0.1) and one to your wifi interface (say 10.0.0.2) and have the two communicate using the 10.0.0.0/24 network. That will assure the routing is correct. You can use the same interface cards and same wires. Just add these as alias ip addresses and you’ll be fine.
Nice of you to share your knowledge, I have had something that’s been a consistent problem along the lines of this post that I’m hoping you have a suggestion about.
I have two networks:
a gigabit ethernet video editing network on a 192.168.1.x network (direct network, no outside connection)
our standard corporate network on 10.130.x.x.
Two Mac Pro’s have the network service order setup with the corporate network interface first (en1:DHCP) and the media network second (en0: 192.168.1.5 and 192.168.1.6). If I don’t put them in this order the internet doesn’t seem to work.
The media server is also a Mac Pro with the en0 (192.168.1.2) and en1 (10.130.178.90) similarly setup.
About 40% of the time the Mac Pros would connect to the media network over the slower 10.130 network… we figured out that if we used a GUI app called WaterRoof we could inject an ipfw command into the Mac Pros that blocks any connection to the media server on the corporate network (10.130.178.90).
This worked great for a while, then suddenly today, the video started playing choppy again and I ended up having to disable the media server’s en1 to the corporate network to force the connection over the 192.168 network. Don’t know how it found it’s away around the IP block (perhaps connecting by share name ?) but I was wondering if creating a route would be a better answer… could you show me the syntax for that…
do I need to do it on the Mac Pros AND the media server? Do I need to save it in some file for it to be permanent?
Any help would be HUGELY appreciated!
Interesting case! You could indeed add a route, so that even the corporate ip address will be reachable over the gigabit network.
Try this on the Mac PRO’s:
sudo route -n add -net 10.130.178.90/32 192.168.1.2
And reversed on the Media server:
sudo route -n add -net 10.130.178.x/32 192.168.1.5
sudo route -n add -net 10.130.178.y/32 192.168.1.6
netstat -nr gives an overview of current routes.
This should make the Media server’s corporate ip address reachable through the gigabit network and vice versa.
Hope this helps 🙂
Hi, This only works until you reboot the machine. Then the route is lost.
My office has restricted access to Internet sites such as Skype & Dropbox. I also have access to an unrestricted Wi-Fi.
The laptop is connected to both access points. Now my problem is, when en0 (ethernet) is my preferred channel then blocked sites like Skype won’t work though I have an active Wi-Fi connection. If I change the preferred channel to en1 (Wi-Fi) then Skype works but I cannot browse any of the company Intranet sites.
Why does the fallback to Wi-Fior visa versa does not work?
Here are my routing table entries using command netstat -nr:
$ netstat -nr
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 192.168.2.1 UGSc 23 0 en1
default 172.16.8.1 UGScI 0 0 en0
default link#6 UCSI 1 0 en3
default link#8 UCSI 1 0 en14
127 127.0.0.1 UCS 0 0 lo0
127.0.0.1 127.0.0.1 UH 3 151425 lo0
169.254/30 link#6 UC 0 0 en3
169.254 link#11 UCS 3 0 en1
169.254 link#5 UCSI 0 0 en0
169.254 link#6 UCSI 1 0 en3
169.254 link#8 UCSI 1 0 en14
169.254.0.1 36:bb:1f:5:b7:d6 UHLSW 1 498 en3 889
169.254.0.2/32 link#6 UCS 0 0 en3
169.254.0.4/30 link#8 UCS 0 0 en14
169.254.0.5 96:eb:cd:3:8f:e4 UHLSW 5 38380 en14 325
169.254.0.6/32 link#8 UCS 0 0 en14
169.254.1.1 link#11 UHRLSW 0 16 en1
169.254.1.5 link#11 UHRLSW 0 8 en1
169.254.81.175 0:26:b9:9e:c6:e3 UHLSW 0 0 en0 1193
172.16.8/23 link#5 UCS 2 0 en0
172.16.8.1/32 link#5 UCS 1 0 en0
172.16.8.1 68:5:ca:10:18:5 UHLWIir 1 0 en0 1073
172.16.8.225 c:4d:e9:c3:51:8c UHLWI 0 0 en0 1190
172.16.9.233/32 link#5 UCS 1 0 en0
172.16.9.233 0:25:0:a4:fa:de UHLWI 0 1 lo0
192.168.2 link#11 UCS 1 0 en1
192.168.2.1/32 link#11 UCS 2 0 en1
192.168.2.1 74:31:70:6f:c6:58 UHLWIir 26 224 en1 1160
192.168.2.103 44:d8:84:8:85:e2 UHLWI 0 0 en1 692
192.168.2.104/32 link#11 UCS 1 0 en1
192.168.2.104 0:23:6c:97:46:a3 UHLWI 0 1 lo0
239.255.255.250 1:0:5e:7f:ff:fa UHmLWI 0 5 en3
239.255.255.250 1:0:5e:7f:ff:fa UHmLWI 0 19 en14
Источник
