Tunnel question

[smoochict]

Hello,

I've got an allocated tunnel from HE.net but was wondering if this service will continue to be available. even after most ISP's have native ipv6?

[cholzhauer]

I haven't heard an official "end date" but I would assume that after everyone has native IPv6, the service would no longer be needed.

But, it's going to be years and years until everyone has native IPv6 access.

[snarked]

..And even when they do, sometimes they have to terminate it.

My colocation facility offered it for 18 months, and I took it.  However, it stopped when they changed transit providers - to providers that don't support it.  That's where the problem lies.

For example, Verizon, which absorbed UUNet, doesn't even have IPv6 addresses for their name servers let alone transit - and they're a tier 1 provider.  Cogent is pretty clueless too, even though they registered an IPv6 network allocation in 2003 (never implemented).

Don't forget:  Everyone who has an IPv4 allocation also has an IPv6 allocation in "6to4" (2002:://16).  No reason not to use it too.

[cconn]

Hello,

I've got an allocated tunnel from HE.net but was wondering if this service will continue to be available. even after most ISP's have native ipv6?

wow, when most ISPs have native ipv6 we will be lucky if it is still in this decade...maybe I am a pessimist  :D

Cogent is pretty clueless too, even though they registered an IPv6 network allocation in 2003 (never implemented).

Not quite true.  Cogent does offer IPv6 transit services (in Canada even, which is quite a rarity here...).  I do have to say however that their IPv6 peering policy is as arrogant as their v4 history, which in turn causes partial connectivity to what little IPv6 is out there.

Before I turned up the BGP session with HE I had 1,000 fewer prefixes announced to me via Cogent, and of the 3,000 or so prefixes I was receiving, not all were reachable for whatever reason.

HE == total connectivity so far.  I would have to graph whatever it is I might not see through HE (if there even is any) but if there is, Cogent picks up the slack, not the other way around.


Here is a look at my current bgp sum:

v6#show ip bgp ipv6 unicast summary
BGP router identifier 66.xxx.xxx.xx, local AS number XXXXX
BGP table version is 303090, main routing table version 303090
4101 network entries using 639756 bytes of memory
7123 path entries using 541348 bytes of memory
5501/3156 BGP path/bestpath attribute entries using 924168 bytes of memory
5335 BGP AS-PATH entries using 159036 bytes of memory
27 BGP community entries using 648 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
Bitfield cache entries: current 1 (at peak 1) using 32 bytes of memory
BGP using 2264988 total bytes of memory
BGP activity 58123/54022 prefixes, 125189/118066 paths, scan interval 60 secs

Neighbor        V          AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
2001:470:xxxx:xxxx::1
                4       6939   48575    5721   303090    0    0 3d23h        3969
2001:550:xxxx:xxxx::9
                4        174  211771   15953   303090    0    0 1w4d         3153