Hello, If you disable and then re-enable the WAN interface start again to work? Or do you strictly need to reboot?

If it is supported by FreeBSD 10.3 then you should be able to shutdown, install the hardware, power up and it will be available as an interface to assign in Interface->Assign. If it does not appear, then it is not supported, and you won't have broken your existing config.

If the .47 device is a Windows client then it probably has its own firewall settings that respond to ping from the local subnet but not to remote pings from outside the subnet.

For all 64-bit AMD and Intel equipment, use the AMD64 image (the "AMD" is from past history of the evolution of that instruction set - both AMD and Intel make processors that have the "AMD64" architecture/instruction set. USB can be be easily written to a USB stick, and you can boot from that to do the install. Also read: https://doc.pfsense.org/index.php/Installing_pfSense https://doc.pfsense.org/index.php/Writing_Disk_Images

nope! Didn't pay anything for the server at all. Decommissioned at work, so got it for free. I don't think you can disable one CPU in the BIOS, at least I don't see the option. I was told (elsewhere) that the only way is to take it off of the board. If you see the BIOS option, could mind letting me know pls? -San

Make sure you have a default gateway. Check Diag > Routes, make sure you have a "default" line there. If you don't, then go to System > Routing, edit one of the gateways and mark it default, then save/apply and check it again. Try to ping out from the firewall by IP address, see if that works. If you can ping to 8.8.8.8, perhaps set that as a DNS server under System > General Setup and enable forwarding mode in the DNS Resolver. Also you could try disabling DNSSEC.

I tried a fresh install and it doesn't work correctly. I have to do some magic for it to see the hard disks (See https://forum.pfsense.org/index.php?topic=109952.msg613371#msg613371). After it can see the hard disk, it can only see 3 of the 5 NICs I've setup for it. I tried 2.3.3 and it had the same issues.

Still replying to myself… Package pfSense-base was missing. I was sure I had this correct... but no (was it installed to some other slice?) Adding this missing package (pkg install pfSense-base) fixed http://pfap.snet/pkg_mgr_install.php?id=firmware which was previously reporting "Unable to retrieve..." (reference: /etc/inc/pkg-utils.inc get_base_pkg_name()).

@jdillard: You'll have to use the Traffic Totals package moving forward and a 3rd party RRD reader, like an NMS, for past totals. You can select date range in Status > Monitoring and export to CSV and total there, but due to the way the data is stored in RRD the accuracy varies. I ended up finding the traffic totals package, and it is working going forward. I researched reading the RRD files manually and that's way over my head.  Doesn't appear to be an easy way to do that. So I used your tip and just exported the data to CSV and imported it in to Excel which I was able to manipulate way easier.  Thanks for that!!

Assuming you've installed the PFS system correctly, it should really just work. The fact you have it running on ESXi leads me to suspect this may be more an issue with a VLAN config on your virtual environment. Just guesswork, of course, until you can supply more details. Post a diagram showing your network setup, with internal IP addresses and some information on your WAN network setup. Not sure where you're seeing external traffic coming in - is this via the PFS logs or are you looking somewhere else?

There is no safe/supported way to change architectures in place.  On 2.2.x and before it could be fudged slightly but still dangerous. The safest way – and the only officially recommended way -- is a reinstall. As for the speed, it may or may not be related to that. Without more info, it's tough to say. We'd need to see info about the RAM usage, CPU usage, packages installed, etc, etc.

Just to add to Roberts reply. If you have wifi at 5Ghz on the pfSense router it will only be 802.11n, currently there is no support for 802.11ac with freebsd / pfsense.

Did you send a message in to our support team as well? I was looking through some very similar screenshots and logs yesterday with some of our other support staff. It looks as though it's having trouble reading the eMMC media, which may indicate a hardware issue. If you already have a conversation going with us via support, keep going that way. If not, contact us and we can check into what may be happening there. If it is a hardware issue and the unit is still under warranty it can likely be replaced with an RMA. If you cannot do that for some reason, or if the unit is out of warranty, then you could purchase an mSATA disk and use that instead of the built-in storage.

";; Received 446 bytes from 192.33.4.12#53(c.root-servers.net) in 5699 ms" So almost 6 seconds to get a response, yeah that is going to cause problems because many clients timeout after 2 seconds linux I think is 5?  So if you had a client asking for www.something.com and it was not cached and had to walk down the tree and your talking long long time to get a response its just going to give up. Shoot even with your 600ms response time from google, and it pulls from its large cache you could run into problems if anything causes a slow response, like what your looking for is not cached in google and it takes a while resolve.  You might want to look into increasing the timeout for dns queries on your clients. These 2 options could be increased from the defaults in resolv.conf timeout:n sets the amount of time the resolver will wait for a response from a remote name server before retrying the query via a different name server. Measured in seconds, the default is RES_TIMEOUT (currently 5, see <resolv.h>). The value for this option is silently capped to 30. attempts:n sets the number of times the resolver will send a query to its name servers before giving up and returning an error to the calling application. The default is RES_DFLRETRY (currently 2, see <resolv.h>). The value for this option is silently capped to 5.</resolv.h></resolv.h>

Thanks for the info  :)

:)