Mele20
Premium
join:2001-06-05
Hilo, HI
| [TWC] IPv6 plans?
I see that Comcast is starting trials this year for a rollout of IPv6 to its residential customers. What and when is TW planning for Road Runner?
I assume my current router does not support IPv6 (Linksy BEFS41 ver 3) as I bought it in November 2003. Does Road Runner have any current support of IPv6 if I had a router that supported it? I am asking because my antivirus vendor has added support for IPv6 in the current version of the product. Because my computer cannot connect to any of the IPv6 addresses for updates and because it tries to connect to those first before trying any IPv4 addresses my updates are taking twice as long now and frequently errors are generated in the log indicating problems with IPv6 and I may have to try more than once to update. Because updates are silent now that means I have to checking the main GUI to see if the update worked. It is getting irritating.
Oceanic DNS servers are giving out IPv6 addresses for my antivirus update servers so is the reason I cannot use my antivirus vendor's IPv6 addresses because of the router not supporting this or what? I still have last year's version of my antivirus on my host XP Pro computer and it does not use IPv6 and my updates on it are just as fast and easy as always. But on my virtual XP and Vista machines, with the current version of my antivirus program, I am experiencing updates taking twice as long and not happening at sometimes because of the attempts to connect to IPv6 addresses. Once the updater finally decides to try IPv4 addresses if the first server is busy (this happens a lot with my antivirus vendor) then the IP6 ones are tried again and finally IP4 at the end and sometimes the updater gives up and there is no update. A couple of minutes later my last year's version of the antivirus on my host computer does the same update in a few seconds and it uses only IPv4 addresses.
--
"The same ferocity that our founders devoted to protect the freedom and independence of the press is now appropriate for our defense of the freedom of the internet. The stakes are the same: the survival of our Republic". Al Gore, The Assault on Reason |
|
whfsdude
Premium
join:2003-04-05
Washington, DC
| TWC is announcing an IPv6 route over its transit AS (AS7843). With that said, it doesn't look like they're aggregating it anywhere inside their regional networks. So you're SOL for native IPv6 connectivity for awhile.
As for AAAA entries - if there is no IPv6 route, the computer shouldn't even try the IPv6 address. If there is a bad route, it will hang and timeout.
My guess would be you have a broken teredo or 6to4 setup. The best thing to do on one of those boxes would be pull up a ipconfig and see if it has a bad ipv6 route.
If it doesn't have anything, you should try running teredo for tunneling on your XP and Vista boxes. |
|
BB User
@charter.com
| reply to Mele20
Unless you use a IPv6 tunnel broker, TWC/RR would have to support it with an firmware upgrade or hardware changeout of your modem (besides all the network updates that would be needed first), and you would have to change your router.
At this point you should probably disable IPv6 in your Windows XP setup, so the software just stops trying to use it.
»IPv6 FAQ »How to turn off ipv6 in xp |
|
Mele20
Premium
join:2001-06-05
Hilo, HI
| I don't use a IPv6 tunnel broker.
I don't have IPv6 installed on XP. But my antivirus updater tries anyway to connect via IPv6 addresses before it tries IP4 ones. It is doing that because Oceanic TW DNS servers on one machine and Level3 Public DNS servers on the other machine are handing out IPv6 addresses for the antivirus update servers as well as IPv4 ones.
I think this is a problem that can be solved only by the antivirus vendor and at this point they are remaining silent even though there are a number threads in their forums about the problem. If this vendor refuses to give us a way to turn off the IPv6 connection attempts then I will probably revert to the previous version of the software that is not capable of using IPv6 or possibly look for another antivirus program.
I supose a third possibility would be to try one of the tunnel brokers (I knew nothing about them until I read the dslr FAQ and links. Thank you for that. I never thought to look there before posting).
--
"The same ferocity that our founders devoted to protect the freedom and independence of the press is now appropriate for our defense of the freedom of the internet. The stakes are the same: the survival of our Republic". Al Gore, The Assault on Reason |
|
RR User
@rr.com | If IPv6 isn't installed, then install IPv6, and see if the errors go away. |
|
RR User
@rr.com
| reply to Mele20
BTW, you've seen these notices from Avira about their update servers being overloaded right?
»forum.avira.com/wbb/index.php?pa···st802308 |
|
Mele20
Premium
join:2001-06-05
Hilo, HI
1 edit | reply to RR User
I installed go6 and the gateway6 utility software installed IPv6 on this XP machine. So, I have this anon connection with a nat traversal tunnel and I don't know how to use it or how to get Avira 9 updater to use it. I tried putting the remote endpoint IP address for go6 connection in Avira's settings for how to connect to the Avira update servers. That just got me an error about improper input. So, I'm quite confused.
Interestingly, Avira updater is taking 3-4 minutes now to update. It was taking 2 minutes before I installed go6 but the long time could be a coincidence. I am talking about a simple one file VDF update that should take less than 20 seconds and does take about 10-15 seconds on my host XP machine with Avira 8.
And yes, I know all about the gigantic update over a week ago that started the overloaded server problem. My Avira 8 couldn't get that at all and I used fusebundle manual update and then it still wouldn't auto update correctly...but all that calmed down several days ago. The servers have not been overloaded for several days and my Avira 8 has been updating twice daily very fast even when the update involves more than a VDF file. But my Avira 9 takes at least twice as long as Avira 8 for the same update and many times, even after the servers stopped being overloaded, can't update at all.
What is happening is that Avira 9 tries all the IPv6 addresses first and I show in the log repeated "error occured iinside the WinINet library" over and over with each IPv6 address attempted. If I am lucky when Avira finally tries the IPv4 addresses I get a connection but many times the first one doesn't work and Avira goes back to trying IPv6 or just gives up. None of this crap happens with Avira 8 because it is not capable of using IPv6 and I never see a error inside WinINet library with it. It does have sometimes severe problems when the servers get overloaded by some gigantic update but the crap with IPv6 is EVERY TIME on Avira 9.
I also don't know quite what to make of IPconfig /all now as it shows IPv6 addresses mixed into my Oceanic RR IPv4 address and some other stuff I was not seeing before. I tried typing one of the IPv6 Avira server addresses in the address bar of Fx3 and that just got me a DNS error so I don't know how to use the tunnel.
Edit: Avira has indirectly acknowledged the problem and is now telling those complaining to use this command to update:
"C:\Program Files\Avira\AntiVir Desktop\update.exe" /DM="0" /NOMESSAGEBOX /receivetimeout=120
Supposedly this command stops Avira 9 from trying to connect to IPv6 addresses. It didn't nothing for me...Avira still tried repeatedly to connect to IPv6 addresses, but at least one user has reported that this command stops that for him and now Avira updates fast and connects fast and only tries IPv4 addresses. Wish that worked for me.
--
"The same ferocity that our founders devoted to protect the freedom and independence of the press is now appropriate for our defense of the freedom of the internet. The stakes are the same: the survival of our Republic". Al Gore, The Assault on Reason |
|
