I did do a nap_map status when the ports were missing from pfSense and FS thought they were still open. I didn't know about nat_map republish, but will try next time. I think the timeframe is days, so this is kind of hard to diagnose. I may add a periodic nat_map republish from fs_cli to our production systems.
In any case, I'll keep an eye on it and try nat_map republish next time pfSense drops the ports to be sure that is working in this environment.
In the meantime, which .c file(s) can I peruse to learn more?
Thanks!
Troy
On Feb 9, 2010, at 3:07 AM, Rupa Schomaker wrote:
I believe FS opens the ports with an indefinite timeout (never close). I'd have to double check. In addition, FS refreshes the NAT mappings on every keep-alive packet sent by the upnp gateway. Have you done a nat_map status once the ports are missing in pfsense to see if fs still thinks the ports should be open? What if you do a nat_map republish? Do the maps get pushed to pfsense and then stay open for a whlie?
Perhaps pfsense is sending a keep-alive packet that we don't process right or is invalid? If so, I'd need a packet trace to do analysis.
--
-Rupa
_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org