The timeout values for a nat session depend on the connection state and the type of connection. For example UDP and TCP are different and a successfully established TCP session has a larger timeout than TCP session that is still in the handshake phase.

Macavity wrote: The timeout values for a nat session depend on the connection state and the type of connection. For example UDP and TCP are different and a successfully established TCP session has a larger timeout than TCP session that is still in the handshake phase.

This is also a problem for me, I cant see current nat sessions because the list is full of old nat sessions that NEVER time out, or if they do they are not removed from the list.
Plus the list is only one page long and does not appear to be long enough to show all the nat sessions.
Only a router reboot can remove the phantom nat sessions


My Billion router shows the nat sessions and their current timeout status with multiple pages

from the release notes of firmware 3.3.1.2

"36. Improved: telnet command for flush nat portmaps; it maybe useful for some conditions portmapsetting –f"

I'm guessing but I don't think they would have introduced this if there weren't problems...

And yes I've had massive problems with it. Try a few torrent downloads and very quickly you can have thousands of NAT sessions hanging around. In my particular case once I get more than 4-5K sessions parts of the admin menus start disappearing

Update the latest firmware 3.3.2 fixes this issue