O Canada! > Canadian > TekSavvy > IPv6 beta

reply to TSI Gabe

Re: IPv6 beta

the latest builds of Toastman's tomato build's support single line MLPPP

reply to TSI Gabe
I was a bit surprised to see my city borough and postcode in my "whois" information for the netblock that was assigned to me. When I e-mailed dnsadmin@, I was told that since it's a beta service, we cannot change any dns/record information.

Does anyone know why the postcode is made public? I only found this old unresolved thread about the issue:
»whois info for Teksavvy IPv6 addresses

In terms of protecting our privacy, this is really not ideal.

Other than that, the service works well!

I configured it on my Debian router at home and wrote a short howto in french:
»www.bidon.ca/fr/random/2012-03-1···e-debian

In short, if you have a router which does IP forwarding, which is the normal way to handle traffic (net.ipv6.conf.all.forwarding=1 in /etc/sysctl.conf), your router will not accept 'route advertisements' (RA). You will have to assign an IP from the /56 to your router, and setup a default route to the ppp0 device. Then configure radvd to distribute IPs to your local network (ex: 2607:f2c0:f00f:aa00::/64, if your block assigned was 2607:f2c0:f00f:aa00::/56, where 2607:f2c0:f00f:aa00::/64 is the first subnetwork you can allocate, from aa00 to aaff ).

reply to TSI Gabe
To those that have the WRT54GL router, and are looking for a newer tomato firmware that supports Ipv6, I highly recommend the "tomato-K26-1.28.7821MIPSR1-Toastman-ND-MiniIPv6.trx" mod found at »www.4shared.com/dir/v1BuINP3/Toa···lds.html.

It's very stable.

reply to TSI Gabe
*originally posted in Teksavvy Direct, but was told to poste in IPv6 forum for all IPv6 issues*

The PPPOE login I got after posting an IPv6 request in the direct forums only gets a dynamic IPv4 address. Is this normal?

I tried both in Linux and Windows. In Windows, if I leave IPv6 and IPv4 enabled on the PPPOE connection, I get a dynamic IPv4 address, and a link-local (fe80) IPv6 address. If I remove IPv4 from the connection properties, leaving only IPv6, the PPPOE connection fails while authenticating.

I used to be able to connect just fine with this IPv6 login up until I upgraded my account to DSL 12 service and TSI shuffled my logins around (asked me to change logins 2-3 times for my main pppoe account), and my IPv6 login hasn't worked since then.

Personally, unless the connection procedures have changed since then, I believe my IPv6 login was probably messed up by TSI, but they refused to help me in the direct forums, stating I should post about this issue here...

Any help or tips would be appreciated! Thanks!

Well, I didn't change anything on my side. The problem only showed up when I upgraded to DSL12 and Teksavvy shuffled my login ID's 2-3 times.

Originally, my IPv6 login was user@hsiservice.net, and my IPv6 IP would get auto-negotiated automatically upon connecting. My IPv4 login w/ static IP was user@dslinternet.ca

When I upgraded to DSL12, Teksavvy told me to use "useratdslinternet.ca@teksavvy.com" to login for PPPoE, however, this was a dynamic IPv4. I called them back to let them know I no longer had my IPv4 static IP. They "fixed" it and said to now login with "user@hsiservice.net" (which used to be my IPv6 login), however, this still didn't have my old static IPv4 address, so I called them back and they finally fixed my IPv4 static IP and told me to login with what was my static IPv4 login originally (user@dslinternet.ca). This fixed my IPv4 static IP problem.

However, since that day, my IPv6 no longer works. Most likely, when they shuffled my login accounts around while trying to fix my static IPv4 issue, they probably removed my IPv6 option/setting from my account. HOWEVER, I can't get anyone to confirm or look into this because I keep getting friggin stonewalled both on the phone and in the Teksavvy Direct forums by reps saying "IPv6 is not supported. Ask in the IPv6 forums."

It's really annoying because it worked seamlessly for months before that, and it's probably just a checkbox they removed somewhere but it seems nobody can be bothered to look.

Actually, I get the distinct impression that this isn't a checkbox anywhere, which is where the problem is and why this is still a beta. They have the basic technical infrastructure, but I suspect they are still working on the internal toolset to be updated to support IPv6. Right now IPv6 is probably added manually to accounts, which is why it's a bit of a crapshoot depending on who does it. Keep in mind that while the old knowledgable TSI team still exists they're a bit diluted among the number of newer, greener team members they've had to bring on lately.

Growing pains are good pains, in the end, but it does show sometimes.

reply to TSI Gabe
My router has gotten an IPv6 address but its using an address from the /64 address space for it's internet IP as well as it has no DNS server listed. Addresses are not being handed out to the PCs inside my network.

Router is set up to automatic IPv6 (native) mode. Am I doing something wrong here or was my account set up wrong?

The standard for IPv6 is to assign the router interface IP statically.

As much as I'd love to statically set an IPv6 address, that isn't an option. Its automatic or IPv6 tunnel. Also shouldn't the interface take the /56 space?

I'm still by far an IPv6 noob, but if your /56 is 2001:1234:5678:10::/56, you can set a static address for any of your devices within that range.

eg:
2001:1234:5678:10::1/64
2001:1234:5678:10::c0ff:ee/64
etc etc

reply to Daxx
How is setting it statically not an option? If you can get it automatically you can set it yourself. Use the ::1/56 address and then set the inernal hosts to use the RA to stateless autoconfig.

reply to TSI Gabe
I got all up and running last night, got IP's on my PC's and I could ping my router ip6 address. I wasn't getting any DNS, nor could I access ipv6.netflix.com or test-ipv6.com

I'll post more updates this evening after I do some honey-do

reply to TSI Gabe
Is this available in the west yet?

reply to TSI Gabe
Talking about crapshoot...
I called TSI two days ago to get an IPv6 native login and I got one @wiredhighspeed.com
But little else...
On advice on the teksavvy forum, I flashed my Cisco e3000 with DD-WRT v.24 and I enabled IPv6 and Radvd but I have no Idea what to do next.
Obviously the result is less than stellar because when I run Test IPv 6 I get 0/10 because my service is running Teredo.

Should I just revert my E3000 back to Cisco firmware and then try Tomato or are there some steps and information I was not told about that need filling in i.e addresses , scripts etc?

DCW

If you are using Teredo, then Windows is doing it's own thing. You should remove all those extra IPv6 methods from your Windows machine, unless you need them for some other reason. All you need to use the TS IPv6 is native IPv6 support added to your NIC.

You can use netsh from CLI to remove Teredo etc.
--
Matt

Tx Matt fro your response.
I did remove teredo on both a vista ultimate and a 7 machine but the problem remains. I have no NATIVE ipv6 connection...
The person who could REALLY help me HAS SUCCESSFULLY flashed DD-WRT on his router and has native Ipv6 working on TSI dsl ... everything else is not going to help unless I can ascertain that the flashing on my router was worth it or not...

from IPv6 test site:
"No IPv6 address detected [more info]

You appear to be able to browse the IPv4 Internet only. You will not be able to reach IPv6-only sites.

Your DNS server (possibly run by your ISP) appears to have IPv6 Internet access.

Thanks again

DCW

reply to didcrywolf

reply to didcrywolf
Yeah, mine is working with Cisco gear, so I'm not sure on the DD-WRT setup. I have WRT54G running DD-WRT but it is just for wireless AP so no radvd running.