RE: IPNat Stops routing

Here is a copy of ipnat -s when it's not working and when it is. The PC has
128Mb of Ram. These ipnat -s shots were taken at a couple hours apart.

Not Working
vormund# ipnat -s
mapped in 64628 out 59329
added 1840 expired 1622
no memory 0 bad nat 61
inuse 218
rules 7
wilds 0

Working
vormund# ipnat -s
mapped in 91951 out 85523
added 3640 expired 3476
no memory 0 bad nat 61
inuse 26
rules 7
wilds 0

Thank-you very much for all the help.
Travis

-----Original Message-----
From: Ryan Beasley [mailto:ryanb@goddamnbastard.org]
Sent: Wednesday, July 02, 2003 3:02 AM
To: Travis
Cc: ipfilter@coombs.anu.edu.au
Subject: Re: IPNat Stops routing


On Wed, Jul 02, 2003 at 02:02:34AM -0400, Travis wrote:
> Well I took a look at the NAT table and I saw it make it to 218 inuse when
> it stopped. I ran ipnat -F and gave it a second then requested a website
off
> the local web server which was down and it now works. So the inuse queue
is
> getting full. Why and what would be a solution, other then login in and
> typing ipnat -F or making a script to do it every so often.

Unlike the state table, there's no compiled limit on the size of
the NAT table. You're limited only by the amount of memory available
to the kernel.

218 is a pretty low number; when you run ipnat -s, how high is the
'no memory' counter? How much RAM is in the machine?

--
ryan beasley <ryanb@goddamnbastard.org>
GPG ID: 0x16EFBD48