It is not incompatible with the motherboard as I have run Windows 7, Windows 8.1, Windows 10, Ubuntu, and Linux Mint with the same set up without an issue. My question is simple, does pfsense support installations on m.2 PCIe-based SSDs?
What you did should have worked. Edit the config.xml and change the interfaces to the new interface names (igp0/igb1?)
Beware search and replace or you'll probably whack some crypto blobs. Be sure every replacement is actually an interface name. Should only take a couple minutes. Then it should restore without the interface reassignment phase.
Not that that's what blew up. It should have worked.
im looking to get a hang of the fundamentals.
Then configure your network in a fundamentally-sound way. Not one that requires hairpinning traffic in and out of 192.168.1.1 to get from 192.168.1.26 to 192.168.100.3.
You also have to disable NAT in pfSense. or you won't be able to directly address 192.168.100.0/24 at all.
MEDIUM ERROR
Smells like a wonky disk.
pfsense 2.2.4 32bit
i386 builds are being phased out. Why not install the x64 build? The hardware is certainly 64-bit.
Hi again :)
Thanks for the quick response.
Unticking the forwarding mode actually seems to have fixed it. Not sure where I picked up that I had to tick this setting, but it seems to do the trick.
Many thanks for that!!!!
While we're at it, would you know if I should tick the "Block Private Network" box in "Interfaces: WAN"?
My understanding from the contextual help is that because I'm behind another router that I need to un-tick this? Is that corrector should I leave it ticked?
Many thanks again for your help!
As the others have already said, this is dead simple if you know what you're doing. Hopefully you did NOT specify a gateway for your LAN NIC.
Post screens of Interfaces - LAN, and Firewall - Rules - LAN.
From here….
https://forum.pfsense.org/index.php?topic=97554.0
It would seem you could boot into single user mode (even on full install) enter the commands and enable TRIM.
You would need your device name (might get that using the dmesg command and then doing the steps). Might try later.
@beetlejelly:
Is another process writing to this file and breaking unbound?
No, that's typical of what happens when a file isn't fsynced and you lose power shortly after writing it. Should be worked around now, and reported upstream to be fixed in Unbound.
https://redmine.pfsense.org/issues/5334
