.
On 15/03/2024 13:26, mailop-requ...@mailop.org wrote:
From: Michael Grimm <trash...@ellael.org>
[...]
And, with IPv6, the "entire /64" should be a single subnet. Either OVH is
sharing a /64 amongmultiple customers or OP has another machine that is spamming from
within the same subnet.
That is is a bad IPv6 planning IMHO . Even the smallest type of
"end-user" in that network (a VM) should have a minimum of 1x/64
assigned and at least 1x/56 provisionned).
Can someone talk to them and get them on track?
Sharing a /64 among multiple customers doesn't make sense. It's not like OVH is
in danger of running out of IPv6 space any time soon.
OVH is sharing a /64 subnet among multiple customers since they started their
public cloud project. You are only provided with a single IPv6 address for your
instance. In the years before that, I had had access to an exclusive /64 subnet.
This is what happens if you think IPv4 while designing your IPv6 network. :(
IPv6 here when well planned, will facilite filtering. It is win-win for
everyone; the managers of the resources (OVH in this scenario) and the
rest of the Internet who will have to handle traffic coming from that
network.
--
Willy MANGA
Douala-IX
AS328913 | tt: @DoualaIx | https://www.peeringdb.com/ix/3561
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
