Hi Steve, Thank you very much for the reply. I'm of the same opinion. I did purchase it from you . How do I get in touch with support? Indigo @stephenw10: That's almost certainly a bad SSD. They can fail to a state where they vanish entirely but come back after a power cycle, until the next time they fail. You should contact support if it's hardware you purchased from us. Steve

Coming back to DNS forwarder not resolving local (fully-qualified) hostnames after upgrade from 2.3.2_1 to 2.3.3_1, it turns out this was caused by: I had the same issue, not even long domain names worked in the DNS forwarder. Turns out it is due to a setting in the General Setup "DNS Server override" "If this option is set, pfSense will use DNS servers assigned by a DHCP/PPP server on WAN for its own purposes (including the DNS Forwarder/DNS Resolver). However, they will not be assigned to DHCP clients." That was checked on my setup and as such none of my local - full domain forward overrides - worked anymore. This was never a problem before pfSense 2.3.3_1. Perhaps it makes sense, but at least unchecking that and manually setting the DNS server setting above that instead of getting it from DHCP immediately fixed the issue I was having. After that I could query for any of the internal DNS entries again. Thanks to @wila (https://forum.pfsense.org/index.php?action=profile;u=320599)

Yeah there's no X400 as far as I know. The M400 maybe? Or X500? Steve

I would recommend switching to real modem devices rather than using the HomeHubs as a modem if you can. Or at least quasi real like the HG612  ;) Steve

What driver version is that? Did you try any of those tunables listed there? Steve

I had the exact same issue going to 2.3.3_1. I think the root cause of this issue is a sector errors that I saw in the console when it boot up. This is how it looked: ls -l /usr/local/lib/libintl* -rw-r–r--  1 root  wheel  0 Apr 19 21:59 /usr/local/lib/libintl.a lrwxr-xr-x  1 root  wheel  0 Apr 19 21:59 /usr/local/lib/libintl.so -> lrwxr-xr-x  1 root  wheel  0 Apr 19 21:59 /usr/local/lib/libintl.so.8 -> -rw-r--r--  1 root  wheel  0 Apr 19 21:59 /usr/local/lib/libintl.so.8.1.5 lrwxr-xr-x  1 root  wheel  0 Apr 19 21:59 /usr/local/lib/libintl.so.9 -> Notice the size. luckily I had another pfsense installed with the same version, so I grabbed the libintl.so.8.1.5 from there.

I'm on 2.3.3-RELEASE-p1.  Looks like you are on 2.3.2.  Maybe those files are different between versions.  You could try to spin one up in Virtualbox and extract the files from there.  That could get you going.

What is the model of the GPS Serial unit you are using?

I had the same problem with squidguard. I updated pfsense from version 2.3.3 to 2.3.3_1 and it solved for me.

You can try a couple of option 13 in console -> GUI update cycles, switching back and forth between stable and snapshots in between (skip the actual updates from console and GUI). Or just ignore it.

I figured it hadn't a clue but couldn't work out why it was all going to hell. What I've done now is to move the 2nd one (here, it was high up and while you couldn't see it it was in the open - not IN the cupboard ;) ) to a different room, where there is another switch so I could plug it in. SAme details as the other one so I am presuming my devices will swap from one to another depending on signal. The coverage is really just needed to get to the garage which is away from the house. The original point is as far away from that as is physically possible! Just thinking there that the usual 10/100 card that was teir originally would have been fine for the 72Mbps connection. I did replace the PCs in the house onbaord cards (and the pfsense cards) with 1GB just for internal traffic - a lot of file shifting going on. Thanks for the help.