Nothing is perfect. Every distribution I used have had bugs at some point.
I would usually wait a while before, maybe until the first point release to upgrade so that there is time to iron out all the teething issues.
The actual problem is only encountered when the raspi-firmware package is (re)configured or when the kernel/initramfs is updated.
Have at look at this: https://wiki.debian.org/DontBreakDebian
I found this to be invaluable when I was borking stuff all the time.
My main draw towards Linux is the exact opposite experience. I have a Linux install that has been carried over three computer and two harddisk changes over 10 years and it’s still as good, or slightly better than it used to be.
My suggestion would be to start with something stable like Debian and read the manual when you want to tinker with it. Especially this: https://wiki.debian.org/DontBreakDebian
I think I misunderstood you. The one I was talking about was a bug in proxmox. If it’s an issues inside lxc, you can replicate the Ubuntu networking stack using nmcli or use systemd-networkd and resolved directly. It behaves identically as far as I know.
Last time I checked this was a known bug. DHCPv6 would even cause many containers to not start or to not get an address.
I understand this part :) I use a fairly complex firewall at work though I only know bits and pieces from reading different manuals. I think the part I didn’t understand was how exactly the routing worked differently in IPv4 vs v6. I get that because NAT happens in IPv4, packets can’t be routed at all without the firewall/router but I wasn’t sure what was the mechanism by which v6 made sure that packets went through the router, especially when you have stuff like v6 DHCP relays.
My ISP dynamically allocates a /64. I don’t even know why they do that.
So even though the device has a public address, the route is through the firewall, hence the ability to filter traffic?
Happy to help :) I have ddns configured with duckdns and it’s been pretty smooth. The only problem will be if you’re behind cgnat.
Why not use dynamic DNS since this isn’t something mission critical?
Debian stable but be careful though, you might never leave after using it for a while :)
It’s so fuckin stable. Way few timeouts too!
I love motion eye for being super simple. It doesn’t have many advanced features but is much less finicky than Zm/shinobi.
I love motion eye for being super simple. It doesn’t have many advanced features but is much less finicky than Zm/shinobi.
I have exactly the same setup 😀
There is a docker container which has transmission and openVPN. The other option is to use any VPN container such as gluetun and route transmission container’s network through that using docker network mode.
Yast. I love zypper and opi but yast is super weird. Like if you want to do things that you can do with yast, you probably know how to do it on terminal.