@cinepro: @Perry: Maybe you can get local support if you provide country and city information. I'm in Los Angeles, but I'd be willing to use a remote session.  But I think I'll give Centipede a try. Thanks! We also offer full support for pfSense installations.  However, I would give Centipede a try first.

The point is that if you back up your config, when you restore the config it'll install the required packages too (from what I've read here - I've not had to do it myself yet).  That and the fact that the installation size is aimed at working for all hardware, not just brand new stuff. My solution was to install rsync and then use rsnapshot (which runs rsync over SSH) to back the pfSense host up across the network.

the overall big picture here is you are worried about heat / power usage etc.   the issue is not about installing torrent junk on pfsense.   so get to the root of the problem a 1200mhz duron wasn't designed to be a 24/7 routing chip, its a desktop processor u could cook your eggs on with big noisy fans etc yank the power sucking, heat generating firewall pc.   put pfsense on a silent passive cooled embedded device with compact flash.  then  get another one and install linux and run it just for file serving/torrents theres even 1u rackmount cases and such that will accommodate two separate mini itx motherboards, then you can have your "one pc" powered on 24/7 but have two independent pc's

bummer nvm maybe one day

OK I will contact my hardware-dealer and ask for freeBSD compatible fibreoptic-card. Thanks foru your help so far.

@tester_02: @Sh4: Install ntop or bandwithd package to keep history Problem right now in 1.2.1 is bandwithd does not work. bandwidthd works for me: See last reply in http://forum.pfsense.org/index.php/topic,11053.0.html

Ask in the Traffic Shaper Bounty.  http://forum.pfsense.org/index.php/topic,2718.0.html If it is then make a contribution and you can get the shaper.

You can also use sftp and schedule it to backup the files that way. http://forum.pfsense.org/index.php/topic,8485.0.html

I don't know if that would be a good idea.  having each allowed outbound port listed in the rules in beneficial.  If you ever wanted to temporarily disable a rule say deny 443 temporarily or 3389 or better yet 25 you would only have to disable the individual rule.  By grouping them under 1 aliase, if you wanted to disable 1 port listed you would have to modify and then delete that port from the aliase.  Also if you were to need to troubleshoot looking at the raw filters it might group everything together.

You might want to put this in as a bounty.

Falcon4, I suggest you open your eyes and at least do a bit of research before claiming that Unix is only good for networking. I am typing this message from a Unix box and the vast majority of my time spent using or developing for computers is on Unix type machines. I've got a room full of servers running Unix doing things other than networking. If you're so worried about "wasting" a computer on Unix to do some networking, go buy a little embedded Alix box for less than $200 and install pfSense on that. Bashing Unix here is not going to make you any friends or encourage anyone to help you.

I think ManageEngines Netflow Analyzer offers 2 free collectors and includes free billing feature's

I would go with 4 interfaces (3 NICs)…two WANs, one LAN, one VLAN.  Disable the internal DHCP on the APs.  Use the DHCP from pfSense for BOTH VLAN and LAN, install captive portal and enable it on the VLAN.  Make sure that the two interfaces are on disjoint subnets, you can also set the default rule on both interfaces to prevent traffic from going from VLAN-LAN and vice versa.  LAN becomes VLAN1 (the default VLAN) in a setup like this. We only have one WAN here, but use the same VLAN for wireless setup.  If your APs can support it, setup two SSIDs; one on the LAN for your employees to connect to the Citrix servers, and a second on the VLAN for guests to hit the captive portal for web access. The full setup would be like this:  WAN1/WAN2 (NIC1/NIC2)-> LAN(VLAN1, NIC3, 10.1.1.1) or guest VLAN (VLAN2, NIC3, 192.168.1.1)

its easy change ISP