Excellent, thanks for the update!

Can you make your docker service start after the NFS Mount to rule that out?

A restart policy only takes effect after a container starts successfully. In this case, starting successfully means that the container is up for at least 10 seconds and Docker has started monitoring it. This prevents a container which doesn’t start at all from going into a restart loop.

https://docs.docker.com/engine/containers/start-containers-automatically/#restart-policy-details

If your containers are crashing before the 10 timeout, then they won’t restart.

His wife was a little less impressed /s

Hans Reiser was convicted of murdering his wife. He is (was?) in jail.

Edit: https://en.m.wikipedia.org/wiki/Hans_Reiser

For free? Probably not.

Wireguard has been audited by some University groups, maybe contact one of them:

• https://www.cerias.purdue.edu/assets/pdf/bibtex_archive/2021-3.pdf
• https://courses.csail.mit.edu/6.857/2018/project/He-Xu-Xu-WireGuard.pdf

I think its better to keep your gateway basic, and run extra services on a separate raspi or similar. Let your router/gateway focus on routing packets.

Openwrt can run Adguard, and as long as your gateway can run docker, you can probably get pihole working.

Could you share the article?

For openwrt+wireguard, see: https://cameroncros.github.io/wifi-condom.html

Looks like tailscale should work in openwrt: https://openwrt.org/docs/guide-user/services/vpn/tailscale/start

For the wireguard server, I am using firezone, but they have pivoted to being a tailscale clone, so I am on the legacy version, which is unsupported: https://www.firezone.dev/docs/deploy/docker

Edit: fixed link

That is likely a speed test server within the same data center as your vps, or they have special traffic shaping rules for it.

Try using iperf from your local box to the VPS and see what speeds you get

I think that should do it. I’ll try later today and report back.

Of course, this risks getting into an even worse state, because if the parent later tries to correctly wait for its child, the call will hang.

Edit: Will clean up the orphan/defunct process.

If the parent ever tried to wait, they would either get ECHILD if there are no children, or it would block until a child exited.

Will likely cause follow on issues - reaping someone elses children is generally frowned upon :D.

Zombie processes are already dead. They aren’t executing, the kernel is just keeping a reference to them so their parent process can check their return code (waitpid).

All processes becomes zombies briefly after they exit, just usually their parents wait on them correctly. If their parents exit without waiting on the child, then the child gets reparented to init, which will wait on it. If the parent stays alive, but doesn’t wait on the child, then it will remain zombied until the parent exits and triggers the reparenting.

Its not really Linux’s fault if processes don’t clean up their children correctly, and I’m 99% sure you can zombie a child on redox given its a POSIX OS.

Edit: https://gist.github.com/cameroncros/8ae3def101efc08be2cd69846d9dcc81 - Rust program to generate orphans.

Never heard that term, but its a very obscure concept, so wouldn’t surprise me if it had multiple names. Probably vender specific names?

Seems quite a few people havent heard of it, hence a lot of the split DNS answers :/

I can’t remember exactly what its called, but something like router NAT loopback is what you want. I’ll have a look around. But if you set it right, things should work properly. It might be a router setting.

Found it: https://community.tp-link.com/en/home/stories/detail/1726

I am also Aussie, but I’ve been buying from Aliexpress of late. Maybe should try some Mirabella bulbs again, last time I bought them it was after the first OTA exploit was fixed, but before cloudcutter. Had to slice open the bulbs and flash via serial.

Are you just getting stuff from Costco?

Have they updated it for new stuff? Last time I tried it cloudcutter was patched in new stuff :(

I saw a 1.5hr video published a few hours ago, dunno if it got removed. Description did say it would be edited and reuploaded.

4 cores is a bit limiting, but definitely depends on the usage. I only have 1 VM on my NUC, everything else is docker.

I thought all the core processors had VT* extensions, I was using virtualization on my first gen i7. They are very old an inefficient now though.

Are you from Tuya? They seem hellbent on locking their stuff down to the cloud.

Perhaps point out to your management that IOT is an enthusiast driven market. If you appease the enthusiasts, they will recommend your products to their less technically inclined friends.

Enthusiasts want both: a good initial software ecosystem, and the option to break out of that if required. If your company can offer that, even if it involves voiding the warrenty, we’ll buy and recommend their stuff.

In the case of Tuya, their stuff was historically super easy to open, solder some jumpers and flash (or exploit the OTA to flash). I bought loads of their power boards and lights. In some ways I was an ideal consumer, I bought their stuff, voided the warrenty immediately (so no support calls), and never used their cloud, so didn’t waste their resources. Now they are making it near impossible, and I won’t touch their stuff.

All that said, good luck, your gonna need it.

I5 3470 is old, but its not that bad. Lots of people are homelabing on NUCs which are only very slightly faster. Performance per Watt will be terrible though. (I am on an i7-10710u, and I’ve yet to run out of steam so far - https://cpu.userbenchmark.com/Compare/Intel-Core-i7-10710U-vs-Intel-Core-i5-3470/m900004vs2771 )

It has VTx/VTd, so should be okay for proxmox, what makes you think it won’t work well?