Date: Fri, 11 Dec 2015 19:58:06 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 205194] Changing MTU higher than 1500 on the interface pfsync0 causes panic Message-ID: <bug-205194-2472-aHkgS7EAPY@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-205194-2472@https.bugs.freebsd.org/bugzilla/> References: <bug-205194-2472@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=205194 --- Comment #1 from Kristof Provost <kp@freebsd.org> --- I've had a quick look at this, and imagine my surprise when it turned out to not actually be a PF bug. Briefly, the pfsync interface doesn't have any ip6 data associated with it, while the netinet6 code assumes it to be present. We panic because of the call to nd6_setmtu(ifp); in the SIOCSIFMTU ioctl() handler. We just need to check if ip6 is active on the interface before we try to do anything with it. There's an open review in: https://reviews.freebsd.org/D4522 -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-205194-2472-aHkgS7EAPY>