In some email I received from Beers, James W., sie wrote: [...] > Since this only allows the age parameter for non-TCP settings, can you > suggest a way that I can boost the age for a TCP-based NAT session so that > the age can be greater than the default age?
Your application cannot be told to do some keep-alive type message at a frequency of less than 10 minutes over the TCP connection ? Another thing you might want to do is use map-block. This uses an algorithm that will result in the same NAT'ing every time, so that if a NAT session times out, a packet sent in the direction that caused the prior NAT mapping to be created will create another one the same (not restricted to SYN flags.) This will not work if the next packet sent comes from the destination of the connection, however. Darren
