Here's a pretty useful converter for bytes to bits. I know this seems silly, but we just need to have all of the information laid out and converted properly. Hope you understand! http://www.matisse.net/bitcalc/

I have decided to not use MAC filter, rather WiFi password access. I tried setting up WiFi password access by navigating to: pfSense > Interfaces > WiFi > Network-specific wireless configuration > WEP > untick Enable WEP > WPA > tick Enable WPA > PSK: password > WAP Mode: WPA2 > Save > Apply. My mobile device now won't find the pfSense WiFi? Any suggestion on how to set up pfSense password access to WiFi please?

Not a big fan of using pfsense as AP..  Just makes no sense to me – I would use a real AP, just so many more features and functionality that way. But I do believe a ifconfig should show your hostap settings.  When you do ifconfig do you see a hostap section?  What does it show?

You might try with BandwidthD  ;) https://doc.pfsense.org/index.php/How_can_I_monitor_bandwidth_usage

@MindfulCoyote: I'm confused ??? (per usual). Like this? Internet <–> [ 1Gbps NIC - Desktop Computer - AC1900 NIC ] <-Wi-Fi-> [DD-WRT on R7000] <–> Client Devices With pfSense then virtual on the Desktop Computer? Sorry, somehow I missed this! I have it set up like so: Internet (cable modem) <-WAN-> 1 Gbps NIC (onboard MOBO) - 1 Gbps Intel NIC <-LAN-> R7000 setup as AP (no DD-WRT for now) pfSense is running as the full blown OS on the computer I built, it's not virtual, all physical!

Do a forum search.  Others have the same Firefox issue.  It has to do with HTTPS.  There is a Firefox option that you can disable to perhaps fix it.

Hello vindenesen Yes you got right.  An MTU Size of 1500 on the WAN Iface solved the problem. As I configured the WAN Iface of my PFSense I read on several forums that the MTU size over the Bluewin VDSL line must be less than 1492 bit. So I put this value in. Now I checked the max. Transmission unit size with my old router (MTU Size is not visible in settings) with ping and I figured out that a package until 1472 data bits go thru without fragmentation. I read on Wikipedia that the Headers are together 28bit. So 1500 shut be possible. On my Linux clients the MTU Value is 1500 and this wasn't a problem befor. Dear vindenesen, thanks a lot to push me to the solution.

hardware issues with your storage device seems to be what is indicated. plug in a standard sata drive and reinstall, see if it resolves the problem. if it does, get a 2.5 inch drive and squize it in there ;)

Thanks Supermule. Been looking at Squid's Reverse Proxy, but I have no luck figuring out how to make Squid take care of the SSL part for my internal HTTP sites. I tried both Squid3 and Squid3-dev but still can't get it to work. Am I missing something or is there a guide somewhere to set this up?

For me it happen so infrequently that I can't be bothered spending the time to fix it.  Plus, I only use VirtualBox as a play lab.  For my real production work, I use vSphere 5.5 and I have never had this issue with VMware.

@imperialdrive: @imperialdrive: Just upgraded from 2.1.1 to 2.1.4… our office moved into a new building and the PFS install there was 2.1.4... after years of great performance, we quickly noticed RDP disconnect before a minute, every time, when going over a VPN connection handled by an internal MS RRAS server.  I went through everything I could think of before finally hooking our previous office PFS device and BOOM everything worked just fine.  So, now I'm thinking, ok let's upgrade to the latest version while I'm at it... now the constant RDP disconnects return. Downgrading now, but hey I feel your pain.  If there's anything I can do to help troubleshoot this for others, let me know. OK, I spoke too soon.  Still had issues.  Downgraded to 2.1.0… STILL ISSUES... went through the following settings with success - disable gateway monitors, clear invalid DF bits, disables firewall scrub, bypass firewall rules for traffic on same interface, unchecked the private networks options under wan, disabled all offloading under network interfaces under advanced After all that, and a full reboot... everything is working.  I'll keep an eye on it and slowly undo some of the changes to narrow it down. Upgraded to 2.1.1 and still running, also crossed the following off the list (offloading under network interfaces can be default, checksum offloading enabled, gateway monitoring can be enabled, disable PF scrubbing does not have to be checked, clear invalid DF bits does not have to be check) which just leaves the bypass firewall rules for traffic on same interface and the unchecked block private networks optoin under wan. I'll upgrade to 2.1.2 later this week and report back more findings.

I would like to point out for anyone else looking at this. If you take the reported average and divide it into the total transferred, it would indicate that the window was only 30 minutes, which makes no sense.

Linux/FreeBSD fundamentally treats RAM differently than on lets say… Windows. The operating system is designed and configured to page/cache as much as it can, and then expire/kick out the less important stuff when the need arises (squid cache, VPN, heavy outbound NAT, lots of states). We have a CARP pair in a data center acting as a reverse proxy which has 12GB of ram. Last time I checked we were using about 95% of total system RAM there. The main firewall pair has 4GB, supports up to 3,000,000 states, serves as VPN headend and NAT, and has about 10% usage. It all depends on your application and how you use the box. :)

The idea of using a separate WiFi access point is (in my mind) based on the idea that the AP has to handle the "wireless" part of the connection in the external box or the internal card, no matter which setup you choose. The advantage of the internal card is you theoretically get more control of the cards internal properties - although support for the cards is sporadic in some cases.  Integrating the network forwarding and routing control is done like any other interface. The external AP is already designed to be "self-supporting" and the internal config has to allow config of the wireless part.  The networking issues are normally handled through the simple expedient of disabling the AP's DHCP and any forwarding functions, UPnp, etc.  Doesn't DD-Wrt have an AP only mode? Personally I have no problem setting up AP's in this mode and treating them like an "extension switch" on my LAN networks with the ability to rely on pfSense for the rest of my firewalling/routing control. Just my $.02  ;)

What is your LAN interface setup? Do you have an internal router or layer3 switch? Any reason you're not running 2.1.4? Steve