WHY ARP has ip bouncing from device to another

[Patrick M. Hausen]

To outline this a bit more for 26.1 we will have a compact default setup using DHCP via Dnsmasq

Then why not also DNS via DNSmasq? Doesn't make sense to me. Also the reliability claim comes as a big surprise to me. But that's better discussed face to face over a beer ;-) If at all.

My point is: you are introducing dependencies on "a gazillion" external projects most of which have no strong ties to BSD and might at one point not even compile without patches on FreeBSD. That's a potentially huge integration workload so there better be a good reason for that.

Similarly why radvd - according to their own documentation a "Linux IPv6 Router Advertisement Daemon" - when rtadvd is built in right into FreeBSD?

[franco]

> Then why not also DNS via DNSmasq? Doesn't make sense to me. Also the reliability claim comes as a big surprise to me. But that's better discussed face to face over a beer ;-) If at all.

The blocklist in Unbound and other features make it more desirable than Dnsmasq for DNS, even for the defaults. Besides, *sense switched away from Dnsmasq DNS a long time ago for same or similar reasons that are still valid today.

> My point is: you are introducing dependencies on "a gazillion" external projects most of which have no strong ties to BSD

Dnsmasq was already in there. Kea is unavoidable. I think this is the problem with modern DHCP.  :)

> Similarly why radvd - according to their own documentation a "Linux IPv6 Router Advertisement Daemon" - when rtadvd is built in right into FreeBSD?

If it's already in there why not. It's been proven to work. They merged our code for FreeBSD integration in 2.20. ;)


Cheers,
Franco