This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[atlas] [ipv6-wg] What to do with RIPE Atlas probes that have only a ULA as IPv6 address?
- Previous message (by thread): [atlas] [ipv6-wg] What to do with RIPE Atlas probes that have only a ULA as IPv6 address?
- Next message (by thread): [atlas] [ipv6-wg] What to do with RIPE Atlas probes that have only a ULA as IPv6 address?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Andre Keller
ak at list.ak.cx
Thu Mar 26 15:49:38 CET 2015
Hi, On 26.03.2015 15:37, Sanjeev Gupta wrote: > I am part of a team deploying IPv6 in S E Asia, for enterprises in > their offices. As we do not have clarity on who the ISP will be, and > this will change frequently till v6 availability stabilises, use of > ULA is common. A NAT66 device is used much a normal IPv4 NAT gateway; > the NAT66 means that if the upstream IPv6 prefix address changes, all > the PCs do ot end up with new addresses. Why would you bother with NAT66 in this case? I mean using ULA for local traffic (like printing, filesharing, building control etc.) seems fine to me. For global connectivity you could just use SLAAC or DHCPv6 as an additional address? Does it really matter, if these additional addresses change from time to time? Regards André
- Previous message (by thread): [atlas] [ipv6-wg] What to do with RIPE Atlas probes that have only a ULA as IPv6 address?
- Next message (by thread): [atlas] [ipv6-wg] What to do with RIPE Atlas probes that have only a ULA as IPv6 address?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]