Closed xtaran closed 2 years ago
OK, time has come to think about this feature. Would it be enough to make this a just general setting or does it make sense to allow this per class?
Latest build from https://github.com/HenriWahl/dhcpy6d/releases/tag/latest comes with an exclude_interface option - can you please test like
exclude_interface = eth0
Would it be enough to make this a just general setting
Can innterface
be used per class?
But anyway, at least from my point of view, it suffices to be a general setting.
or does it make sense to allow this per class?
For me it does not make sense since this is a safety measure to never allow DHCPv6 on e.g. the upstream link of a router.
Latest build from https://github.com/HenriWahl/dhcpy6d/releases/tag/latest comes with an exclude_interface option - can you please test like
Will probably try it on a test device later today.
Thanks!
Yes, it just works as a general setting.
Added in documentation at https://dhcpy6d.de/documentation/config/general
I have two DHCPv6 servers which both have an onboard
eth0
interface and a second USB-basedenx<MAC address>
interface which is the one I'd like to run dhcpy6d on. I'd like to streamline bothdhcpy6d.conf
by making dhcpy6d listen on all interfaces buteth0
(which is the upstream link interface of the router).With dnsmasq this works easily like this (including the original explanatory comments in
dnsmasq.conf
):It would be nice if something like this would be possible with dhcpy6d as well.