| IPv6? So, today is IPv6 World Launch day.
»www.worldipv6launch.org/
According to Telus, they are launching IPv6 permanently today as well.
»about.telus.com/community/englis···rld_ipv6
So, does that mean we can get IPv6 addresses now? Or does it just mean their corporate site has an IPv6 address? |
|
TheMGPremium
join:2007-09-04
Canada
kudos:1 | What it sounds like to me is that they've simply added an IPv6 address to telus.com (making the Telus website IPv6 accessible), nothing more. |
|
| reply to tofusl
That is what it sounds like doesn't it?
However, during previous IPv6 Days it seems like they may have enabled IPv6 to DSL links (maybe).
2011:
»IPV6 Test (bimmerdriver's test)
»World IPV6 Day
2012:
»World IPV6 Launch Day
I'm just starting to learn about IPv6 in any depth. So I'm still not sure about what I'm talking about. I'm still very confused by it all -- although my IPv4 understanding is pretty solid.
Seems like IPv6 addresses support a local-link address (not sure how it figures out the upper bits, but it uses the Hardware MAC address in it's local-link address).
It also seems like it can auto-discover routers using NDP, but how does it get settings like DNS servers? Does Telus support DHCPv6 right now? There's some mention of SLAAC? (Not sure what that is...)
Maybe members w/ more clue can educate. |
|
| reply to tofusl
I've got a ipv6 tunnel through sixxs. I can confirm that when I access telus.com, it uses v6:
2001:56A:3:123::EEEE.80 > 2001:4978:2E1:0:x:x:x:x.48538: tcp 1380
Kind of a bass ackwards way of getting to telus. 1: Desktop to my router (v6-v6) 2: Router to Sixxs via ipv4 (tunneled). 3: sixxs ipv6 to telus ipv6 (native v6).
Will sure be nice when Telus starts providing v6 ip's to home connections. (native v6 to your door).
As far as I'm aware, there isn't really a dhcpv6. Assignment of v6 ip's is handled by RA (router advertisement). My router runs 'radvd', a router advertisement daemon. (Just try that on the actiontec).
The sixxs tunnel routes a whole /48 subnet here. Being that /64 subnets are recommended for lan segments, I have a total of 65,536 subnets of /64 size. I'm using 1 out of 65,536 for my lan. Still trying to figure out what to do with the other 65,535 /64 subnets. |
|
| I have an Actiontec router for Optik and I can't seem to get a tunnelbroker.net IPV6 tunnel thru it. I'm looking forward to native IPV6 support as well.
I suspect that TELUS will go with DHCPv6 when ready. Stateless Address Auto-configuration (SLAAC) will probably work well on the home LAN, but Comcast in the US is using DHCPv6 from what I know.
I did find this link off Google showing some TELUS IPV6 connectivity: »bgp.he.net/AS852 |
|
| reply to tofusl
There is still a relative lack of services available on IPv6 transport, both world wide and on Telus. For example, the root servers have been able to provide DNS lookup on IPv6 for some time, but to my knowledge there are still no Whois servers available.
Most modern routers are dual stack and support both protocols. I suspect that some DSLAM's that support DSL networks are dual stack as well, but I doubt they have been enabled. Very few NAT routers support IPv6, but then again NAT is not necessary with IPv6. Windows Vista and Win7 are both dual stack and come complete with the Teredo Tunnel, which works behind a NAT router that does not support IPv6. By default, the Teredo Tunnel is not functional and must be enabled. To find out how, see:
»www.yellowhead.com/IPv6_How.htm |
|
brad
join:2007-09-06
Etobicoke, ON | said by couttsj:There is still a relative lack of services available on IPv6 transport, both world wide and on Telus. For example, the root servers have been able to provide DNS lookup on IPv6 for some time, but to my knowledge there are still no Whois servers available.
Most modern routers are dual stack and support both protocols. I suspect that some DSLAM's that support DSL networks are dual stack as well, but I doubt they have been enabled. Very few NAT routers support IPv6, but then again NAT is not necessary with IPv6. Windows Vista and Win7 are both dual stack and come complete with the Teredo Tunnel, which works behind a NAT router that does not support IPv6. By default, the Teredo Tunnel is not functional and must be enabled. To find out how, see:
»www.yellowhead.com/IPv6_How.htm
Heh. Whois servers don't really matter for what is initially rolled out but even if they were that hasn't been an issue for quite some time..
whois.arin.net has IPv6 address 2001:500:31::46
whois.arin.net has IPv6 address 2001:500:31::47
whois.arin.net has IPv6 address 2001:500:31::48
whois.ripe.net has IPv6 address 2001:67c:2e8:22::c100:687
whois.apnic.net has IPv6 address 2001:dc0:2001:11::220
Your comment about routers is not true, I can find upwards of 30 routers from the 6-7 major brands (such as Cisco, Netgear, D-Link, Apple, ASUS, Buffalo) the avg consumer buys right now. |
|
| said by brad:Heh. Whois servers don't really matter for what is initially rolled out but even if they were that hasn't been an issue for quite some time..
whois.arin.net has IPv6 address 2001:500:31::46
whois.arin.net has IPv6 address 2001:500:31::47
whois.arin.net has IPv6 address 2001:500:31::48
whois.ripe.net has IPv6 address 2001:67c:2e8:22::c100:687
whois.apnic.net has IPv6 address 2001:dc0:2001:11::220
Your comment about routers is not true, I can find upwards of 30 routers from the 6-7 major brands (such as Cisco, Netgear, D-Link, Apple, ASUS, Buffalo) the avg consumer buys right now.
Your right!!!! The only one that doesn't show one is whois.afrinic.net. Now I can finally finish my IPWhois checker.
As far as the NAT routers are concerned, I guess I should have been more specific. Most NAT routers currently in service do not support IPv6, but that should change over time. |
|
brad
join:2007-09-06
Etobicoke, ON | said by couttsj:Your right!!!! The only one that doesn't show one is whois.afrinic.net. Now I can finally finish my IPWhois checker.
As far as the NAT routers are concerned, I guess I should have been more specific. Most NAT routers currently in service do not support IPv6, but that should change over time.
To a certain degree I agree about CPE in the field but I think you would also be surprised how many people have gone through hardware refreshes over the last 2 years to upgrade to a newer wired or 11n capable wireless router and a lot of those have v6 support out of the box or have newer fw from the OEM vendor. It'll definitely change over time as more customers go through hardware refreshes to newer gear for the 11n or 11ac support. |
|
Reviews:
 ·TELUS
| reply to titan_rw
There is a DHCPv6 (»en.wikipedia.org/wiki/DHCPv6).
I wonder if when Telus finally gets around to offering IPv6 if we will have static ip addresses?
I wish they would get on with this. Lots of customers have routers which could support IPv6 if only they would allocate an address. Even if their DNS servers don't support it, there are alternatives. |
|
brad
join:2007-09-06
Etobicoke, ON | said by bimmerdriver:Even if their DNS servers don't support it, there are alternatives.
The DNS servers as in the recursive resolvers used by Telus clients to resolve FQDN's does not matter for the initial roll out as you can query AAAA records over v4 or v6, but even then v6 enabling their recursive resolvers is a relatively easy thing to do compared to v6 enabling their core IP network / xDSL network and other components. |
|
| reply to brad
said by brad:Heh. Whois servers don't really matter for what is initially rolled out but even if they were that hasn't been an issue for quite some time..
whois.arin.net has IPv6 address 2001:500:31::46
whois.arin.net has IPv6 address 2001:500:31::47
whois.arin.net has IPv6 address 2001:500:31::48
whois.ripe.net has IPv6 address 2001:67c:2e8:22::c100:687
whois.apnic.net has IPv6 address 2001:dc0:2001:11::220
Your comment about routers is not true, I can find upwards of 30 routers from the 6-7 major brands (such as Cisco, Netgear, D-Link, Apple, ASUS, Buffalo) the avg consumer buys right now.
Can't seem to find out where else to ask this question, and you seem to be somewhat knowledgable on the subject, so here goes.
Regardless of the transport method (IPv4/IPv6) used, the arin whois server seems to require the use of the "n" (Network address) option, where the others don't. The arin server requires it for IPv6 addresses as well, but the others choke on it. Is this normal? |
|
