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. On Mon, Feb 8, 2010 at 10:21 PM, Troy Anderson <troy@tlainvestments.com>wrote:
I have been using pfSense (1.2.3) and FS. FS nicely uses UPnP to poke holes in the firewall, but it seems that the holes close after a while. I cannot find any documentation in FS nor in pfSense as to what the timeout is. Is there a setting in FS to do some kind of keep-alive thing with UPnP to keep, e.g. 5060, open? Or is it already doing that and pfSense is the issue?
Thanks! _______________________________________________ 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
-- -Rupa