Date: Wed, 5 Jul 2017 00:35:18 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: "Herbert J. Skuhra" <herbert@mailbox.org> Cc: freebsd-net@FreeBSD.org Subject: Re: [Bug 220351] Path MTU discovery works only after resetting an internal interface MTU (mpd5, ng_nat, ipfw) Message-ID: <595BD1D6.2040203@grosbein.net> In-Reply-To: <87eftytwbi.wl-herbert@mailbox.org> References: <bug-220351-2472@https.bugs.freebsd.org/bugzilla/> <bug-220351-2472-lCDWr8PCgb@https.bugs.freebsd.org/bugzilla/> <87r2xzaw30.wl-herbert@mailbox.org> <87bmp3x7eu.wl-herbert@mailbox.org> <59590064.1040700@grosbein.net> <87a84myitf.wl-herbert@mailbox.org> <59590FE6.7030109@grosbein.net> <878tk6ydwt.wl-herbert@mailbox.org> <87eftytwbi.wl-herbert@mailbox.org>
next in thread | previous in thread | raw e-mail | index | archive | help
03.07.2017 3:31, Herbert J. Skuhra wrote: >> Instead of enabling ipv6cp in mpd5 I've also tested with an IPv6 tunnel >> from HE... same issue. :-( > > Hmm, adding "mtu#1440" to /etc/rtadvd.conf apperently fixes these > issues. Makes sense? Perhaps, as temporary workaround. You could fill new IPv6-related PR on this.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?595BD1D6.2040203>