Re: dhcp6leased, rdomains, and reject route

On 2026-06-04 17:59 +01, Tom Smyth <[email protected]> wrote:
> Hi, folks
> when we have been working with nsh and domains,
> each daemon has its own personality / instance config in each rdomain.
>
> one place where we have found problems is the DHCP server (which goes
> through all interfaces if I recall correctly) and sees that it doesnt have
> a valid config for a given interface and skips it...  (rather than checking
> the interface rdomain (if i recall correctly)
>
> I agree that Dhcpdleased or dhcpd6leasedshould not cross rdomain boundaries,
> if you have a routing domain with an interface(s) with dhcpleased,
> dhcpleased in that routing domain (should) be able to assign an new address
> and routes within the new rdomain,
>
> the trick of creating an instance of a daemon using symlinks and rcctl
> symlink flags, for each rdomain is quite elegant,  see url below,

This trickery is not needed for dhcpleased(8) and slaacd(8). Both are
rdomain aware and handle multiple interfaces in a single daemon. In fact
you cannot run multiple instances. The problem also does not apply to
dhcpleased(8), it receives a lease on one interface and it configures
that interface using the correct rdomain. there is no rdomain boundaries
crossing happening.

dhcp6leased(8) is a different beast. The whole point of it is to get a
lease on one interface (wan-side) and configure one or more *different*
interfaces (lan-side). Only then the question arises what it should do
if the wan-side and lan-side interfaces are in different rdomains.

Florian

-- 
In my defence, I have been left unsupervised.