On Wed, Feb 16, 2022 at 11:05 PM Simon Kelley <si...@thekelleys.org.uk> wrote: > On 16/02/2022 20:19, Martin-Éric Racine wrote: > > The startup message DOES suggest that DHCP is bound to an exclusive > > interface, not to wildcard. This is misleading. > > No it's not. it calls setsockopt(SO_BINDTODEVICE) which binds the socket > to the physical interface, instead of to a IP address.
Ah. > > Meanwhile TFTP is not meant to appear on loopback. > > Why? I guess we could argue the 15-year old design decision to do that, > but it would be pointless since I'm not going to change it now and risk > breaking installations which rely on it. Fair enough. Mind you, if I add the interface specification as follow, it does what I need: enable-tftp=br0 Then TFTP indeed only is available on the IP for br0. Nontheless, I still think that since interfaces=br0 is already specified, it should have sufficed to ensure that all services are only available on that interface (plus DNS also being available on loopback, since this is an explicit exception stated in the documentation). Anyhow, feel free to close this bug if you don't think that any code or documentation change is required. Martin-Éric
