IPv6 when?

[#1]

So you get get security by obscurity.

[#2]

Not really no,  Like I said, XP doesn't support IPV6 so you'll need Vista/7/Linux/OSX (though I think I read that OSX has issues).  Vista/7/Linux has a firewall turned on by default so you get normal security through that.  Most people also use a router which has a built in firewall so you get protection that way.  If anything it'll provide more security because of scanning where it scans by IP going up by 1 each time, although until the entire internet is IPV6 people will have to either be dual stack or use an IPV4 tunnel broker for IPV4 over IPV6.

[#3]

XP Does support IPv6, see http://ipv6int.net/systems/windows_xp-ipv6.html

[#4]

Quote from: avatastic

XP Does support IPv6

With the important omission, which affects anyone using just a DSL modem, that it doesn't support ppp6. Another, slightly less important point, is no support for dhcp6. It could be that someone could provide these via an addon software package but it's something ISPs will have to consider if/when rolling out native ipv6 (ie without 4 to 6 gateways/proxies).

[#5]

Turning on IPV6 isn't something a non-techie would do in Windows XP though, if they did, the XP Firewall does protect the network there although the sort of people who would turn on IPV6 are also the sort who would have anti-virus/firewall protection from 3rd party sources too.

[#6]

Quote from: _CN_

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

Its understandable that much of the interest here is for IPv6 access for broadband connections. However, what about public facing web and email servers?
Anybody running a business will want to remain accessible to the whole world once IPv4 has run out. This point is approaching fast in the Asia-Pacific region.

[#7]

It will be a very long time before someone deploys a public facing web server or email server (other than those deliberatly campaigning for IPv6 use) with only IPv6 access, a very very long time indeed.
Even after addresses have run out there are many ways to stretch, reuse, dual use etc IP addresses.
I'm not suggesting anyone should rest on their laurels because of that, far from it, as things get stretched and reused more we will see cracks and errors arise, but what I do mean is, for general consumer there is no need to panic that in the near future some email or web services will become unavailable to you because Plusnet don't yet support IPv6.

[#8]

I mean that if you have a public facing website you would want it to be accessible from those who only have IPv6 access.... or else you can't do business with them.
In some parts of the world IPv4 depletion means that new connections will be IPv6. If you run a B&B in Yorkshire you would not want to miss the growing Asian market.

[#9]

I can't imagine any ISP, hosting centre or any business providing connectivity forcing people to only use IPv6 for many many years to come.
There is little danger of what you suggest.

[#10]

Websites will be dual stack, IPV4 and IPV6 at the same time.  http://www.thinkbroadband.com for instance are dual stack, an NSLookup gives:
C:\Users\David>nslookup www.thinkbroadband.com
Server:  cdns02.plus.net
Address:  212.159.6.10
Non-authoritative answer:
Name:    www.thinkbroadband.com
Addresses:  2a02:68:1::4
          80.249.99.130
So that website is available via 2 addresses, your IPV4 and 6 which defaults to IPV6 if it's available.
Of course, just putting 2a02:68:1::4 into Google Chrome doesn't do the same as putting in 80.249.99.130, it searches for 2a02:68:1::4.  Anyone with an IPV6 only connection will be able to view thinkbroadband (which has an IPV6 speedtester btw) but also, so will anyone with an IPV4 only connection.

[#11]

Quote from: David

Quote from: richandsian Quote from: David As far as I'm aware, Netgear offer *no* IPV6 enabled routers. I believe my DGND3300 does... unless Netgear were just taking the mickey when they left the configuration page in for it. Quite right, I just checked.  If you head over to www.tunnelbroker.net you can sign up and add the DNS to the 6to4 tunnel and get IPV6 now, although you'll need to notify the site every time you disconnect unless you have a static IP.  Be interesting to know if your router firewall works with IPV6 traffic to, the Netgear site doesn't even mention IPV6 and (if I'm reading this right) the config page is actually hidden? Out of interest, what CPE are you looking at PlusNet?  Thompson, Netgear, Zyxel, Cisco, Billion? [Moderator's note by Jim (Oldjim)  link fixed ]

Just seen this on the Netgear site: http://kb.netgear.com/app/answers/detail/a_id/18631/kw/WNR1000v2

WNR1000v2 Firmware Version 1.1.2.28
New Features:
1. Support IPv6 and passed IPv6 ready logo certificate.

I think this is the router that Plusnet are now shipping for those on the FTTC trial, could those on that trial perhaps be used in a trial for IPv6 at some point in the future?

[#12]

Quote from: benoh

I dont see your v6 prefix in the routing table atm, perhaps you could announce it

Its out there now

[#13]

And it can be reached:
Tracing the route to 2A02:16C8::1
  1 2001:7F8:4:FFFF::2 4 msec 0 msec 4 msec
  2 2001:7F8:4:1::1AD7:1 4 msec 8 msec 12 msec
  3 2001:7F8:4::1AD7:1 4 msec 0 msec 0 msec
  4 2A02:16C8::5 0 msec 4 msec 0 msec
  5 2A02:16C8::1 4 msec 4 msec 4 msec
[corrected address for trace]

[#14]

How can there only be 1 hop between you and Plusnet?

[#15]

adw@avatastic:~$ traceroute6 2A02:16C8::1
traceroute to 2A02:16C8::1 (2a02:16c8::1), 30 hops max, 80 byte packets
 1  2001:41c8:1:5e2c::1 (2001:41c8:1:5e2c::1)  0.670 ms  0.623 ms  0.613 ms
 2  2001:41c8:0:858::2 (2001:41c8:0:858::2)  0.962 ms  1.074 ms  1.209 ms
 3  2001:41c8:0:74::1 (2001:41c8:0:74::1)  7.419 ms  7.485 ms  7.635 ms
 4  lonap.he.net (2001:7f8:17::1b1b:1)  7.617 ms  7.618 ms  7.725 ms
 5  2001:7f8:4::1ad7:1 (2001:7f8:4::1ad7:1)  7.992 ms  8.263 ms  8.140 ms
 6  2a02:16c8::5 (2a02:16c8::5)  184.050 ms  167.199 ms  167.298 ms
 7  2a02:16c8::1 (2a02:16c8::1)  8.059 ms  8.563 ms  8.393 ms

And from my PN connection (via HE tunnel)

[adw@skynet ~]$ 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  34.582 ms  33.859 ms  32.419 ms
 2  gige-g4-6.core1.lon1.he.net  26.022 ms  36.969 ms  28.057 ms
 3  2001:7f8:4::1ad7:1  25.347 ms  26.913 ms  29.016 ms
 4  2a02:16c8::5  28.834 ms  27.009 ms  30.479 ms
 5  2a02:16c8::1  30.974 ms  29.645 ms  26.330 ms

(edited because I was a dingbat and tracing to the wrong address)