Date: Wed, 7 May 2003 19:32:47 +0200 From: Clement Laforet <sheep.killer@cultdeadsheep.org> To: veedee@c7.campus.utcluj.ro Cc: anderson@centtech.com Subject: Re: NAT performance tweaks Message-ID: <20030507193247.6f60584f.sheep.killer@cultdeadsheep.org> In-Reply-To: <20030507170155.GA13015@c7.campus.utcluj.ro> References: <3EB67822.3070802@centtech.com> <20030505182756.093fb1c3.sheep.killer@cultdeadsheep.org> <3EB6A0BF.1040803@centtech.com> <20030506042044.GA84589@c7.campus.utcluj.ro> <3EB922B7.2080002@centtech.com> <20030507170155.GA13015@c7.campus.utcluj.ro>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Would certainly be nice to make it as a sysctl. It's a pain in the ass > to edit it manually everytime I cvsup. :/ Using a sysctl variable is a BAD idea for NAT table. If this variable is if it can be) modified, all the NAT table must be reinitialized, because of hash key. You should have a table size which minimizes hash collisions, and then avoids loops and/or hypothetical race conditions. clem
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030507193247.6f60584f.sheep.killer>