I have had a few discussions with visa@ about builds on OpenBSD/octeon. For ports builds, 1GB of memory like in the EdgeRouter 4 and 6 is too little to build big things like gcc which is required for quite a few things. The EdgeRouter Lite, EdgeRouter PoE, and USG are even worse with 512MB of memory. Also, the EdgeRouter 4 and 6 have some issues with the USB 3.0 controller that visa@ has not been able to work out yet. It's pretty difficult to get any insight into what is happening with the USB 3.0 controller. The ER4 and ER6 work reasonably well with Samsung USB Fit USB 3.0 flash drive but occasionally weird errors happen and the system freezes up or panics. I was not able to get a Samsung T3 or T5 USB SSD to work with the ER4 or ER6.
The best route for a readily available machine for OpenBSD/octeon builds is either the USG Pro 4 or the EdgeRouter Pro. They both come with 2GB of memory but can be upgraded with up to 8GB of memory. Unlike the USB flash drives in the USG and EdgeRouter Lite/PoE, the internal storage is soldered on as was said in this thread already. The best route for storage I have found thus far is a USB SSD like the Samsung T3 or T5. I have not tested any others at this point but others probably work as well. For the EdgeRouter Pro, I have it running from a 250GB Samsung T3 USB SSD and have upgraded it with an 8GB SODIMM of DDR3 1333MHz memory. The part number that worked for the EdgeRouter Pro is Patriot PSD38G13332S. I found this information from the UBNT forums. For the USG Pro 4, I bought the same Patriot memory but had all sorts of crashes and problems. I'm not sure if the memory chip is bad or if it is just expecting different memory (have not had time to test) but I looked at the factory memory in the USG Pro 4 and bought similar memory which works fine. The factory chip is Kingston KVR16S11S6/2. I bought a set of Kingston KVR16S11K2/16 which is two 8GB chips. They work perfectly and I plan to get another USG Pro 4 for a second build machine to utilize the second 8GB chip I have. With 8GB of memory, most ports builds work fine including gcc but occasionally I see some weird error that usually disappears with restarting the dpb(1) build. Bryan
