https://doc.pfsense.org/index.php/Multi-WAN is good and current information. Read that, try it, then ask if you are stuck.

Because you had a rip in the space time continuum? ;) your clock on your device was OFF would be my guess..

Can you ping them if you select LAN as source there? If so the NAT is working fine and you probably have a firewall rule missing somewhere. If you;re using policy routing to send packets to a gateway grouyp you will need a firewall rule above that to bypass it to reach the modem interfaces. Steve

Thanks for the update.  :) Steve

Yeah, I learned the hard way: Panic-ville. Hair on fire. Naked running through the campus. All that.  :D IBOX-501(N10a) Intel J1900 Quad Core 2.0Ghz 1SO-DIMM, support 1333/1066Mhz, DDR3L(1.3V low power), 4GB AMIBIOS 32MBit 4IntelWG82583 10/100/1000M Lan 32GB SSD Pretty much like this one: https://www.amazon.com/Firewall-Micro-Appliance-Gigabit-Barebone/dp/B01GIVQI3M/ The hardest lessons learned are the hardest to forget

You could probably write the install image to a SATA hard drive and boot from that. Then install to mSATA. Or if you can boot anything at all (some Linux distro from ISO) you can boot that then download the installer image and DD it to the on-board eMMC. Then boot from that an install to mSATA. Steve

The libcurl.so.4 should be reinstalled by curl as indicated by pkg its installed as a part of that: pkg which /usr/local/lib/libcurl.so.4 When i rename that file curl complains with the same error as you have, when i reinstall curl with previous command it works again.. For my test anyhow.. Not sure what else to try, maybe reinstall 'everything'?: pkg-static unlock pfSense-kernel-pfSense pkg-static upgrade -f

I installed a proxy with squid, squidguard and sarg. But blacklist management is not for everyone and reports are bad.

[image: 10z2q6o.jpg]

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