26 Oct
2024
26 Oct
'24
8:17 a.m.
On 25/10/2024 23:17, Andy Smith via BitFolk Users wrote:
Hi Simon,
On Fri, Oct 25, 2024 at 09:01:12PM +0100, Simon Kelley via BitFolk Users wrote:
Thanks for that.
Further question: I have an address in my now-deprecated /56 range
configured on my VPS which bitfolk's auto-monitoring checks connectivity
too (or at least it used to). Completely removing use of the /56 is
therefore going to require some changes to that monitoring, I think.
Does the auto-monitoring also check connectivity to the standard ::2
address in the /64? If so, same situation.
Maybe it would be worth defining an address within the new /48 which is
conventionally the address of the VPS, and used for connectivity checking?
Apologies if this is already going to be in the forthcoming wiki entry.
I thought it worth mentioning in case it isn't.
Simon.
I can see the existing /64 and /56 there, but no
new /48.
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
_______________________________________________
BitFolk Users mailing list <users(a)mailman.bitfolk.com>
You're subscribed as <simon(a)thekelleys.org.uk>
Unsubscribe:
<https://mailman.bitfolk.com/mailman/postorius/lists/users.mailman.bitfolk.com/>
or send an email to <users-leave(a)mailman.bitfolk.com>