Well, bossman decided to do away with our DNS server & make the big fish upstream do it for us so the problem solved itself! Thanks for all the help though.

Good luck mate.

…and you add pass rules on the extra LAN/VLAN interfaces. (Only the first LAN-style interface gets a default pass rule added)

@jimp: Reinstall the package. A 404 means the file is missing, most common cause is the package files being gone but the menu entry remaining. Reinstalling the package will fix it. Ah! Thank you so much! I never had used the package before on this firewall, and didn't realize I never installed it. The previous one I had someone else had configured that feature. It was difficult to find in the packages because I was looking for "RRD" and skipped over "mailreporting" thanks!

ok, thank you.

Thanks Phil! that makes sense.

It isn't (very well?) encrypted by default, though you can enable it easily enough: http://en.wikipedia.org/wiki/Remote_Desktop_Protocol#Security_issues Steve

Ahaa, I disabled the admin account and tried with a personal one ….. Great, thanks a lot for your help! Rumpi

@glennbtn: I have 1 or 2 lan ip's I want to block access to certain websites. Can anyone advise the best way Firewall rules on the LAN interface.

Is there a way to put a FQDN into PFsense DNS without registering a domain name externally?  Almost like an lmhosts file in Windows?  Looks like you can add a DNS "Host Override" under advanced in DNS forwarder?  Is it a good idea to do this?  For example, the FQDN for the pub is an external hosted website, but could add wifi.puburl.com into the hosts override and assign this to the captive portal ip? Still not really sure what that call to the function does mentioned above? Looks like it would only be useful if you had more than one interface using the Captive Portal.  It seems to look at the interfaces in use for the portal, get the IP/Subnet for those interfaces, look to see which the clientIP 'matches', and then assigns the IP address for the captive portal according to which interface the client is on? So if using just one interface, you could opt to loose the call to this function, as you are always going to get the same result from the call. Is there a reason to NOT use the hostname of the pfsense server?