Revision 4 as of 2026-11-20 03:22:14

Clear message
Page name: ipv6

[DRAFT] IPv6 Numbering Plan

Why use Unique Local Addresses?

=== Why not Private IPv4 Addresses? ===

  • Many people have always-on VPNs to somewhere else where they might use the same range
  • Of course we also still have those for now for internet access (NAT grrr)

  • Cannot be routed across links if we want that sometime
  • They are all within asingle /64 prefix
  • Really cumbersome to use, as you always have to specify the interface aswell

Why not Global IPv6 Addresses

  • We don't currently have an uplink
  • Nobody gets confused about ULAs only being accessible locally
  • We could loose the global prefix, the ULA prefix we can guaranteed use forever

Format for Unique Local Addresses

fdGG:GGGG:GGGG:LLVS:HHHH:HHHH:HHHH:HHHH

  • GG:GGGG:GGGG global ID as per RFC 4193

  • LL location (e.g. h19, arcade, camp network, ...)
  • V vlan (or similar)
  • S subdivision of prefixes within vlan
  • HHHH:HHHH:HHHH:HHHH host

tiny vlans may also be assigned /64 prefixes, in that case please use the highest available prefix first

Assigned Prefixes and Addresses

  • fdb6:29e0:99a6::/48 ULAs for /dev/lol (subnet assignments MUST be listed here)

    • fdb6:29e0:99a6:1900::/56 for use at Hofgasse 19

      • fdb6:29e0:99a6:1900::/60 primary VLAN

        • fdb6:29e0:99a6:1900::/64 statically assigned addresses (MUST be listed here)

          • fdb6:29e0:99a6:1900::1 firewall

          • fdb6:29e0:99a6:1900::1883 mqtt broker

        • fdb6:29e0:99a6:1901::/64 dynamically assigned addresses (DHCP, SLAAC)