My home network has a couple of Windows 2012R2 servers and several devices all on an IPV4 network connected to the Internet via an HG659. NAT enables outgoing connections to work. There are a couple of pinholes to allow incoming connections to a website and SMTP.I thought I should move into the IPV6 era. Vodafone now support IPv6, but the problem is that the supplied 'prefix' is not static. The servers need to have static IPV6 addresses, as they do for IPV4, but Vodafone can change your IPV6 prefix which stuffs things up as it is part of the server address. Their note says 'You'll receive a /56 prefix. Currently, we don't offer static IPv6 addresses, although the prefix you receive should persist across router reboots." Maybe so, but I set the whole thing up and it was working, but now Vodafone have changed the prefix. Why? Because they can!I thought that the whole point of IPV6 was that it wouldn't run out of addresses, so why don't Vodafone give us a static prefix at least for the duration of a contract with them? It seems you can't even buy one at the moment. You could buy an IPV4 one, though it was bundled with other stuff and was too expensive, so I used a DDNS for that.There are dire warnings about using the FDxx ULAs out there for IPV6.So, how do I set up an IPV6 network with static addresses for the servers, and allow selective incoming access without having to reconfigure my whole network every time Vodafone decides to change my address? This is a non-trivial task, involving changing server addresses, and altering DHCP to dole out addresses in the new space. (If I don't use my DHCP, the addresses don't get automatically updated in DNS).This may seem nit-picky for a home environment, but it's also the model for our school environment which will need to be done in due course.I could I suppose ditch IPV6 and retire before it becomes compulsory, but I try not to be defeatist!Any ideas or suggestions?
↧