Also works here, Ubuntu + latest FF.

The only way I could get it working was to install 2.1.5 and then do an upgrade to 2.2.4. (I don't see 2.1.5 in the download list anymore.) There is something with the disk layout that conflicts with the 6501 bios boot and I haven't seen any solution.

@heliop100: …. Any idea? Your partition is read only ?

@Derelict: Nope.  Upgrading in the first place will clobber most of that anyway.  Pretty much on you to have a log of the out-of-gui changes you have made so you can duplicate them on a reinstall. Yup, fair enough for the cowboy that goes off-road, such as myself. I wanted to see if I could salvage the situation without blowing the escape hatch, it's been a couple days, so far so good. :)

This question would be better posed in the Cache/Proxy forum. When you make any changes to squidGuard, you MUST click the Save button and then go back to the General Settings tab and click the Apply button.

@robi: What kind of NICs are there, having such problems? It's an APU1D box with the Realtek 8111E GB interfaces. The unit is connected to a Cisco 2960 (trunk-only port). I maxed out at 85 MBps on a 100 MBps Internet line before changing the MTU - then I got 98 MBps throughput without changing anything else, leading me to suspect MTU problems due to the VLAN tags.

What a relief! Now I know I'm not the only idiot in this world.  :o 've burnt an Advantech AIMB-272 pretty much the same way  ::) And yes, it's fun to make custom cases with dremels and flexes…

I am assuming that this is a BIOS issue, as I have had this work on other machines.

You're making an issue for yourself, something that works for hundreds of thousands of us, usng pfSEnse, doesn't work for you. As the mentionned "gateway-on-lan issue", totally not existent, even when looking it up in Google, but suddenly present on your system, this is pretty much the same thing. Static DHCP leases are setup in pfSense. Handle them, like creating, modify, delete them in the GUI, and all is well. There is no need to wipe some hiding database (btw : Google knows where this 'database' is, as soon as you use the correct word: config.xml). For some reason, most of us do not use a power-backup supply (UPS) for our pfSenbse boxes, and still things work very well. And yes, you are not the only one with power failures. So : the good news is: there is no problem. And if there is one : you made it up yourself, so : remove it, and you're ok ;) edit: using a static IP on the client (PC) which fells out of the network mask of pfSense will break the connection, that is normal.

Some Windows clients try to muck around with CR/LF if they think they see any ASCII character.  Check for an option to download as a binary file.

The pfSense default is 115200 with 2.2.x. The Alix BIOS default isn't 9600 either, but rather 38400, IIRC. Fix your settings to match everywhere.

If you rule out the low hanging fruit, the next thing is drivers, memory, or harddrive issues corrupting data.

(1) Should a full install be done on the M.2 (and leave the emmc as a fallback)? This would be the most and common installation method, full install on a SSD/mSATA/M.2 but the full installation can also be done on the eMMC storage because it is predestinated for many read/write cycles without failures. So if the nor SquidGuard are not really needed it would be also a really gain for many update / upgrade procedures.

Yes, as noted above, booting the ISO doesn't work. None cares at FreeBSD land.

I gave up on this once I took a look inside the memstick image and compared it to the upgrade image.  the memstick contains an ISO, the upgrade contains a tar image of a viable filesystem.  I had a known working  memstick available, so I slicked the box and reinstalled that way, then added back my config file and was on my way. of course reverting that way doesn't scale, you need local access.  I did figure out where to upload a backup to have it recognized in the web ui, but wasn't sure if trying to roll back a release would succeed from that route.