Docker supports IPV6 just fine but it has to be enabled before you start deploying containers. And understandable why Zima doesn't enable it by default as I doubt the majority of folks that are going to homelab with this device aren't likely running IPV6. You're one of the few tech youtubers that I watch that is running IPV6. Heck in my NOC we only have one, out of over 130 customer network, running IPV6. And these are major telecom entities. IPV6 soapbox aside I think this device is a little overprices considering the alternatives and a little bit too much form over function. They could have kept the second ethernet port, PCIe slot, and given an option for 32gb ram and i'd have bought one. As such this thing would be relegated to running pFsense or OpenSense, Pihole, or some edge services. Cool that they sent one in for review, though. Good to see that hardware firms are finally taking notice of your channel. 👍
eMMC's have a very limited write cycle lifetime. Make sure to keep all files and folders that will have frequent changes, such as logs or cache, off of the eMMC unless you want it to fail in 3-4 years. And on that model since it's soldered on, it's not easy to replace. It's the eMCC write cycle limits that killed the iLO in old HP Gen8 servers due to a BIOS bug causing too many writes of the IPMI logs. And they too had soldered on eMMC chips requiring the motherboard to be sent in to HP to be replaced (unless you know someone skilled in replacing BGA chips).
It's an interesting SBC, still can't justify the cost however compared to perfectly good hardware people throw out. Than again I smoke and drink beer :P
I'd like to see some power specs with a kill-a-watt or similar device. Especially with 2 NAS/Enterprise grade drives attached, as that looks like a primary use case.
Like the idea of using different video shooting angles, some seems to be hit and miss though. Suspense music was a bit loud and much. Keep up the good work!
As for docker and IPv6 in Docker if you use 'bridge' networking you have virtual IP, it's the default because you can then filter it using iptables and create complicated rules. If you use 'host' it will expose casaos ipv4/v6 to the docker container, adguard would have casaos's v4 and v6 address, it's easier but harder to manage
Usually it's a focus issue, since I film solo I can't always see if I've made a mistake on the camera screen until I get into editing. Autofocus also does me dirty kinda often.
That is a really interesting device. I know I've chatted about how I follow your channel because we're doing a lot of the same things, me for work, and I assume you for fun? Anyway... I tried to do the thin client with a Raspberry Pi 4 via the Proxmox API/spice client, but, at least I didn't think, the performance wasn't good enough for our college. I'm wanting to find a solution where we can put the compute within our data center and all of our instructional computer laboratories would thin client to our multi host Proxmox cluster. I wonder if this would be a good choice to try this out?
@@apalrdsadventures we have a handful of departments we do our labs for but only one of them has come to me during the pandemic, while we were fully remote, and wanted to use a usb fpga. Other than that the other departments just use keyboards and mice.
@@VexMage you can definitely use a Pi4 for remote desktop, but unfortunately Spice is pretty slow. If you instead use freerdp the performance will be much improved. be sure to play with the defaults though... Freerdp uses pretty old parameters by default...
@@LampJustin as a thin client this would need to be handled by the software on the system, since we aren't a software shop it'd all have to be doable through automation with as little responsibility on the users' side; as students shouldn't be responsible for learning how to interact with our labs. This was the allure to using the Spice client via Proxmox, the system would simply boot to a script that pulled the token from Proxmox through an API and initiated the Spice client connection. This Pi4 image is available now to do this. Also our solution needs to be operating system agnostic, so while xrdp can be installed on Linux, etc... another allure to the Spice client was that it didn't matter if we were running ReactOS, Hurd, an operating system written by one of our professors, etc... However your suggestion that Spice itself may be the bottleneck, perhaps I should relook into the Pi4 software performing the automatic connection to Proxmox VM terminals and see if VNC is directly supported. If it is, then perhaps VNC would work well 🤔 Thank you for the lead!
@@LampJustin I forgot to mention the other nice thing about the Spice solution is that USB passthru from the thin client to the Proxmox VM is allowed. It's one reason NoMachine is mentioned a lot with our project!
Docker supports IPV6 just fine but it has to be enabled before you start deploying containers. And understandable why Zima doesn't enable it by default as I doubt the majority of folks that are going to homelab with this device aren't likely running IPV6. You're one of the few tech youtubers that I watch that is running IPV6. Heck in my NOC we only have one, out of over 130 customer network, running IPV6. And these are major telecom entities. IPV6 soapbox aside I think this device is a little overprices considering the alternatives and a little bit too much form over function. They could have kept the second ethernet port, PCIe slot, and given an option for 32gb ram and i'd have bought one. As such this thing would be relegated to running pFsense or OpenSense, Pihole, or some edge services. Cool that they sent one in for review, though. Good to see that hardware firms are finally taking notice of your channel. 👍
eMMC's have a very limited write cycle lifetime. Make sure to keep all files and folders that will have frequent changes, such as logs or cache, off of the eMMC unless you want it to fail in 3-4 years. And on that model since it's soldered on, it's not easy to replace. It's the eMCC write cycle limits that killed the iLO in old HP Gen8 servers due to a BIOS bug causing too many writes of the IPMI logs. And they too had soldered on eMMC chips requiring the motherboard to be sent in to HP to be replaced (unless you know someone skilled in replacing BGA chips).
It's an interesting SBC, still can't justify the cost however compared to perfectly good hardware people throw out. Than again I smoke and drink beer :P
looks like a serial connector could be soldered on the board and you can jtag this
stay away from ubuntu shell ads and horrible snaps #pear shaped
I'd like to see some power specs with a kill-a-watt or similar device. Especially with 2 NAS/Enterprise grade drives attached, as that looks like a primary use case.
Love the content. The camera focus wonders around.
Yeah, I'm aware, it's not always easy to get it right working solo
Works well as a moonlight client. Also, a nvidia 1030 works stable as it is low power.
I had looked at the zima before, kinda sweet. the 2 NICs + SATA is such a neat thing
It's certainly useful for a lot of projects, I definitely have a lot of ideas to do with it
Like the idea of using different video shooting angles, some seems to be hit and miss though. Suspense music was a bit loud and much. Keep up the good work!
I must say I really enjoyed the suspense Music :)
Yay for a dockerless homelab! A test using a PCIe extender for 2 (or 4) cheaper NVMe drives would be interesting.
It’s literally using docker
@@andherium I know that, I was showing some support for the dockerless comment.
I really like this one for router. It is a pity it comes with 2 Realtek NICs instead Intel ones or similar. Pfsense does not like it.
As for docker and IPv6 in Docker if you use 'bridge' networking you have virtual IP, it's the default because you can then filter it using iptables and create complicated rules. If you use 'host' it will expose casaos ipv4/v6 to the docker container, adguard would have casaos's v4 and v6 address, it's easier but harder to manage
Interesting Review. A lot of Bluriness in this Vid. Have you been shooting with wide open aperture? Maybe because of insufficient lighting?
Usually it's a focus issue, since I film solo I can't always see if I've made a mistake on the camera screen until I get into editing. Autofocus also does me dirty kinda often.
Little disappointed about the realtek nics. But oh well, that' how you can keep the price down.
If you are using Linux it's legitimately not a problem
That is a really interesting device. I know I've chatted about how I follow your channel because we're doing a lot of the same things, me for work, and I assume you for fun? Anyway... I tried to do the thin client with a Raspberry Pi 4 via the Proxmox API/spice client, but, at least I didn't think, the performance wasn't good enough for our college. I'm wanting to find a solution where we can put the compute within our data center and all of our instructional computer laboratories would thin client to our multi host Proxmox cluster. I wonder if this would be a good choice to try this out?
What sort of requirements do you have? Is USB at the workstation important?
@@apalrdsadventures we have a handful of departments we do our labs for but only one of them has come to me during the pandemic, while we were fully remote, and wanted to use a usb fpga. Other than that the other departments just use keyboards and mice.
@@VexMage you can definitely use a Pi4 for remote desktop, but unfortunately Spice is pretty slow. If you instead use freerdp the performance will be much improved. be sure to play with the defaults though... Freerdp uses pretty old parameters by default...
@@LampJustin as a thin client this would need to be handled by the software on the system, since we aren't a software shop it'd all have to be doable through automation with as little responsibility on the users' side; as students shouldn't be responsible for learning how to interact with our labs. This was the allure to using the Spice client via Proxmox, the system would simply boot to a script that pulled the token from Proxmox through an API and initiated the Spice client connection. This Pi4 image is available now to do this. Also our solution needs to be operating system agnostic, so while xrdp can be installed on Linux, etc... another allure to the Spice client was that it didn't matter if we were running ReactOS, Hurd, an operating system written by one of our professors, etc... However your suggestion that Spice itself may be the bottleneck, perhaps I should relook into the Pi4 software performing the automatic connection to Proxmox VM terminals and see if VNC is directly supported. If it is, then perhaps VNC would work well 🤔 Thank you for the lead!
@@LampJustin I forgot to mention the other nice thing about the Spice solution is that USB passthru from the thin client to the Proxmox VM is allowed. It's one reason NoMachine is mentioned a lot with our project!