Date: Tue, 22 May 2018 15:15:10 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 206721] FreeBSDs DHCP client(dhclient) does not support the interface-mtu option(option 26). Message-ID: <bug-206721-7501-KjKxFl14hV@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-206721-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-206721-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206721 --- Comment #20 from Roman Bogorodskiy <novel@FreeBSD.org> --- (In reply to jimp from comment #19) Overall, I'd prefer the current behavior by default: there are environments where it's necessary to respect MTU value supplied by the (properly configu= red) DHCP server. So we basically either support properly configured DHCP server= s or add a workaround for misconfigured DHCP servers. I think it's better to sup= port proper configurations rather than trying to solve problems created elsewher= e. But loosing remote access because of that could be unfortunate indeed. I'm wondering how common is this type of misconfiguration? Maybe we can add a release note about that? --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-206721-7501-KjKxFl14hV>