[bitfolk] IPV6 autoconfig broken on dunkel since around 1550Z

Hi, IPv6 autoconfig has been broken on dunkel since about 1550Z. Impact is that if you're on dunkel and rely on autoconfig for IPv6 then your IPv6 will have stopped working. This appears to be due to radvd going into a tight CPU loop, as it does fairly regularly. It does not appear to be a very high quality piece of software, but without any alternative implementation. I added some monitoring to check when radvd reaches >90% CPU, but it seems I misunderstood how to use Nagios's check_procs plugin for CPU monitoring, so it didn't fire. At around 1615Z a customer notified me that their IPv6 wasn't working, and I've been investigating since then. I've since replaced the monitoring of that with one that works. If I kill it and restart it then it will almost certainly start working again, but I want to keep it broken to investigate it and properly test some workarounds. I do recommend that everyone using IPv6 on their VPS does statically configure it. Cheers, Andy -- http://bitfolk.com/ -- No-nonsense VPS hosting