OSMC should honor DHCP option classless-static-route

In a non-flat network it is imperative to use existing mechanisms for coherently distribution network configuration to the nodes.

Static routes for internal networks come in handy if using e.g. OpenVPN on machines and still wanting to access services in other internal networks.

Static routes are best distributed using DHCP, eg. option 121 (classless-static-route).

macOS honors this option, Linux does, even Windows!

Osmc should be no exception to this!
Sure, it is possible to make a local configuration, even using the openvpn config file. That is not the point here. This file would need to be updated every time when the Osmc box is moved to a different internal network. That is not suitable and not the response I am looking for.

Why not just use a dhcp client that honors the pertinent options?

This is better raised with the ConnMan developers to see if something is missing there.

That is extremely vague. There isn’t a unified network management solution for Linux and won’t be for the foreseeable future.

If you wish to install a different DHCP client you can do so, but it’s not something we would directly support.

I am an OSMC customer, I just care about the functionality. How it gets there?

Maybe you raise it with the ConnMan team? Or you replace ConnMan with something else?
Thats your decision.

Still, the functionality is requested for OSMC, because that is where I would like it.
Thank you for understanding.

If there’s sufficient demand for this feature, I will look in to how we can implement it.

Our goal is to provide enough networking for domestic use cases. For more complex scenarios, you could configure this yourself, but it would be out of our remit. The simplest solution would likely be to install dhclient

understood. thanks for considering the request.

A way to implement this is to have the router that has the default route know about all the static routes and have it reflect them back to clients. This causes only a tiny delay, as only the first packet destined for a subnet is delayed…after that, the client adds the route to their routing table and will send directly to the gateway for that subnet.

1 Like