Jump to content

IPV6 peers are not being connected to ?!


rafi

Recommended Posts

OS: XP

ubuntu torrent

90/1000 are IPV6 peers in the peers' list

teredo is on

uTorrent: 2.03

I can see logged connection attempts to IPV6 peers but no IPV6 peer is connected to in the peers' tab. (might be a local issue here with teredo).

46614868.th.png

And to another related issue:

I can see IPV6 connection attempts whether net.disable_ipv6 is true or false :( Surly this is a bug!

Link to comment
Share on other sites

Nope ... but I have a good excuse - how should I know you need to do that, if it's not in the help file, cause you didn't update it ? :P

Edit:

Also - I also recommend to log on startup if IPV6 is disabled or not (I see only a line "IPV6 installed" either way)

Link to comment
Share on other sites

true would stop ipv6 from working within utorrent. If you want to use IP v6 addresses then you need to set it to false. I've never used it in windows xp but i know its not installed by default, you will have to either add it with a tunnel broker or some conversion process.

I had used http://gogonet.gogo6.com/ for a while until I heard about the security issues because my isp doesn't yet support it.

Link to comment
Share on other sites

I figured if it was confirmed it would have already been moved to the bug section and not in troubleshooting still. Although I'm still not quite sure where the problem is, as you posted above he doesn't have an external address for ipv6 regardless of functionality in utorrent.

Link to comment
Share on other sites

Well I just went and looked through mine and apparently I should be on this list as well,

[2010-07-24 23:20:02] [2002:dd7e:6758::dd7e:6758]:23018(*torrent): Disconnect: Peer error: A socket operation was attempted to an unreachable network.

Every couple minutes. ipv6 is disabled currently and I had uninstalled gogo6 a couple of weeks ago based on security issues. Didn't notice it until I checked the logs I was still getting full bandwidth with the peers that were left.

If its important all of my ipv6 attempted connects are outgoing, my isp currently does not support native ipv6 and i've disabled my tunnel broker temporarily.

20663 on win7 64 (wrt160n - speedstream modem in bridge mode)

Link to comment
Share on other sites

I figured if it was confirmed it would have already been moved to the bug section...
Firon Wrote:

Did you restart after turning it on/off?

It seems that Firon tests are not confirming it. paintball9: You are using uT 2.2, not 2.03, right ?

...20663 on win7 64

If it is also on Win7 x64 it should be attend to ASAP, since this OS was the main reason they've invented this option for... :(

GTHK: Your screen-shot doesn't show an IPv6 address usable with the outside world.

How do I troubleshoot it (since it is - still... - in the 'troubleshooting; section...) ?

Link to comment
Share on other sites

Win 7 x64 2.0.3.20683, net.disable_ipv6=true.

I see ipv6 peers connected to torrents, as well as constant "Disconnect: Peer error: A socket operation was attempted to an unreachable network" in the log.

Also, IPv6 is installed and Got Teredo Address always comes up when starting utorrent.

I'm not savvy with ipv6 stuff, I don't know what a tunnel broker is for example. I know my isp doesn't support native ipv6, ipv6 is installed and teredo is enabled, but that's all I know.

Any help would be greatly appreciated.

Link to comment
Share on other sites

I know you asked rafi, but I figured i'd run it as well incase it helped,

First query didn't work

C:\Users\*>netsh int ipv6 show state teredo

The following command was not found: int ipv6 show state teredo.

(don't have teredo installed) second returned this

Microsoft Windows [Version 6.1.7600]

Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\*>netsh int ipv6 show address

Interface 1: Loopback Pseudo-Interface 1

Addr Type DAD State Valid Life Pref. Life Address

--------- ----------- ---------- ---------- ------------------------

Other Preferred infinite infinite ::1

Interface 12: isatap.{2DEE5E11-220C-4A89-8427-EC4D006A0DAA}

Addr Type DAD State Valid Life Pref. Life Address

--------- ----------- ---------- ---------- ------------------------

Other Deprecated infinite infinite fe80::5efe:192.168.1.101%12

Interface 16: isatap.{B13D0450-50CC-4516-9E78-AFDF81B95BFC}

Addr Type DAD State Valid Life Pref. Life Address

--------- ----------- ---------- ---------- ------------------------

Other Deprecated infinite infinite fe80::5efe:192.168.187.1%16

Interface 11: Local Area Connection

Addr Type DAD State Valid Life Pref. Life Address

--------- ----------- ---------- ---------- ------------------------

Other Preferred infinite infinite fe80::bd95:ab97:f48a:ad8e%11

Interface 15: isatap.{4EEEEA90-7B0A-41F2-9958-4260FAF7A686}

Addr Type DAD State Valid Life Pref. Life Address

--------- ----------- ---------- ---------- ------------------------

Other Deprecated infinite infinite fe80::5efe:192.168.233.1%15

Interface 13: VMware Network Adapter VMnet1

Addr Type DAD State Valid Life Pref. Life Address

--------- ----------- ---------- ---------- ------------------------

Other Preferred infinite infinite fe80::7037:3032:d0a6:a617%13

Interface 14: VMware Network Adapter VMnet8

Addr Type DAD State Valid Life Pref. Life Address

--------- ----------- ---------- ---------- ------------------------

Other Preferred infinite infinite fe80::6cd1:fa3b:4196:bd76%14

Link to comment
Share on other sites

GTHK:

Member Re: IPV6 peers are not being connected to ?!rafi: Trying to use Teredo? netsh int ipv6 show state teredo & netsh int ipv6 show address

C:\WINDOWS>netsh int ipv6 show teredo -state

Teredo Parameters

---------------------------------------------

Type : client

Server Name : default

Client Refresh Interval : default

Client Port : default

State : offline

Error : secondary server address unreachable

C:\WINDOWS>netsh int ipv6 show address

Querying active state...

Interface 5: Teredo Tunneling Pseudo-Interface

Addr Type DAD State Valid Life Pref. Life Address

--------- ---------- ------------ ------------ ------------------------

Link Preferred infinite infinite fe80::ffff:ffff:fffd

Interface 4: Local Area Connection

Addr Type DAD State Valid Life Pref. Life Address

--------- ---------- ------------ ------------ ------------------------

Link Preferred infinite infinite fe80::21d:7dff:fe9c:9d37

Interface 2: Automatic Tunneling Pseudo-Interface

Addr Type DAD State Valid Life Pref. Life Address

--------- ---------- ------------ ------------ ------------------------

Link Preferred infinite infinite fe80::5efe:192.168.2.3

Interface 1: Loopback Pseudo-Interface

Addr Type DAD State Valid Life Pref. Life Address

--------- ---------- ------------ ------------ ------------------------

Loopback Preferred infinite infinite ::1

Link Preferred infinite infinite fe80::1

I've also installed IPV6 , and I'm getting:

C:\WINDOWS>ping6 ipv6.google.com

Pinging ipv6.l.google.com [2a00:1450:8004::68]

from fe80::21d:7dff:fe9c:9d37%4 with 32 bytes of data:

Reply from fe80::21d:7dff:fe9c:9d37%4: Destination address unreachable.

Reply from fe80::21d:7dff:fe9c:9d37%4: Destination address unreachable.

Reply from fe80::21d:7dff:fe9c:9d37%4: Destination address unreachable.

Reply from fe80::21d:7dff:fe9c:9d37%4: Destination address unreachable.

Ping statistics for 2a00:1450:8004::68:

Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\WINDOWS>

thanks

Link to comment
Share on other sites

  • 2 weeks later...
Have the same problem..

Is it true (the default), and uT still TRIES to connect to IPV6 peers ? (set your logger to show outgoing connections) .

Edit:

I think that maybe I got it... What confused the devs is exactly what confuses us... the NAME they gave this flag/control: net.disabled_IPV6...

If it's true you might thing it is enabled and false - disabled, when in fact it works the opposite way... :P

So, we are confused, and they mixed it up in the code :P ... lol ... This proves the importance of choosing sane names/notations...

The button line - on XP it seems to work in reverse (logged) :

When net.disabled_ipv6 = false - uT does NOT attempt to connect to ipv6 peers

When net.disabled_ipv6 = true - uT DOES attempt to connect to ipv6 peers

Next venison/hotfix - please revert the name of this flag to net.Enable_ipv6, and everything will work fine (on XP) ... :)

Now, on other OSes - I don't know... My bet would be that on Win 7 (X32/X64 ?) it will work strait . But who knows... ;)

Link to comment
Share on other sites

What it's supposed to be based on a name of disable.

net.disable_ipv6 = true -> ipv6 is disabled and ipv6 peers should not be attempted

net.disable_ipv6 = false -> ipv6 is enabled and ipv6 peers should be attempted

Well, as I said - on XP it's reveresed... ;) check it up, and confirm. I can be mistaken too...

my test sequence:

0. enable logging of outgoing connections

1. download ubuntu torrent with "true"

2. see ipv6 peers connect attempts

4 stop.

5. set it to "false"

6. advanced->clear peers' list

7. re-start DL

8. no ipv6 attempts ....

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...