Hi Simon, On Fri, Oct 25, 2024 at 09:01:12PM +0100, Simon Kelley via BitFolk Users wrote: I'm sorry, that was my fault. Walked away without pressing return on that particular command line (no customer on talisker was assigned a /48)! It's there for you now. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting

Hi Simon, On Sat, Oct 26, 2024 at 09:17:41AM +0100, Simon Kelley via BitFolk Users wrote: Neither of those checks were actually added automatically. Quite a lot of people just immediately disable IPv6, so I decided to not automatically create monitoring checks on those addresses. Ping checks for the …::2 address of the /64 were added manually on request. Very few customers asked for /56s — I think something like 20 of you — so in those cases (if I remembered) I'd asked for a pingable address inside the /56 and manually added a check against that. This was slightly more important as the way we were doing things it was a bit too easy to forget to route the /56 when moving the VM to a different host. That concern doesn't really apply now as I have moved all IPv6 configuration into the main single config file for each VM, so it is not possible to forget about it. So, all of that was manual and all I can do at the moment is manually change it on request. I would suggest the all zeroes address which is the first usable one in each /48, 2a0a:1100:1xxx::/128. However if I did that now, I expect that more than 95% of VMs would show an alert for this being unreachable so that'd be making a lot of work for myself. Bearing in mind that there's going to be several groups: - Don't care about IPv6 at all, don't want to do anything - Haven't got around to doing the work to make their new /48 reachable, no plans when or if they will do so - Have actually set this up Of those groups the last one will be the smallest and I think they are the only ones who would welcome being contacted about this. I could put in there that if you would like for an IPv6 address to be checked by monitoring you should assign the first usable address, and then our stuff that builds the monitoring configuration could start monitoring that if it begins to respond? Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting

Hi Mike, On Fri, Oct 25, 2024 at 09:18:10PM +0100, Mike Zanker via BitFolk Users wrote: The old one will continue to work but the new configuration is to use fe80::1 as the default gateway, and as you have noted that would be the only way to stop using the deprecated /64 assignment. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting

Hi Mike, On Sat, Oct 26, 2024 at 09:25:44AM +0100, Mike Zanker via BitFolk Users wrote: That is a good start. I will add it to the article (any customer can edit the article so do just add things like this). It depends what one means by "Minimal" I suppose. If it means "least amount of rules" then this is probably it for a default-deny ip6tables firewall. If it means "least amount of things allowed" then it's only certain types of ICMPv6 that are needed and the source address that it comes from is quite specific also. I'm not going to find time to look that up though so if anyone else knows, please just edit it in. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting

Hi Jamie, On Tue, Oct 29, 2024 at 06:45:52PM +0000, Jamie Stallwood via BitFolk Users wrote: There is no intention to ever take away the deprecated IPv6 addresses. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting