marcel
join:2013-02-23
Mississauga, ON | reply to johnwhelan
Re: IPv6 beta I have RT-AC66U same options and I have pretty much given up on getting it to work with Teksavvy. I am not an expert on this stuff so I am not really sure who to blame but although I love my router Documentation on how to set up IPv6 simply sux. I wish it was automatic. I think that's what "DHCP-PD" connection would do if it was supported by Teksavvy. |
|
| It sounds like we need the static IP side but what the values for
WAN IPv6 Address
WAN Prefix Length
WAN IPv6 Gateway
LAN IPv6 Prefix
LAN Prefix Length
LAN IPv6 Address
IPv6 DNS Server 1
IPv6 DNS Server 2
IPv6 DNS Server 3
are I'm unclear. Perhaps someone can translate the terms into Teksavvyish.
Thanks John |
|
Reviews:
 ·TekSavvy DSL
| N66u is easy to configure with TekSavvy.
Yes, you do use "Static IPv6". In the future hopefully this will move to automatic with DHCPv6-PD but for now static is the way it's done.
Configure your PPPoE connection for your @hsiservice.net login first and verify that regular IPv4 works fine, then...
Assuming TekSavvy assigned you:
IPV6 /64: 2607:f2c0:a000:aa::/64
IPV6 /56: 2607:f2c0:f00f:bb::/56
You would fill in the following on your 66u:
WAN IPv6 Address: 2607:f2c0:a000:aa::1
WAN Prefix Length: 64
WAN IPv6 Gateway: 2607:f2c0:a000:aa::1 (same as your address)
LAN IPv6 Prefix: 2607:f2c0:f00f:bb::
LAN Prefix Length: 56
LAN IPv6 Address : 2607:f2c0:f00f:bb::1
So, the WAN is your /64 address with "1" on the end (or could be anything, it's just an assignment you give) and a 64 prefix (hence /64).
The LAN prefix is your /56 without any address (so ending in ::), 56 as the prefix lenght, and your prefix with "1" at the end (or whatever you want) as the LAN address.
You can leave the DNS servers blank as TSI's v4 name servers resolve AAAA without issue and I've found TSI's v6 name servers be a little unreliable.
Once this is done you can go to »test-ipv6.com
If it shows the following:
Your IPv6 address on the public Internet appears to be XXXX
then it works. Hope that helps. |
|
| I now have the IPV6 setup as static with the addresses in.
>Configure your PPPoE connection for your @hsiservice.net login first and verify that regular IPv4 works fine, then...
I'm still running on the old login not the @hsiservice.net so how do I change this?
Thanks John |
|
|
|
Reviews:
·TekSavvy DSL
| said by johnwhelan:I now have the IPV6 setup as static with the addresses in.
>Configure your PPPoE connection for your @hsiservice.net login first and verify that regular IPv4 works fine, then...
I'm still running on the old login not the @hsiservice.net so how do I change this?
Thanks John
On the left where it says WAN, click that.
Change the username to your username @hsiservice.net
Click apply. |
|
| I dug around the WAN settings and eventually stumbled across PPPoE then it was just a matter of dropping in the new userid. So it appears the new userid is both IPv4 and IPV6 which I didn't appreciate.
The test-ipv6.com shows its all working. I did wonder if I might need to play in Win 7 but apparently not.
Many Thanks
Cheerio John |
|
Reviews:
·TekSavvy DSL
| said by johnwhelan:So it appears the new userid is both IPv4 and IPV6 which I didn't appreciate.
Correct. The @hsiservice.net login will give you both traditional IPv4 and IPv6 over PPP natively.
Enjoy. |
|
brad
join:2007-09-06
Etobicoke, ON | reply to johnwhelan
said by johnwhelan:So it appears the new userid is both IPv4 and IPV6 which I didn't appreciate.
Huh? That's what it is supposed to be. Not making any sense. |
|
Reviews:
·TekSavvy DSL
| said by brad:said by johnwhelan:So it appears the new userid is both IPv4 and IPV6 which I didn't appreciate.
Huh? That's what it is supposed to be. Not making any sense. I think he meant appreciate as in 'understand', not that he was unhappy. |
|
marcel
join:2013-02-23
Mississauga, ON | reply to SimplePanda
said by SimplePanda:N66u is easy to configure with TekSavvy.
Yes, you do use "Static IPv6". In the future hopefully this will move to automatic with DHCPv6-PD but for now static is the way it's done.
Configure your PPPoE connection for your @hsiservice.net login first and verify that regular IPv4 works fine, then...
Assuming TekSavvy assigned you:
IPV6 /64: 2607:f2c0:a000:aa::/64
IPV6 /56: 2607:f2c0:f00f:bb::/56
You would fill in the following on your 66u:
WAN IPv6 Address: 2607:f2c0:a000:aa::1
WAN Prefix Length: 64
WAN IPv6 Gateway: 2607:f2c0:a000:aa::1 (same as your address)
LAN IPv6 Prefix: 2607:f2c0:f00f:bb::
LAN Prefix Length: 56
LAN IPv6 Address : 2607:f2c0:f00f:bb::1
So, the WAN is your /64 address with "1" on the end (or could be anything, it's just an assignment you give) and a 64 prefix (hence /64).
The LAN prefix is your /56 without any address (so ending in ::), 56 as the prefix lenght, and your prefix with "1" at the end (or whatever you want) as the LAN address.
You can leave the DNS servers blank as TSI's v4 name servers resolve AAAA without issue and I've found TSI's v6 name servers be a little unreliable.
Once this is done you can go to »test-ipv6.com
If it shows the following:
Your IPv6 address on the public Internet appears to be XXXX
then it works. Hope that helps.
I have almost given up on this, thank you very much this works for my RT-AC66U router as well. I just wish ASUS would give better documentation on how to set this up. |
|
2 edits | reply to SimplePanda
said by SimplePanda:WAN IPv6 Address: 2607:f2c0:a000:aa::1
WAN Prefix Length: 64
WAN IPv6 Gateway: 2607:f2c0:a000:aa::1 (same as your address) On my router, it kicks back the error "IPv6 Address and Default IPv6 Gateway should not be same." This makes sense, and I'm not sure how it could work as written...
The Default IPv6 Gateway is the one missing piece of the puzzle for me since my Cisco apparently doesn't support IPv6CP. |
|
Reviews:
·TekSavvy DSL
| said by bthornhill:said by SimplePanda:WAN IPv6 Address: 2607:f2c0:a000:aa::1
WAN Prefix Length: 64
WAN IPv6 Gateway: 2607:f2c0:a000:aa::1 (same as your address) On my router, it kicks back the error "IPv6 Address and Default IPv6 Gateway should not be same." This makes sense, and I'm not sure how it could work as written... The Default IPv6 Gateway is the one missing piece of the puzzle for me since my Cisco apparently doesn't support IPv6CP.
I know on it's face it shouldn't work. The ASUS firmware seems to require these fields to be filled out but seems to be happy using what is provided by the PPP connection in place.
I can't remember testing V6 over PPP on a Cisco but I -think- I had it working at some point. |
|
| reply to marcel
I think the problem is when IPv6 first started to roll out it was more a technical curiosity than anything else. It was probably fashionable to modify router software which is normally not recommended for ordinary mortals.
It's been around a number of years now but its beginning to gain some traction with end users for pure functionality reasons. IPSec is probably the most important but peer to peer is also becoming important and IPv6 offers some advantages here besides the running out of address space whatever.
Also more home routers support it without modified software.
To move forward and expand to a wider audience it needs simpler clearer documentation which I think has appeared on this thread. Thank you very much.
If someone none technical is told the userid for IPv4 is @teksavvy.com and later IPv6 uses @hsiservice.net there is little reason for them to realise that @hsiservice.net also has IPv4 as well as IPv6.
Also the terminology used by ASUS is not the same as used by Teksavvy.
I used to hire librarians 'cause they were intelligent and cheap and get them to write down the steps in terms they could understand. We had many fewer queries from end users once we did this. The downside was the agency I hired them from was talking to me one day saying they couldn't quite understand what I did with them, they all seemed very happy to work for me but then went off and got jobs as technical writers afterwards.
Cheerio John |
|
brad
join:2007-09-06
Etobicoke, ON | reply to bthornhill
said by bthornhill:said by SimplePanda:WAN IPv6 Address: 2607:f2c0:a000:aa::1
WAN Prefix Length: 64
WAN IPv6 Gateway: 2607:f2c0:a000:aa::1 (same as your address) On my router, it kicks back the error "IPv6 Address and Default IPv6 Gateway should not be same." This makes sense, and I'm not sure how it could work as written... The Default IPv6 Gateway is the one missing piece of the puzzle for me since my Cisco apparently doesn't support IPv6CP. You couldn't use IPv6 over PPP without IPv6CP support. I don't know the specifics of the UI for your router but you're probably setting the v6 connection mode to PPPoE somewhere and that implies the use of IPv6CP. |
|
| Well, according to Cisco it does not support IPv6CP, so their claim of IPv6 support is false, to be blunt.
The router demands the default gateway be entered, so I'm stalled at this point. I'm not going to keep dropping $150 routers playing a guessing game. |
|
brad
join:2007-09-06
Etobicoke, ON | said by bthornhill:Well, according to Cisco it does not support IPv6CP, so their claim of IPv6 support is false, to be blunt.
The router demands the default gateway be entered, so I'm stalled at this point. I'm not going to keep dropping $150 routers playing a guessing game.
Ya, not having IPv6 over PPPoE support would be a pretty big issue for their IPv6 support. |
|
Reviews:
·TekSavvy DSL
| said by brad:said by bthornhill:Well, according to Cisco it does not support IPv6CP, so their claim of IPv6 support is false, to be blunt.
The router demands the default gateway be entered, so I'm stalled at this point. I'm not going to keep dropping $150 routers playing a guessing game.
Ya, not having IPv6 over PPPoE support would be a pretty big issue for their IPv6 support. Seems a pretty big fail on Cisco's part.
I had issues getting 6rd working on a Cisco E4500 as well (Rogers 6rd BR's). Both a D-link and an ASUS worked fine and are very stable but the E4500 wouldn't even get a ping through.
Hell, even an Airport Extreme hacked to work on 6rd by manually calculating the prefixes worked.
Amusing considering the 6rd RFC was written by Cisco. |
|
| reply to TSI Gabe
I recently switched to my @teksavvy.com from my @hsiservice login because of the huge congestions issues with the latter and I am still getting my IPv6 address. Has teksavvy enabled IPv6 for standard logins now? Or is this an oddity?
--
Argue opinions using facts. Not facts using opinions. |
|
| Well you don't "get" an IPv6 address with either; it's all statically-assigned. So this would be something of your doing, not Teksavvy's. |
|
Reviews:
·TekSavvy DSL
| reply to RobinK
said by RobinK:I recently switched to my @teksavvy.com from my @hsiservice login because of the huge congestions issues with the latter and I am still getting my IPv6 address. Has teksavvy enabled IPv6 for standard logins now? Or is this an oddity?
So you're using @teksavvy.com and your V6 address space is still working? You can ping outside and test-ipv6.com works?
Maybe they're finally rolling v6 out to production. |
|
