Date: Sat, 11 Aug 2012 11:56:03 +0200 From: Ian FREISLICH <ianf@clue.co.za> To: Gleb Smirnoff <glebius@FreeBSD.org> Cc: Garrett Cooper <yanegomi@gmail.com>, current@FreeBSD.org Subject: Re: Speaking of ship blockers for 9.... Message-ID: <E1T08QN-0000S9-H1@clue.co.za> In-Reply-To: <20120809114130.GC20560@FreeBSD.org> References: <20120809114130.GC20560@FreeBSD.org> <501D52AD.4010105@protected-networks.net> <CAFPOs6pPB1uLXALPwkVwFKyOLCw3%2Bx1vwW%2BCry9eBW7g04jy7w@mail.gmail.com> <CAGH67wTt295u0f_hewbKPxo63uDjtFL-9G3Gy_5yiur=7Nd4iQ@mail.gmail.com> <E1SyoLs-0000P8-UU@clue.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
Gleb Smirnoff wrote: > Let me give you link to my branch of pf: > > http://lists.freebsd.org/pipermail/freebsd-pf/2012-June/006643.html > http://lists.freebsd.org/pipermail/freebsd-pf/2012-June/006662.html > > In that branch the code that puts the "reverse" pointer on state keys, > as well as the m_addr_changed() function and the pf_compare_state_keys() > had been cut away. > > So, this exact bug definitely can't be reproduced there. However, others > may hide in :) Thanks. I'll be able to work on this next week. My system is pretty similar to yours - 16 cores, full BGP RIB, 20+ VLANs + CARP on 4*bce(4), PF+Sync, 400k+ states, NAT, tables, anchors etc. The complication is that the production system is on 8 and the pfsync is incompatible with 9 and CURRENT. And, 9/CURRENT is unuseable for me as a backup without this fix because of the state mismatch rate. Ian -- Ian Freislich
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1T08QN-0000S9-H1>