IPv6 when?

[#1]

2001:7f8:4:1::1ad7:1 is one of the two LINX interfaces for PN.
The PN allocation is 2a02:16c8::/32 and I guessed there would be something on 2a02:16c8::1

[#2]

Quote from: avatastic

I can't get a trace from my HE tunnel however.

I can...

C:\Users\David>tracert 2A02:16C8::1
Tracing route to 2a02:16c8::1 over a maximum of 30 hops
  1   252 ms     6 ms     7 ms  2001:470:1f09:611::
  2    64 ms    53 ms    52 ms  *****.tunnel.tserv5.lon1.ipv6.he.net [2001:47
0:1f08:611::1]
  3    69 ms    71 ms    46 ms  gige-g4-6.core1.lon1.he.net [2001:470:0:67::1]
  4    77 ms    50 ms    57 ms  2001:7f8:4::1ad7:1
  5    55 ms    47 ms    50 ms  2a02:16c8::5
  6    49 ms    49 ms    47 ms  2a02:16c8::1
Trace complete.

Maybe HE just needed a refresh which has occurred now?

[#3]

For some reason I was tracing to the 2nd hop in the initial trace...

traceroute6 2A02:16C8::1
traceroute6 to 2A02:16C8::1 (2a02:16c8::1) from 2001:470:1f08:5f3::2, 64 hops max, 12 byte packets
 1  avatastic-1.tunnel.tserv5.lon1.ipv6.he.net  27.573 ms  96.233 ms  28.282 ms
 2  gige-g4-6.core1.lon1.he.net  41.559 ms  22.478 ms  39.391 ms
 3  2001:7f8:4::1ad7:1  31.493 ms  25.121 ms  25.562 ms
 4  2a02:16c8::5  25.285 ms  40.893 ms  22.865 ms
 5  2a02:16c8::1  85.455 ms  100.569 ms  31.932 ms

From my HE tunnel.

[#4]

Looks good from here
bohara@titan> traceroute6 2a02:16c8::1                                                                              ~
traceroute to 2a02:16c8::1 (2a02:16c8::1), 30 hops max, 80 byte packets
1  gw.ipv6.guestsrv.nsrp.ripe.net (2001:67c:2e8:3::1)  0.914 ms  1.126 ms  1.115 ms
2  gw.ipv6.transit.nikrtr.ripe.net (2001:610:240:101::1:1)  2.085 ms  2.077 ms  2.064 ms
3  20gigabitethernet1-3.core1.ams1.ipv6.he.net (2001:7f8:1::a500:6939:1)  4.280 ms  11.007 ms  4.477 ms
4  10gigabitethernet1-4.core1.lon1.he.net (2001:470:0:3f::1)  11.454 ms  11.444 ms  11.431 ms
5  2001:7f8:4::1ad7:1 (2001:7f8:4::1ad7:1)  12.402 ms  12.396 ms  12.616 ms
6  2a02:16c8::5 (2a02:16c8::5)  12.355 ms  11.318 ms  11.433 ms
7  2a02:16c8::1 (2a02:16c8::1)  11.908 ms  12.384 ms  12.617 ms

[#5]

I don't know if any of the PN bods are able to comment but will there be an IPv6 trial at any point? If so - [waves hand in air] 

[#6]

Yeah there will, no dates set yet though but we'll be looking for a few triallists so if you already have IPv6 capable hardware the best place to let us know is this thread and we'll keep you updated when it's nearer the time.

[#7]

Modem - Netgear DM111P
Router - Asrock A330GC running FreeBSD (amd64) and IPv6 enabled ppp
Current IPv6 access - TunnelBroker.net
Interested in trailing - Yes! (in case my previous posts on this matter were unclear)

[#8]

Quote from: dave

Yeah there will, no dates set yet though but we'll be looking for a few triallists so if you already have IPv6 capable hardware the best place to let us know is this thread and we'll keep you updated when it's nearer the time.

Me

[#9]

Quote from: dave

Yeah there will, no dates set yet though but we'll be looking for a few triallists so if you already have IPv6 capable hardware the best place to let us know is this thread and we'll keep you updated when it's nearer the time.

Me too. I'm already online with HE's Tunnelbroker service, and I use a Linux box (actually Xen VM) as a router.

[#10]

Nice one guys, I've just started compiling a list which I will add to from anyone else who posts here.
Jojo

[#11]

I have an ADSL modem which is independent of PPP (Point-to-Point Protocol) and thus should work with IPv6. I would be interested in trying that.
Does it matter that my exchange is 20CN with no current planned date for 21CN ?

[#12]

IPV6 is just a protocol, doesn't matter if you're on dialup, adsl, asdl2 or fibre, cept for speeds.
I'd like to add my name to the list, Cisco 877W so IPV6 ready.

[#13]

Hi
Hopefully mid-to-end April we will be ready to start testing with real end-users.  Our aim is to be ready for participation in World IPv6 Day (8 June 2011), not just making our website available but to have broadband users enabled too.

[#14]

I was just checking what I'd need to change to switch from a tunnel to a PN system, seems pretty simple.

ipv6 unicast-routing
!
interface Vlan1
   ipv6 address 2001:8B0:xxxx:1::1/64
!
interface Dialer1
   ipv6 enable
!
ipv6 route ::/0 Dialer1

Though I have my ipv6 address on BVI1 not VLAN1 (for Wireless) though on older firmwares putting it on BVI1 will break it (past experience, luckily I have a console cable to fix my mistakes ;D)

[#15]

Quote from: _CN_

A blog will be posted in the coming weeks, this will include our plan etc.

I'd look forward to it.
Even if its still early days, and not everything is yet tied down, such a blog may be helpful and interesting now. There will be increasing public awareness as IPv6 day approaches and early adopters will want to prepare for whats going to happen next.