SixXS::Sunset 2017-06-06

transporting a subnet to another PoP
[de] Shadow Hawkins on Wednesday, 09 April 2008 13:36:18
Hi there, just recently someone told me that there's a new PoP available in Duesseldorf, which seems to have better latency timings then the one in Hamburg i'm currently at. Probably because it's more then 500km away from it. So long story short I decided to request a second tunnel to check the timings and it seems pretty good. Now i'm wondering if it's possible to request a subnet (i already have one with deham01) and if i reconfigured my setup just remove the old tunnel including the old subnet. From the FAQ i just got that it's not possible to "transfer" the subnet to another PoP. Is anything speaking against what I'm trying to do? Thanks in advance.
transporting a subnet to another PoP
[ch] Jeroen Massar SixXS Staff on Wednesday, 09 April 2008 14:20:32
If you are changing PoPs, you will have to renumber. Thus request a new tunnel and a new subnet. Then delete the old ones.
transporting a subnet to another PoP
[si] Shadow Hawkins on Wednesday, 09 April 2008 16:24:45
Sorry if this is silly (I'm still new to IPv6), but isn't one feature of IPv6 easy (transparent) renumbering ? Or is the "just change the router config" the "easy" part ? :)
transporting a subnet to another PoP
[ch] Jeroen Massar SixXS Staff on Wednesday, 09 April 2008 16:33:13
The easy part is the fact that you should always get a /48. As such you don't have to redesign your network when you go to another ISP. You 'just' have to replace the first 48 bits in all the configuration files and presto. And that is the problem, configuration files with hard-coded IP addresses are all over the place, as such you will have to update them all and first find them. Key to renumbering is thus having them in a known place, then you can just s/oldprefix/newprefix/ and done. But now there is another problem: remote locations. For instance, you have DNS glue, that means you have to notify the remote DNS admins to update these. Or firewall rules and ACL's at a remote company, you need to convince them to update it etc etc etc. Thus while it is a bit easier, as you simply always get that /48, you still need to do the same amount of work in getting it done. For most home networks though, it should not be too difficult to renumber as you will have a minimum amount of configuration files and hopefully kept track of where things are. That is why, as long as you stay with the same PoP, you have a good deal: you just move your tunnel endpoint and presto, all keeps on working.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker