logoalt Hacker News

wernam • today at 4:14 PM • 2 replies • view on HN

NAT64 is for ipv4. How does relate to ipv6 routing?? Also, ULA is non routable and has lower precedence (3) than ipv4 (35), so ipv4 will always be preferred over ipv6 in your configuration


Replies

eqvinox • today at 5:19 PM

> ULA is non routable

ULA is absolutely routable. Are you confusing it with LLA?

> and has lower precedence (3) than ipv4 (35)

This already got changed in https://datatracker.ietf.org/doc/html/draft-ietf-6man-rfc672..., the document is fully done with the RFC editor queue and only waiting for the [SNACBIT] reference to get published.

New preference table:

  Prefix        Precedence Label
  ::1/128               50     0
  $known_local/4x       45    14 (**)
  ::/0                  40     1
  fc00::/7              30    13 (*)
  ::ffff:0:0/96         20     4 (*)
  2002::/16              5     2 (*)
  2001::/32              5     5
  ::/96                  1     3
  fec0::/10              1    11
  3ffe::/16              1    12
  
  (*) value(s) changed in update
  (**) $known_local = the ULA Known-Local IPv6 prefix(es),
  with lengths between /40 and /48 (if any)
  with precedence and labels per the rules in Sec 5.3
➕ show 1 reply
kccqzy • today at 6:19 PM

I was responding to OP’s concern with setting up NAT64 pools using the changing GUA prefix. My fix is to use the well-known prefix. On my network that uses NAT64, IPv4 is only for devices that don’t support IPv6.