New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
I am also not a native speaker, and because of that, many of my words come out rougher and more direct than intended. The curse of many non-native speakers!
We already got partial answer to this with https://www.spamhaus.org/faqs/combined-spam-sources-css/#css-how-handle-ipv6 url I posted:
What's important to understand here is that /64 isn't chosen by coincidence or because it looks nice. The /64 subnet is both a technical necessity and a practical recommendation to ensure proper IPv6 network operation.
IPv6 addresses are 128 bits long. When you split them into two parts:
IPv6 supports Stateless Address Autoconfiguration (SLAAC), which allows devices to automatically configure their own IP addresses without needing a DHCP server. For SLAAC to work properly:
The device must generate its interface identifier (IID), which is a 64-bit value.
The first 64 bits of the IPv6 address (the prefix) identify the network, while the second 64 bits are used for the device’s unique identifier within that network
This is why the /64 prefix size is critical. It ensures there are exactly 64 bits available for the host identifier, which is needed for proper auto-configuration and the generation of unique interface identifiers.
Using other subnet size could break the functionality of SLAAC and other IPv6 features that rely on a fixed 64-bit host portion.
Now I am going to sleep - I will suffer tomorrow
0 no one needs IPv6
this is a shitpost.
Only if your ISP is stuck in the past (or you pay good $$ to have static IPv4).
Please, read man. There's absolutely no difference between /128 and /64 in term of handling the abuse. Like said for several times, IPv6 is not IPv4. It works fundamentally differently. Forget the old IPv4 mindset...
Example: https://www.spamhaus.org/faqs/combined-spam-sources-css/#css-how-handle-ipv6
Yeah, because multiple NAT layers are solution, right?
@Mumbly I do now understand why /64 is needed. I can get you a gun, we'll shoot together whoever talking on smaller block than a /64 !
I know which LIR/provider to stay away from and recommend against for my next project and friends.
Instead of arguing about random bullshit, this is the most obvious and correct answer.
You should not use smaller than /64 subnets, even for point-to-point links. /64 is used for single LAN and SLAAC. /56 would be the minimal end site assignment while /48 would be for larger sites.
Start with a /64 per server.
Be able to assign a /56 and/or a /48 upon request.
Kind of.. We will not add /128's to drop lists, /64 is the smallest that get added to a drop list.
Annoying that our colo assigned us a /124, but a big part of that I suspect was to prevent it from being used 'normally', to encourage it to be OOB only.