On Wed, Aug 06, 2003 at 11:36:31AM +0200, Martin Husemann wrote:
> On Wed, Aug 06, 2003 at 09:56:28AM +0200, Manuel Bouyer wrote:
> > > The person said in the e-mail that the machine is running other stuff, and
> > > is swapping.
> > 
> > Yes, but it shouldn't affect NAT.
> 
> He also said emule clients. Those open *tons* of connections concurently,
> all needing NAT state. The number of sessions per client is to some degree
> configurable, but mostly not realy obvious.
> 
> On the NAT machine, do a "ipnat -l" some time when both clients are active.
> The list probably is *long*. I could imagine the NAT state (unswappable
> kernel memory) to eat up 32M.

No, I think he's just hitting the hard limit on NAT stats compiled in the
kernel, which is pretty low (I think it's 127)

--
Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
     NetBSD: 24 ans d'experience feront toujours la difference
--