Date: Fri, 18 May 2018 15:24:55 +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-NYIWWtWXYl@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 jimp@pfsense.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jimp@pfsense.org --- Comment #10 from jimp@pfsense.org --- There does not appear to be a way to disable or override this behavior, even using supersede in the dhclient.conf doesn't let you turn it off or set an alternate value. My ISP sends a bogus MTU value of 576 which was ignored before, but now gets set and leads to major connectivity issues since the M= TU should be 1500. The link bounces when the MTU is set as well, at least on e1000. I see dhcl= ient was changed to help cope with that but it also affects other things that key off link up/down events. Any chance this can be reopened and the change backed out until it can be m= ade optional, perhaps by a command line parameter to dhclient? This will probab= ly impact a number of people unexpectedly on upgrade. --=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-NYIWWtWXYl>