ipv6-ops Digest, Vol 159, Issue 1

Jared Mauch jared at puck.nether.net
Wed Oct 23 16:34:29 CEST 2019


You can often disable this on the host.  Much of this is the lack of (or poor) configuration capabilities of the software/OS.  If I know I always want to pick a specific IPv6 address in the same /64 it’s not too hard, but it’s also not as easy to configure without writing your own application.

The general consensus is that you shouldn’t use IP addresses and use some fixed name in the .local subnet and use mDNS to discover the device, but of course this often has it’s own issues.

Lets say I have 2 clothes dryers I’m connecting, I don’t know which one is dryer.local and which is dryer-1.local

- Jared

> On Oct 23, 2019, at 10:26 AM, Michael Sturtz <Michael.Sturtz at PACCAR.com> wrote:
> 
> I have found more problems with the DHCPv6-PD.  The issue is on many home networks where people are using server type hardware such as Windows(TM) networks where DNS is used to locate and secure the network the renumbering event creates major problems as the on premises DHCPv6 server has no way to understand that a renumber event has occurred.  People are very used to the IPv4 RFC 1918 static addressing where nothing on their local internal network will change without notice.  The fact that ISPs can randomly change the internal delegated address without notice is a major problem.  That will confuse people and cause problems especially where a customer has equipment such as Windows or Linux servers or other equipment that requires static addressing or DHCPv6.   I understand that for certain operational reasons ISPs need to renumber addresses however I suggest we discourage the practice.  We also could modify the RFC to require a message to be sent by CPE to all downstream network devices that a network renumber event is being scheduled.  This can be sent as a multicast message that encodes the date that the renumbering will occur.  I realize that we need to understand the security implications of this.  This is just one idea that could smooth the renumbering events when then have to happen for some operational reason.  



More information about the ipv6-ops mailing list