Support for DHCP option 121 with dnsmasq

[wellsgz]

I am trying to push some classless route through DHCP option 121 w/ dnsmasq, but no luck to make it work.

At the mean time I do some sniffering and seems the option didn't even send by server side,

Here is the context I make at /jffs/configs/dnsmasq.conf.add

dhcp-option=lan,249,111.39.112.0/24,192.168.7.1

So the question is does DHCP option 121 being supported? If so, how should I configure it? If not, is it possible to add it to next release?

Appreciate your help.

 

[jernau]

Just tested this and adding the following added a classless route for me;

dhcp-option=lan,121,10.0.0.1/24,192.168.1.34

 

[john9527]

I am trying to push some classless route through DHCP option 121 w/ dnsmasq, but no luck to make it work.

At the mean time I do some sniffering and seems the option didn't even send by server side,

Here is the context I make at /jffs/configs/dnsmasq.conf.add

dhcp-option=lan,249,111.39.112.0/24,192.168.7.1

So the question is does DHCP option 121 being supported? If so, how should I configure it? If not, is it possible to add it to next release?

Appreciate your help.

Did you make a typo?

 

[wellsgz]

Both option 121 and 249 are used to push route other than default to client.

After some more test, I found the options are working well with dnsmadq in Merlin build, the problem resides on client side.

Windows could accept the option 121 correctly, while OSX, even the latest Yosemite will simply ignore the option.

And it seemed that the filter even happened at driver lever, that wireshark can't even see option 121 in the bootp packet.

Now I add a static route at start-up by scripting as a workaround for the issue, thank you for your advices