IPv6 Support

[Aaron]

Originally Posted by nemesis

Any word on native IPv6 support on Linux VPS's yet?

We are getting closer to being able to offer this, there are a few more network upgrades which need to take place before we can implement this. We'll keep everybody posted when it becomes available.

[gnif]

I noticed that breifly after the recent kernel upgrade that I had a valid IPv6 address assigned to three of my hosts, which I could ping, and use... about 15 minutes later these addresses were removed.... why? whats going on?

[Aaron]

Hi gnif,

Not sure how this happened, as none of our VPS nodes have IPv6 capabilities, and parts of our network don't have it yet either. Maybe it was another user on the network assigning these off?

Originally Posted by gnif

I noticed that breifly after the recent kernel upgrade that I had a valid IPv6 address assigned to three of my hosts, which I could ping, and use... about 15 minutes later these addresses were removed.... why? whats going on?

[gnif]

Well, here is the ifconfig for each host, still have it in my bash history:

eth1      Link encap:Ethernet  HWaddr AA:00:AE:1F:85:02  
          inet addr:10.5.1.69  Bcast:10.5.255.255  Mask:255.255.0.0
          inet6 addr: 2002:6f76:a412:2:a800:aeff:fe1f:8502/64 Scope:Global
          inet6 addr: fe80::a800:aeff:fe1f:8502/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:105669 errors:0 dropped:0 overruns:0 frame:0
          TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:21607109 (20.6 MiB)  TX bytes:1942 (1.8 KiB)

eth1      Link encap:Ethernet  HWaddr aa:00:83:29:d7:02  
          inet addr:10.5.1.22  Bcast:10.5.255.255  Mask:255.255.0.0
          inet6 addr: 2002:6f76:a412:2:a800:83ff:fe29:d702/64 Scope:Global
          inet6 addr: fe80::a800:83ff:fe29:d702/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9169731 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7484 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1610807043 (1.5 GiB)  TX bytes:593257 (579.3 KiB)

I was able to ping both of these addresses from an external source briefly, and the machines were able to ping each other

~# ping6 2002:6f76:a412:2:a800:aeff:fe1f:8502
PING 2002:6f76:a412:2:a800:aeff:fe1f:8502(2002:6f76:a412:2:a800:aeff:fe1f:8502) 56 data bytes
64 bytes from 2002:6f76:a412:2:a800:aeff:fe1f:8502: icmp_seq=1 ttl=64 time=0.224 ms
64 bytes from 2002:6f76:a412:2:a800:aeff:fe1f:8502: icmp_seq=2 ttl=64 time=0.254 ms

--- 2002:6f76:a412:2:a800:aeff:fe1f:8502 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.224/0.239/0.254/0.015 ms

[Aaron]

Sounds like someone is broadcasting this on our network. That netblock is IANA reserved for 6-to-4, my guess is for IPv6 tunnel: http://whois.arin.net/rest/net/NET6-2002-1

Originally Posted by gnif

Well, here is the ifconfig for each host, still have it in my bash history:

eth1      Link encap:Ethernet  HWaddr AA:00:AE:1F:85:02  
          inet addr:10.5.1.69  Bcast:10.5.255.255  Mask:255.255.0.0
          inet6 addr: 2002:6f76:a412:2:a800:aeff:fe1f:8502/64 Scope:Global
          inet6 addr: fe80::a800:aeff:fe1f:8502/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:105669 errors:0 dropped:0 overruns:0 frame:0
          TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:21607109 (20.6 MiB)  TX bytes:1942 (1.8 KiB)

eth1      Link encap:Ethernet  HWaddr aa:00:83:29:d7:02  
          inet addr:10.5.1.22  Bcast:10.5.255.255  Mask:255.255.0.0
          inet6 addr: 2002:6f76:a412:2:a800:83ff:fe29:d702/64 Scope:Global
          inet6 addr: fe80::a800:83ff:fe29:d702/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9169731 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7484 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1610807043 (1.5 GiB)  TX bytes:593257 (579.3 KiB)

I was able to ping both of these addresses from an external source briefly, and the machines were able to ping each other

~# ping6 2002:6f76:a412:2:a800:aeff:fe1f:8502
PING 2002:6f76:a412:2:a800:aeff:fe1f:8502(2002:6f76:a412:2:a800:aeff:fe1f:8502) 56 data bytes
64 bytes from 2002:6f76:a412:2:a800:aeff:fe1f:8502: icmp_seq=1 ttl=64 time=0.224 ms
64 bytes from 2002:6f76:a412:2:a800:aeff:fe1f:8502: icmp_seq=2 ttl=64 time=0.254 ms

--- 2002:6f76:a412:2:a800:aeff:fe1f:8502 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.224/0.239/0.254/0.015 ms

[gnif]

no worries, that would make sense and explain why it was on the internal lan , was about to jump for joy that IPv6 was here... damn

[Aaron]

Don't worry, we are working on it! In fact we have the remaining hardware on order to bring our entire AU network to support IPv6! So its on the books, and we are trying to get this up as soon as possible.

Originally Posted by gnif

no worries, that would make sense and explain why it was on the internal lan , was about to jump for joy that IPv6 was here... damn

[PC_Nerd]

So...
Support desk is heading towards some maintenance in order to " upgrade to support IPv6"...

Does this mean that IPv6 will be available for VPS customers any time soon, or am I just that little bit too eager...?

Cheers

[ross]

Hi PC_Nerd,

A little to eager I'm afraid. That notice is in reference to our US network where our Support Desk operates from.

We are upgrading some network infrastructure there, but the issue with vendor software still not supporting it is still a big blocker we need to work through.

[PC_Nerd]

Ahh well - I'll keep my eager eye on the forums for any more news.
Thanks!