On quinta-feira, 21 de abril de 2016 12:34:50 PDT Mats Wichmann wrote: > On 04/21/2016 12:19 PM, Light, John J wrote: > > I can imagine a server could remember what port/IP it's been running on, > > and if a restart results in a different port or IP, it would announce via > > multicast its new port/IP, identifying itself with its guid. > > > > OTOH, that's a major change. Also, the announcement could be lost, so the > > client would still need to be able to rediscover. > > > > John > > I don't know what people are implementing, but one of the IPv6 schemes lets > you build your address from the mac address, which means it does not > change. I have a couple of systems where that's being done....
https://tools.ietf.org/html/rfc4941 - Privacy Extensions for Stateless Address Autoconfiguration in IPv6 https://tools.ietf.org/html/rfc7217 - A Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address Autoconfiguration (SLAAC) Both are implemented on Linux and privacy extensions are getting enabled by default on modern operating systems. Grepping my syslog since my last reboot, I see: Apr 18 12:26:44 tjmaciei-mobl4 avahi-daemon[1158]: Registering new address record for fd2d:2122:f24:0:35c3:6aff:dc75:dda0 on tap0.*. Apr 18 18:44:32 tjmaciei-mobl4 avahi-daemon[1197]: Registering new address record for fd2d:2122:f24:0:259e:2610:449a:9879 on wlp2s0.*. Apr 20 20:04:06 tjmaciei-mobl4 avahi-daemon[36857]: Registering new address record for fd2d:2122:f24:0:59ce:bc6d:46f3:1a49 on wlp2s0.*. This is even without rebooting. After any reboot, it changes again. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
