News for hackers. Stuff that matters.

A comment on IPv6-ghost-ship: Using TOTP as part of an AWS EC2 IPv6 address. Parent comment

Re:IPv6-ghost-ship: Using TOTP as part of an AWS EC2 IPv6 ad... by nybble41 on Thursday January 06, 2022 @03:23PM (#29829511)
> Using ULA … the network side of our private internet space is only 6 characters

How do you fit the fixed 8-bit ULA prefix (fd00::/8) plus the 40 random bits you're supposed to use for the Global ID (per RFC 4193) into six hex characters? It should be at least 12, e.g. fdXX:XXXX:XXXX::/48.

As for remembering addresses, yes, just use (m)DNS. You can even set up an mDNS Discovery Proxy[0][1] so that devices which don't support mDNS themselves can resolve the names via regular unicast DNS.

[0] https://www.rfc-editor.org/rfc/rfc8766.html

[1] https://github.com/mkuron/mdns-discovery-proxy

[ Parent | on HN ]
Re:IPv6-ghost-ship: Using TOTP as part of an AWS EC2 IPv6 ad... by reincarnate0x14 on Thursday January 06, 2022 @03:36PM (#29829696)
What few private organizations I've seen working with ULA ... are not using really random global IDs. I'm sure larger scale organizations are following RFC4193 more honestly, but getting V6 going at all versus ever more horrifying NAT contraptions in industrial networks is usually enough of a victory for me.
[ Parent | on HN ]