Pro'sI'm running this at a house with the latest version of OpnSense in a house of 4 people who are doing Zoom/Teams/games/Steam downloads/Online Games.  The NICs are performing well.  I was using a NUC with two realteck NICs that seem to get hung up a lot (existing connections working but new connections wouldn't occur).I love the price point and the concept of just hardware with coreboot support for you to install whatever you want on it.The hardware performance seems to be adequate.  With OpnSense, I have the basic local DNS, DHCP enabled along with traffic shaping, Insight monitoring and ntopng traffic monitoring.  The memory usage is only about 10-15 percent of the 8 gigs, the CPU usages is around 180 percent (it has 4 cores so that's out of 400 percent).ConsEven though the amazon pages says Coreboot, this unit doesn't have coreboot on it.  The company's website recommends you don't flash it and if you want coreboot to buy a unit from them directly with the core boot option.While the performance of the hardware is decent, the reliability is not.  After an uptime as little as two days, I will get error messages like(ada0:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error(ada0:ahcich0:0:0:0): Retrying command, 3 more tries remain(ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 40 28 56 70 40 03 00 00 00 00 00(ada0:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error(ada0:ahcich0:0:0:0): Retrying command, 3 more tries remain(ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 40 e8 23 78 40 03 00 00 00 00 00(ada0:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error(ada0:ahcich0:0:0:0): Retrying command, 3 more tries remain(ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 c0 a8 24 78 40 03 00 00 00 00 00(ada0:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error(ada0:ahcich0:0:0:0): Retrying command, 3 more tries remain(ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 80 a8 25 78 40 03 00 00 00 00 00(ada0:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error(ada0:ahcich0:0:0:0): Retrying command, 3 more tries remain(ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 40 68 4d 72 40 03 00 00 00 00Which indicates the FreeBSD OS the OpnSense is running on had an error when trying to write to the disk.  I have Insight and ntopng running which writes network statistics to disk, this issue will largely be impacting that but there's also a chance of this causing OpnSense to fail.There are a couple of possibilities what is causing it:Bad SSD - This comes with an SDD of a brand BiWin (which I never heard of before).Overheating - This is a fanless device.  The heat sink is pretty warm but doesn't feel too hot.  OpnSense detects one temperature sensor (which I'm guessing is a chassis temp senor) that is at a steady 27C (which is not to hot).Other bad hardware - If it's not heat or the SSD it could be bad board, CPU or memory.Now I have to try to figure out which it is or return the device.  I'm thinking of getting a SSD from a reputable brand like Samsung, but if that doesn't help I got a bigger hole in my wallet.UPDATE:I replaced the SSD with a Samsung brand 30 gig.  And now it's working great without any disk write errors.  My recommendation is to avoid this 120 gig version of this product.  The SSD it comes with is not reliable.