Thanks for your replies... In the last week or so I've been testing further...
Using the following items to slow/alleviate the otherwise randomness of ip's and port's been generated via my cgnat boundary nodes... APP - Address pooling paired EIM - Endpoint independent mapping EIF - Endpoint independent filtering (session-limit and outbound refresh are recommended) AMS Load balancing hash-key src-ip on my inside domain interface These combinations of options seems to cause a few nicer things to occur to help gaming and peer-to-peer and banking websites to work as they should. Let me know if you have seen similar issues and successes or failures with your cgnat deployment. -Aaron
