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

Thank you! Thank you! Thank you! While I don't know exactly what the problem was, I am able to work around it by moving the PPPoE off of the pfSense unit onto the DSL gateway and still maintain the pfSense as the firewall. Now the Cloudflare sites are visible from inside my network. Thanks to your suggestion CMB, I was able to try another configuration on the WAN side that at least isolated the problem to PPPoE. Do we have a potential bug here in the PPPoE subsystem? I'm going to check with the Internet provider to see if any changes were made on their DSL infrastructure and see if there are any clues there. I would love to see the root cause of this explained and fixed. Bob.

who says its a problem?

Is it OpenVPN or IPSec? There are special topics here for each. Post the log from client and server.

Well after looking more in-depth on how VLAN's work and what I need to buy I made up my mind :) I got the D-Link DGS-1100-08 (https://www.amazon.com/gp/product/B008ABLU2I/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1) The reason I did not go with the T-Link is because people were complaining of a high pitch noise. For the access point I got the UniFi UAP-LR (https://www.amazon.com/gp/product/B00HXT8S9G/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1). I got this since it had good reviews and supported what I need. I also see it does have a guest option for logins which will work great for my needs. I have plans to make a guest VLAN with pfSense and then setup the VLAN on the UniFi AP and use that for the guest network. This is what I have a idea on from how I understand on how this all works. If I am wrong please do explain since I am new to this. Also another thing I would like to ask is for my modem I got the Q1000. I am guessing I will put the WAN into Transparent Bridging and put the PPPoE info on my pfSense router? (If Im right or wrong please let me know  :)) My new chart on the plan is this: Home: Modem -> Router(LAN) -> Switch -> AP (Home Network) Guest: Modem -> Router(VLAN) -> Switch - AP (Guest Network) Thanks