'outbound_interface' support for DHCP6 server?
Some initial questions
- Are you sure your feature is not already implemented in the latest Kea version? Yes.
- Are you sure what you would like to do is not possible using some other mechanisms? It is possible, but inconvenient and inconsistent.
- Have you discussed your idea on kea-users or kea-dev mailing lists? No.
Is your feature request related to a problem? Please describe. I have a pair of Kea DHCP servers without direct connection to the clients (they receive all requests via relay). The machines have a 'transport' interface that is used to route traffic to the rest of the network, but is not the address used for services. The service interface is a 'dummy' interface, and that is the interface configured in the server config files. In spite of that, the server believes that requests are received on the 'transport' interface even though it is only bound to the 'mgmt' interface.
In the DHCP4 server, I can set outbound_interface
to use-routing
so that replies can be sent out without having a socket open on the 'transport' interface.
Describe the solution you'd like
In the DHCP6 server, support the same outbound_interface
mechanism as the DHCP4 server supports.
Describe alternatives you've considered If I also bind the server to the 'transport' interface, the server can send replies. That is my current configuration.
Additional context I am using Kea 2.0.1, but have checked the docs for 2.1.2 and the code in the repo and this feature is not available in the DHCP6 server.
Funding its development Kea is run by ISC, which is a small non-profit organization without any government funding or any permanent sponsorship organizations. Are you able and willing to participate financially in the development costs? Possibly.
Participating in development Are you willing to participate in the feature development? ISC team always tries to make a feature as generic as possible, so it can be used in wide variety of situations. That means the proposed solution may be a bit different that you initially thought. Are you willing to take part in the design discussions? Are you willing to test an unreleased engineering code? Yes to all.