I decided to do the old Windows trick - switch it off and switch it back on (reboot actually)  and lo and behold it started working again…. At least I'll know what to do if it happens again.

4 per minute is nothing. I was getting several per second before I turned off logging on the default block rule. With my 100Mb connection, I could scan the entire Internet in about 1.5 hours. During that scan I will have hit you at least once. Over the period of the day, I will have hit you almost 16 times. That's one computer. There are hundreds and thousands of compromised computers constantly scanning. If it was showing 5-10 per day, then it wasn't showing you everything.

started working, weird. Maybe it was the browser cache. What made me look is I got traffic from China and I set to top 20.

IIRC it was a limit of OpenSSL or the PHP OpenSSL module. They were rejected and wouldn't properly create a certificate. Might be worth a re-test. Supposedly certificates can contain those now but they have to be utf8.

Ok thanks I'll give it a shot, my motherboard had to be RMA'd so won't be able to try it for a week!

Yes I am. Thanks.

Ahhh fine. Answer my own forum :) See the setting below. Using Firewall Aliases & firewall Rules Firewall Aliases & Firewall Rules -  Firewall Aliases -  IP > Add -           Properties                   Name = (Aliases Name)                   Description =                   Type = Host(s) Host(s)                   IP or FQDN = (Domain IP Address)                   Description= - Firewall Rules     - Lan > Add                 (Leave everything else as normal except Destination)                 Destination =                                     (Single host or Aliases)  /  (Aliases name) - Advanced Options - Gateway  ( Chose WAN interface) Click save

Has anyone actually done this before and can provide an example of a rule addition from the developer shell?

I know this other method should probably work as well internet <–-> modem (bridged) <---> Pfsense 70.111.111.111 PPPOE / gateway 196.111.111.41 <---> DHCP <---> 196.111.111.42 <---> Server                                                                                                                                                                                       196.111.111.43 <---> Server                                                                                                                                                                                       196.111.111.44 <---> Server                                                                                                                                                                                       196.111.111.45 <---> Server                                                                                                                                                                                       196.111.111.46 <---> LAN but when trying to manage the rules table becomes it becomes quite messy, specially when you start to add forwarding and load balancing rules, and the rules for the LAN traffic, etc... that is pretty much why I decided to revert back, to a more simplistic 1:1 setup, to make redirection rules easier to manage, and to have everything at plain sight, not having to worry about accidentally messing up the rules for the Other machine, or mixing up the forwarding rules for the LAN, or scrolling through pages and pages of rules that are similar which are required for load balancing (2 WAN), and multiply that by 6 or more IPs, it becomes like a Book of rules to manage :P

how would I go about setting up pfSense as a DNS server for hosts on the localdomain? Does this help? https://www.youtube.com/watch?v=s3VXLIXGazM

AllGamer, muswellhillbilly, Thanks for your tips. I have tried already some of them and mostly those methods are not the same easy as just port forward to RDP. I do not expect clientless VPN. I think it would be possible to setup simple web page which enables RDP port forward to one of my LAN PCs. With additional precautions (port forward allowed for specific source address only and expires in certain period of time) this should be safe enough. Or not? I just though that this simple way is probably already implemented by other people.

MADZerQ: Maybe you should ask for your money back :)

Thanks for this information. It's just what I have been looking for to check out the firmware.

What about FAT32? It supports file systems bigger than 64GB. Works with DOS/Windows and Linux. Also a possibility is to use FreeBSD's filesystem UFS which might work with Linux but I'm not actually sure on that.

read this for reference https://forum.pfsense.org/index.php?topic=110217.msg614080#msg614080