I apologize for taking so long to respond. I implemented the change to the
MAP configuration in /etc/ipnat.conf, adding the age parameter. So my entry
looks like this:
map fxp1 10.168.0.0/16 -> 204.186.176.34/32 portmap tcp/udp 10000:60000 age
3600/3600
The problem still exists. If I monitor connections from the 10.168.1.0
subnet using ipnat -lv, it appears as if the age parameter is not being
utilized. Could this be happening because I have LARGE_NAT enabled? I do
not purport to be a coder, so please bear with me and correct me if I am
wrong.
When I look into ip_nat.c, I find the following lines of code in the
ip_natout function:
#ifdef LARGE_NAT
else if (nat->nat_age > fr_defnatage)
nat->nat_age = fr_defnatage;
#endif
It appears as if nat->nat_age is set to fr_defnatage, which is 10 minutes,
if LARGE_NAT is enabled. This also appears to be the behavior that is being
experienced.
Can I comment out the #ifdef block of code, recompile, and then see what
happens? What I hope to accomplish is to eliminate this check for LARGE_NAT
so that my age parameters take effect.
-jwb
-----Original Message-----
From: Darren Reed [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 12, 2003 6:17 AM
To: Dan Sopher
Cc: [EMAIL PROTECTED]
Subject: Re: IPNAT Age vs. IPFILTER Age
In some email I received from Dan Sopher, sie wrote:
> Where is this documented?
At least ipnat(5)
Darren
