https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206721
--- Comment #21 from j...@pfsense.org --- (In reply to Roman Bogorodskiy from comment #20) I see it less as "a workaround for misconfigured DHCP servers" and more as preserving current expected behavior. I didn't even know my ISP DHCP server was sending broken information until this change was active by default. I'm not sure how many others are in the same boat, but having them find out after the fact during an upgrade seems troublesome. Ultimately, this is a new feature and not a bug fix. This new feature could potentially break current installations in unexpected ways (it certainly astonished me to find it broken). Preserving the existing and expected behavior is safe. If someone needs the new feature, IMO, they should have to make the change to activate it. It's a bit awkward that it has to be superseded to disable the change instead of going out of your way to enable it, but we're limited by what the dhclient configuration supports. If it were entirely up to me, I would leave it out of the default request list and supersede it to 0, and if someone wants to use the DHCP MTU they can add it to the request list and remove the supersede value. Since it is not up to me, having an entry in the release notes would be OK as an alternative as long as it's prominent. It may even warrant a HEADS UP to lists to call attention to it for wider testing before 11.2-RELEASE. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
