Understanding IPV6

Is there a good guide to the use of IPV6 in a domestic environment?

In reply to a post by Michael_Chare:

Is there a good guide to the use of IPV6 in a domestic environment?

As a general rule you shouldn't really have to do much. Most modern devices (laptops, tablets and phones) will support it and if your provider has given you a service that supports it, it will usually "just work". What exactly are you trying to do with it?

There is a beginners guide here if you wish to learn how it works:

https://www.youtube.com/watch?v=z7Al3P8ShM8

As Seb says, it will usually just work with supplied ISP routers.

One thing some get concerned about is the public nature of IPv6 addresses. Many of us who tinker with networks have grown used to NAT and that our devices in the home have private IP addresses, so are hidden away, but with IPv6 each device gets a public IP address and this somehow feels insecure. However all ISP routers will have firewalls that default to blocking incoming traffic, so even with a public IPv6 address our devices are protected by the firewall and all incoming traffic is blocked. Only traffic coming back in reply to an outgoing connection is allowed back to our devices.

Also because there are so many addresses, scanning for devices to find them is hard, for example, you will likely have at least 18,446,744,073,709,551,616 possible public IP addresses in your home, and devices don't start at 1, they randomise their address, so its hard for someone to just probe your network.

In reply to a post by Michael_Chare:

Is there a good guide to the use of IPV6 in a domestic environment?

Many parents turn it off at the router, as they rely on things like MAC address to device being sticky to use in firewall rules for content screening or limiting internet access at bedtime. (In theory domestic IPv6 should use the MAC in the address, but the nature of the addresses blow most non-IT people's minds).

Some very large UK ISPs still don't provide IPv6, including mine (Virgin Media), and there are currently no major US / UK internet services that only work on IPv6. However in Asia the opposite is common, without v6 many sites disappear, but these are generally not in English.

In reply to a post by seb:

In reply to a post by Michael_Chare:

Is there a good guide to the use of IPV6 in a domestic environment?

As a general rule you shouldn't really have to do much. Most modern devices (laptops, tablets and phones) will support it and if your provider has given you a service that supports it, it will usually "just work". What exactly are you trying to do with it?

I would just like to learn about IPV6 to the extent that I fully understand how a domestic IPV6 network works. Neither of the two ISPs I have connections to support IPV6 at the moment.

For example to configure one local device I have to use IPV6, I have to choose whether the IPV6 mode should be 'route advertisement', DHCP or manual. I would like to understand the implications of using these alternatives.

There are not really any implications and you can have DHCP and Router Advertisements enabled, however some devices don't support DHCP so Router Advertisements has to be a minimum really. You wouldn't normally ever manually set IPv6 addresses, but you can if you wanted a more memorable one I suppose.

DHCP for IPv4 was a way of managing a very small range of IP addresses on the internal side, perhaps a couple of hundred, and it meant devices got given unique IP addresses.

With IPv6 on your Internal network you would have 18446744073709551615 public IP addresses for any device to choose from, so we no longer need something like DHCP micro managing each IP address, and the device itself can just generate a random one, and the chances of choosing one already in use is very very small, plus devices will check first that no one has the same IP they have randomly picked. The device just needs to know the first 64 bits of the IPv6 address and that is what the router is advertising, and the device can randomly assign the other 64 bits to be a unique address.

Windows uses DHCP as well as RA on IPv6, so if DHCP is enabled for handing out IP addresses, Windows will get one DHCP address and then make up one or more random ones to use on the Internet, this is for security and privacy as it can then discard the address and pick another random one later, so websites have a harder time tracking the device.

So on peer to peer networks (e.g. 3 windows PCs on a home LAN) the idea of managing them by IP (v4) disappears. Not many home routers support DDNS registration (as we have in corporate Windows LANs) so finding a PC by name is going to be a game of broadcast again?

Many parents disable IPv6 so they can control (on a firewall type device) their teenagers access to the internet by time... made harder by mobile devices randomising the MAC address

In reply to a post by jchamier:

So on peer to peer networks (e.g. 3 windows PCs on a home LAN) the idea of managing them by IP (v4) disappears.

When a PC wakes up on my Windows network, all the other machines can connect to it by its name, which is automatically associated with a local IPv4 address in the router's DNS server.

Whether it's possible to do the same with an IPv6 address I don't know, but given no-one is switching off IPv4 anytime soon on their home networks, I assume IPv4 will be suitable for automatic LAN hostname mapping for quite some time.

I suppose I could also look into utilising the static local addresses (IPv6 ULA and link-local addresses), but I have no need.

In reply to a post by Oliver341:

When a PC wakes up on my Windows network, all the other machines can connect to it by its name, which is automatically associated with a local IPv4 address in the router's DNS server.

Do you define manually in your router DNS, or use a DDNS ? I'm used to corporate on-premises AD where DDNS is automatic. The ISP routers I am familiar with have no such thing as a DNS, at best they are proxy to the ISP DNS, and don't resolve for short names (no FQDN).

Whether it's possible to do the same with an IPv6 address I don't know, but given no-one is switching off IPv4 anytime soon on their home networks, I assume IPv4 will be suitable for automatic LAN hostname mapping for quite some time.

Yes, dual-stack is going to live for quite a while.

I suppose I could also look into utilising the static local addresses (IPv6 ULA and link-local addresses), but I have no need.

My ISP doesn't do IPv6, so its all theoretical here. (Virgin Media).

In reply to a post by jchamier:

Do you define manually in your router DNS, or use a DDNS ? I'm used to corporate on-premises AD where DDNS is automatic. The ISP routers I am familiar with have no such thing as a DNS, at best they are proxy to the ISP DNS, and don't resolve for short names (no FQDN).

When a Windows PC is connected to my Sky router, the DNS server on the Sky router automatically creates a DNS record for it.

E.g.
1) I connect PC2, e.g. called "PC2", to my Sky Router
2) The Sky router automatically creates a DNS entry for PC2 and maps it to e.g. 192.168.0.6
3) On PC1 I can then ping PC2 by doing "ping PC2"

I assume pinging PC2 would break if the DNS servers on PC1 are set to e.g. Google DNS instead of the Sky router.