Hi, On Fri, Oct 25, 2019 at 11:33:29PM +0000, Michael Sturtz wrote: > The problem with non-routable private ULA addressing is most vendor equipment > doesn't support having a SLAAC or DHCP6 dynamic routable address and a static > ULA address.
You have claimed that before, but I find this hard to believe. In my
experience with various host implementations, having multiple addresses
(multiple SLAAC prefixes or static + SLAAC) works just as one would expect.
Maybe not OpenSolaris, but anything sane out there.
So, which systems exist that cannot handle static + SLAAC?
> For simple home networks I suppose we could have a RFC that proposes the FE80
> address space be used as the "static" address space for SOHO server
> addressing and locating such as local DNS or single server environments or
> the end user equipment could just assume that it would be "static" given the
> common use of EUI-64 for the /64 portion (Windows excepted).
fe80 is not ULA, and using fe80 for mDNS is long-established practice
already :-)
> Right now, with the way it actually works in the field it is very disruptive
> every time the /64 is renumbered by the ISP In my experience this happens
> way too often. An end user should not have to go around and reboot devices,
> hunt around for the new printer IP and so on just because the ISP caused a
> renumber of their automatically assigned /64.
This is why "enter an IPv6 address for a device into anything else" should
be strongly frowned upon. Nobody should need to know the IPv6 address
for a printer in the first place.
mDNS exists, bonjour exists, these things actually work well.
Gert Doering
-- NetMaster
--
have you enabled IPv6 on something today...?
SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
signature.asc
Description: PGP signature
