Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Simply put: does Mac OS X support RFC3442?

RFC3442 implements DHCP codes (121 and 249) to provide classless static routes to DHCP clients.

I can only seem to find rather old information circa 2005-2008 which implies that OS X does not support RFC3442. Any chance this has changed recently and I'm just doing something wrong while setting it up? My anecdotal testing seems to confirm that OS X does not support RFC3442 but I'm looking for confirmation.

If OS X still doesn't support RFC3442, what is an alternative method of pushing static routes to OS X clients?

share|improve this question
up vote 1 down vote accepted

Per, it should be possible to use ipconfig to get the values of arbitrary options from the most recent DHCP transaction. I presume you'd need to use a custom launchd plist to run something when the interface is (re)configured.

share|improve this answer
That workaround is definitely viable. I suppose the answer to the first questions is no, then? – rthomson Mar 18 '11 at 3:38
Right, this is a workaround. The linked article lists the RFCs it obeys, and 3442 wasn't one of them. But any decent DHCP client (admittedly this excludes at least some Solaris versions...) provides a mechanism to get at other DHCP options, because custom options are used fairly widely in larger shops. – geekosaur Mar 18 '11 at 3:43
Answer accept, friend. – rthomson Mar 18 '11 at 6:11
Using ipconfig with 10.7, the classless routing options are not shown. There seems to be no way to get them in the Mac. Or does the Mac only request certain options and the dhcp server only sends the requested ones? – mivk Jul 7 '13 at 18:28
DHCP is modelled on the client saying "give me this list of options" and the server only returning the values it has for that list of options. You can tell the server to forcibly include a parameter even when not included in the parameter request list. For ISC dhcpd, this might be done with option dhcp-parameter-request-list = concat(option dhcp-parameter-request-list, 79) to add 0x79 (121, CIDR route list) to the list. For dnsmasq, you'd specify the option with dhcp-option-force=... instead of dhcp-option=... – Phil P Apr 17 '15 at 22:37

Well, it looks like OSX 10.11 El Capitan supports it. Now my laptop catches the rule in our office and I no longer have to fix the routing table manually.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.