I have a bit of a convoluted network setup, with an openvpn host internally that I route traffic through for vpn clients, separate from the default gateway that sits at the edge. I have ISC's dhcpd set up to push the route for that out to clients, but udhcpc on Turnkey doesn't seem to honor the option.

The general structure is this:

Main subnet: 10.0.2.0/23, with 10.0.2.x for statically defined clients and 10.0.3.x for dynamic clients.

10.0.2.1 is the gateway, 10.0.2.4 & 5 are dhcp, 10.0.2.6 & 7 are dns, and 10.0.2.8 is the openvpn host.

The VPN host internally has 10.1.1.1, the vpn network is 10.1.1.0/24, and all vpn clients get routed out to the 10.0.2.0/23 network via 10.1.1.1.

All of my 10.0.2.0/23 clients get pushed a route for 10.1.1.0/24 via 10.0.2.8 as well as their default gateway via 10.0.2.1. On everything that actually uses that configuration, routing back and forth to the vpn clients works without any issues.

Some clients (Ubuntu primarily) ignore the 'routers' dhcp option when option 121 (classless static route) is set, so I'm actually pushing the default route twice, and Microsoft clients require their own dhcp option for pushing routes (249), so that's set as well (and appears to work without issue for them).

Turnkey, on the other hand (at least the fileserver package) ignores both options 121 and 249, but at least still accepts the routers option to set the default gateway.

Aside from setting the route statically on the fileserver, is there any way to get udhcpc to accept option 121 and configure the routes DHCP has already told it to use?

Thanks!

(edit: I should note, the turnkey fileserver host's a VM, not container, on top of proxmox, and pulls the rest of its network config just fine from DHCP, it only seems to ignore the provided routes)