Date: Mon, 04 Nov 2019 03:57:29 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 241698] pfctl segmentation fault, weird "set skip" behavior Message-ID: <bug-241698-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241698 Bug ID: 241698 Summary: pfctl segmentation fault, weird "set skip" behavior Product: Base System Version: 12.0-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: darksoul@darkbsd.org I was running pf with the following line : set skip on lo Replacing it to : set skip on lo0 And then reloading configuration with the following command ends up causing= a segmentation fault and a core dump : # pfctl -f /etc/pf.conf The core dump reveals it occured in strncmp() but pfctl did not provide the base symbols so I can't be sure yet of what is going on. #0 0x000000080048c1d5 in strncmp () from /lib/libc.so.7 (gdb) bt #0 0x000000080048c1d5 in strncmp () from /lib/libc.so.7 #1 0x000000000021d7f0 in ?? () #2 0x0000000000220c6a in ?? () #3 0x0000000000222cbb in ?? () #4 0x000000000021d11b in ?? () #5 0x000000080026d000 in ?? () #6 0x0000000000000000 in ?? () It should also be noted that re-trying the command right after this works, = this time. Also, for some reason, I had to run pfctl twice to have traffic on the loopback interface processed properly. (This would prove to be nasty because DNS queries and traffic between jails would end up blocked...) As a workaround, I have now removed "set skip on lo" and gone for "pass qui= ck on lo0 no state". This has mitigated both issues (the pf segfault when rewriting pf.conf between lo and lo0, and traffic to lo0 being blocked) --=20 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-241698-227>