Date: Sun, 16 Oct 2016 20:17:13 +0200 From: Marek Zarychta <zarychtam@plan-b.pwste.edu.pl> To: freebsd-net@freebsd.org Subject: pfr_update_stats: assertion failed. Message-ID: <20161016181713.GA95110@plan-b.pwste.edu.pl>
next in thread | raw e-mail | index | archive | help
--FCuugMFkClbJLl1L Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable The issue occurred first two years ago, after upgrade from 8 to 9 branch. Now this i386 machine is running 11.0-STABLE and despite it was compiled with "WITHOUT_ASSERT_DEBUG=3Dyes", still from time to time message buffer is fed with: pfr_update_stats: assertion failed. pfr_update_stats: assertion failed. pfr_update_stats: assertion failed. pfr_update_stats: assertion failed. pfr_update_stats: assertion failed. pfr_update_stats: assertion failed. pfr_update_stats: assertion failed. PF rules here are a bit complex, machine acts as a gateway for RFC-1918 networks and just does the job. pfctl -sr | wc -l 498 Any advice how to debug this or find triggering PF rule? =20 Why setting "WITHOUT_ASSERT_DEBUG=3Dyes" is ignored by PF code? --=20 Marek Zarychta --FCuugMFkClbJLl1L Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAABCAAGBQJYA8QlAAoJEHWf7P/9Uo0swawH/13xmfxh4S9NRtD7REdlWbR6 23x00UW0SjBshBG6Ex/Ly78yG5BDctVhxyOTnI6DZJDeczz14oUZrJGe/L0hoOWa orJrrZzekxTc15j4CGyjRFqX1SUVlrnc2FBL2z20gJ2bTl4RiJ35Y4E9lZvaZF6G oEgN5+fBHzaHIaCXje0XloLHXu9+AdnAExKxDjzF+OLivH10MmC7KuzOPnzp9FUf ZzRshy5+gTGB17qgabd5dcofQiG17x2j0icYEaXbe2TZ8twOSXGZ6I5Pu2hZCeoh b0e1gcTovydkQpj2je86Is4XEjj1oo/CcENEQ2QUJ7BZx6s4KdC7t1SGem3yyN0= =N0tI -----END PGP SIGNATURE----- --FCuugMFkClbJLl1L--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20161016181713.GA95110>