I've no idea - but I'm sure if you read the thread and RTFM on FreeSwitch you'll find out ;)

looks like its generated in /etc/sshd um, whats the policy for modifying system files manually? Obviously you must loose the changes when you upgrade. Do I just keep a list and fix it again after I upgrade? –-sorry, that's off topic, don't answer that :)

Thanks, I'll see if I can get something working with "dup-to". Nancy

Seems like a pretty convoluted way to get things done when split-dns would handle it better… http://doc.pfsense.org/index.php/Why_can%27t_I_access_forwarded_ports_on_my_WAN_IP_from_my_LAN/OPTx_networks%3F

You'll have to make some minor code changes to be able to assign lagg interfaces. The creation and setup of lagg can be hacked in manually.

You can also disable filtering entirely from the command line with a 'pfctl -d'.  Alternately, we leave the loaded ruleset in /tmp/rules.debug, feel free to edit it to fix your connectivity issue and reload with pfctl -f /tmp/rules.debug, then do whatever work you need to do in the UI to make the fix permanent. –Bill

This could also be a thermal problem. You could try to clean all the fans and passive heat sinks.

http://forum.pfsense.org/index.php/topic,7011.0.html found with a search in Virtualization installations and techniques search word vlan

plz search http://forum.pfsense.org/index.php/topic,14207.msg75330.html#msg75330

if my internet speed is not getting close to being maximized Try with a ubuntu torrent, If you don't download with full speed on that it could be your client. For me deluge and torrentflux work better that transmission and vuze does. aka I don't want to load balance http traffic and have to login twice on each site since it's different IPs you could just load balance torrent traffic. I don't see how you can avoid logging in twice.

i just meant that you allow LAN(private)-> WAN and LAN(public) -> WAN in the Rules section (Source/Destination) but disallow LAN(public) -> LAN(private). If you want to access LAN(public) from LAN(private) then allow it, otherwise block it.

This turned out to be an issue with cacti 0.8.7c, upgrading to 0.8.7d fixed it.