https://doc.pfsense.org/index.php/FTP_without_a_Proxy

If you are willing to switch to haproxy-devel (1.5) it should be able to do both ssl-offloading and transparent-clientip. Also in the background it will create the needed ipfw rules. How good of a job it will do for pop3s / imaps / smtps.. i have no experience there.

"but it would be useful if it could default to a common subnet mask imo." And who says what is common.. is /24 common?  Maybe to you - but to others maybe they always use /25 when bringing up a new segment..  You have no idea what a user might be creating a interface for..  To assume /24 solves nothing - if the user doesn't understand what the mask is in the first place.. Put in a feature request if you would like the drop down to start on /24 for new interfaces for ipv4, and /64 for ipv6 since drop down on that one is /128

Check the Packets RRD graphs, it's likely more or less in line with the search rate. There isn't a "you must have X rate of searches given Y rate of insertions/deletions", an average setup will be roughly along the lines of the numbers I posted previously, but that's dependent on what's happening on your network and can vary widely depending on the typical load your system is under. It sounds like you have many packets going through a small number of connections.

The bandwidthd package will do that. Thank you for that tip.  I had it installed a long time ago but haven't looked at it in quite a while.

Yes, its working for me!!! Great thanks  :) Can you please guide me how to enable joinme in?

yep, you are right stephenw10. I didn't think about him running nano. Well crap, and he already bought a 4GB CF. Personally I would have gone for 30GB or more and stuck with a ordinary HD, but that's me. More questions to be had here. What kind of wireless AP? PCI, PCI Express I assume? What chipset? What version of PfSense When your wireless device connects to it what speed is your wireless device reporting if any? BTW, sorry about my other reply, wasn't thinking straight when I replied.

Yes,  The firewall rule on WAN allowing access to your webconfig port on WAN address. The reason I hesitate to spell it out for you is because it's not a desirable thing to do.  Plenty of examples already out there.

Both are specific to SCTP, which has to be in use for either to be relevant. Nothing in the base system nor any packages does so. It'll be patched in 2.2.1 regardless, but has no applicability to what is available today.

that's not relevant to FreeBSD. With its Linux emulation, it seems it is (or might be), but that isn't something we use nor include.

Looks like a crash unmounting a filesystem. Could be a corrupt filesystem or perhaps the disk and/or driver aren't playing nicely with 2.2

I posted a HOWTO here: https://forum.pfsense.org/index.php?topic=87738.0

hi johnpoz i done as you showed in your pic but still says port closed. please advice many thanks

pfblocker is dead. see pfblockerng here: https://forum.pfsense.org/index.php?topic=86212.0

No such issue. Also, make sure you allow both UDP and TCP (UDP being used for any recent Windows versions).