![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://sh.itjust.works/pictrs/image/15634034-afae-4426-826f-0ba7e2d1adda.png)
I don’t have a good answer for you.
DHCPv6 is pretty well the only good way to have a prefix delegated by your ISP and have it chopped up and deployed in an automated fashion through multiple layers of an edge network. I’m also a real fan of the audit trail in the logs that results from a stateful transaction.
Some background info if you haven’t run into it though is described by this google issue tracker id: https://issuetracker.google.com/issues/36949085. The summary is that one guy at google is obstructing DHCPv6 being implemented on android.
I’ve built out a bunch of IPv6 networks that implement DHCPv6 on the edge. I personally use a whole lot of android devices and none of them get IPv6 addresses, pretty well everything else does. I’m mostly cool with it at this point, eventually the guy who is obstructing IPv6 at google will move on.
I replaced mythtv with tvheadend on the backend and kodi on the frontend like 5 or 6 years ago.
The setup and configuration at the time on mythtv was slanted towards old ( obsolete ) analog tuners and static setup and tvheadend was like a breath of fresh air in comparison where you could point it at a DVB mux or two and it would mostly do what you want without having to fight it.
I’m not sure how much longer I’ll want something that can tune DVB-S2 and DVB-T though. Jellyfin and friends handle everything other than legacy TV better than kodi these days.