Try Google Translate next time you run into some foreign text: https://translate.google.com Suspicious, via command prompt able to reboot and everything worked mostly normal. ;D ;D Thank you all !!. Glad to hear you got it working.  The Universal Windows Fix sometimes applies to other OSes as well.

https://doc.pfsense.org/index.php/Setup_Squid_as_a_Transparent_Proxy https://doc.pfsense.org/index.php/Setup_Snort_Package

Ok i solved the problem with booting from the 2nd Slice of my Nano-BSD Version and was able to backup the config. After reinstalling the SD Card with Version 2.2.5 and importing the Config everything works again. :)

And that is still a broke setup using /30 on wan and /24 on lan since they STILL Overlap!!!

Also along the power train of thought.  Many switches have a PoE power budget so even if x ports support PoE they can't all simultaneously run at full power.  So need to understand the switches PoE power budget and the draw of the devices being powered.

@littlearl: Newbie here.  Sorry for the bother folks, and thanks in advance for any help. I have an older laptop running 2.2.5 on a 4GB USB stick.  It's going great for the most part, but I know that stick is going to fail at the wrong time, so my preparation was/is to have an exact bootable copy that I can sijmply plug and play when the first one fails. Using dd to image the one drive to the other does fine with the bits but #2 doesn't boot.  I've tried messing with gpart to make partitions active and such, but nothing is working. I know this is probably basic, but I'm learning, and I promise I'll get better with help :) Thanks! Nano bsd has two partitions slices  containing two copies of os. Maybe that could be of some help.

WAN is .3 now?  I thought it was .1…  Is your pfSense WAN set to DHCP or static, and what's its currently-assigned IP address??

bitrot

forget about the router for now. what ip address did you give the pfsense box during the install? just type that into a web browser of a machine connected to the network switch. failing that lookup the default gateway of the machine your sat at and try that address in the web browser Chris

Should work fine from what I've read here previously.

That wasn't really needed, you could have just moved the pfSense webGUI to a different port, plus… uhm... that WebGUI thing shouldn't normally be accessible from WAN at all.

Thank you guys, we sent it back the LAN ports are 100 MB

Strange. With is little to nothing as information I can't say anything useful. All I know is that my DNS config spreads out over several (web GUI) pages. Any combination of settings on these pages are possible, only a few do make sens and will "do the job". All you gave is 127.0.0.1 (localhost, or pfSense itself) and "8.8.8.8" which is probably and (free) DNS from Google. Probably your setup makes it impossible that 'pfsense' can reach "8.8.8.8" …. It might also be something else. Who knows ....

I just has the hard drive on this system crash with no SMART warning(s) beforehand. I'm going to assume that these crashes were caused by this. I bought a new drive and I'll see how it goes. Thank you all for your help.

@plasmoid: I guess it would void the warranty, but dont know for sure since havent bought the box yet. Very likely. Though what would be the point in buying a firewall appliance just to break it? You'd be better off getting a vanilla 1U unit and installing whatever you want on that.

Thanks appreciate the answers - looks like a 1U unit is probably not going to happen based on budget and  a quick look on eBay. How about an Intel i5-2400 processor @ 3.10GHz with 12 GB RAM tower PC? Looks like those can be had fairly cheaply, then all I have to do is get a good performing PCIe dual NIC. thoughts? Thanks

2.2.2? That a typo and you meant 2.2.5? If not, start with 2.2.5. If you used that memstick to install using a laptop, it's likely not the ADI memstick, as you wouldn't have had a VGA console, only serial on COM2. Guessing you have the regular memstick, as where it stops outputting is where the VGA memstick (or non-ADI serial one) will stop outputting. The 4860-1U isn't on backorder at store.pfsense.org, btw. Only the desktop version is out of stock right now. But what you have will work fine.

Just to advise others. I found teh connection went up & down continuously until I set the MTU on the WAN interface to 1492. The default of 1500 doesn't work with the Infinity modem.

Not a matter of logic.  I answered that question from home where I run DD-WRT as I can't afford real pfSense hardware and I don't have a spare PC laying around.  I realize it's kind of ironic that I sit here and answer pfSense questions all day but don't run a unit myself, sort of like a barefoot cobbler.