RFC 3442 support, dhcp client classless static routes

Submitted by -
Status: New Idea


My ISP uses DHCP option 121 to send static routes to my router for ISP services.

As of today, this option is not supported in the DHCP client.

Adding it in the request line makes this line be ignored by the dhcp client :

interface "eth1.838" {
request subnet-mask, routers, ntp-servers, rfc3442-classless-static-routes;

 Then I've found a workaround to send the parameter like this :

option rfc3442-classless-static-routes code 121 = array of unsigned integer 8;

interface "eth1.838" {
        request subnet-mask, routers, ntp-servers, rfc3442-classless-static-routes;

So in the tcpdump, my request includes this option. No bugger.

But we still lack the routes handling, so I've added them by hand for now, but it'd be great to have the system handles them.

So I think we'd need a 

- get values on dhcp exit

- set them in routing table

- probably methods and rules to clean old rules etc...

From what I've searched, the exit hook script is available in debian wheezy (in /etc/dhcpd/dhclients-exit-hooks/ ), I've no clue about how the cleaning done.

This feature seems to be available in most EdgeOS competitors.

by Previous Employee UBNT-stig
on ‎05-01-2014 04:13 PM
The version will support a client-options field so you can do things like:
ubnt@wlb# show interfaces ethernet eth0
 address dhcp
 description WAN
 dhcp-options {
     client-option "send dhcp-client-identifier 1:2c:39:96:31:30:b0;"
     name-server no-update
 duplex auto
 speed auto
on ‎05-03-2014 06:28 AM

Thank you Stig.

My main concern was the routes integration, any chance to see this in a future update ? (I reckon this is not a priority, just wanted to add it somewhere in your todo list)

on ‎04-10-2016 06:45 AM



it seems it is not fixed in actual 1.8.0. I think it should not be a problem because Debian uses ist since years.


Or i am wrong???