setup up a host override in pfsense for server.whatever.tld your local domain is then you will be able to access http://server.whatever.tld that is if your nas uses http.  If your trying to just access a file share via unc you could still do \server.whatever.tld For example I access my storage server via \storage.local.lan [image: fqdn.jpg] [image: fqdn.jpg_thumb]

Could it be an errant .pid file that makes it think that there is a lock when there isn't really one?

No, you cannot get a report using captive portal usernames. There is no way to reliably map the IP addresses to a username over time, and it isn't logged since squid and captive portal do not directly interact. If you want to use it that way, force the users to put in proxy settings (or use WPAD, etc) and use squid authentication instead of captive portal.

That's probably just a bit rate mismatch in the config. After the boot prompt the console is being set to a different rate. The BIOS on the APU is 115200,8,n,1. pfSense (FreeBSD) is probably set to 9600 in the config. If you set your serial console to 9600 you will likely get incorrect output during POST but after that it should be sane. When you get your system up go into System > Advanced and set the serial speed to match the BIOS (115200).

I certainly wouldn't suggest a floating rule for what is presented as a very basic single interface/direction firewall case. Just my $.02

The interface assignment for that is just a stub, really. Disabling that doesn't stop it from being configured. The actual config for the interface is in the GIF settings under Interfaces > (assign), GIF tab.

I try to ping google.com from Pfsense shall and pinging failed.

@jimp: Is there a specific reason you feel that you need to add 250+ IP alias VIPs on the firewall? What problem are you attempting to solve? Odds are there is a much easier way to accomplish the same goal. That's a good point as well. Many times if you're trying to do that, you're doing it wrong.

Last 0 Firewall Log Entries. (Maximum 50) No logs to display original ipv6 is fe80::

Somehow  that rule is very confused. It has an IPv6 gateway but is passing to an IPv4 address. Looks like it's an automatic NAT rule though. I'd check the settings on the WAN interface (gateways selected), plus look at the NAT rule in question and its associated firewall rule.

System>Packages, uninstall it.

Because your WAN's reconnecting or renewing every 10 minutes. "IP change or dynamic WAN reconnection" Guessing you probably have a DHCP WAN with a 20 minute lease time. If that's the case it's not anything to worry about.

Okay, thanks.

So, this is my LAN firewall rules and these are my Outbound NAT rules. I set DNS servers for each gateway under System>General settings. However, when I put them in place and disable the default LAN to all rules I get no connectivity on both the file server (101) and my PC which should fall under the next rule, correct? Edit: This was the guide I used.

The block the support guys use is out of Austin (shared between our office and Austin colocation), the updates and much of the other file hosting is out of NYI in NJ. So no, the same netblock can't be used for both. Point taken on support access though, it's something we've talked about making a package or similar to help accommodate. That may be something that comes in the future.