Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#1795 closed Bug (fixed)

Having IPv6 connectivity breaks IPv4 and NAT traversal

Reported by: JeremyVisser Owned by: jhujhiti
Priority: Normal Milestone:
Component: libtransmission Version: 1.42+
Severity: Major Keywords: ipv6
Cc:

Description

My computer is connected to the IPv4 Internet via a symmetric NAT (UPnP-enabled), and also to the IPv6 Internet through a subnet also routed to the same connection.

Transmission is set to listen on port 51413. When I have IPv6 enabled on my computer, Transmission will only bind to port 51413 on my IPv6 address. Also, Transmission will not attempt to perform UPnP NAT traversal, and cannot see a list of IPv4 peers from the tracker.

I needed to disable IPv6 on my computer to get my torrents to work. Transmission needs to be a good citizen and be able to communicate with IPv4 and IPv6 peers simultaneously.

Environment

  • Transmission 1.50b5 r7815 on Mac OS X v10.5.5

Change History (14)

comment:1 Changed 12 years ago by livings124

  • Resolution set to invalid
  • Status changed from new to closed

That release is too old. Please reopen if this is still an issue with current source.

comment:2 Changed 12 years ago by JeremyVisser

1.50b5 is just over a week old -- doesn't seem very old to me.

But anyways, I'll try a trunk build on my Linux box tomorrow and report back.

comment:3 Changed 12 years ago by livings124

It's very old considering this is being actively developed. A week is a long time.

comment:4 Changed 12 years ago by jhujhiti

I'm going to push a change I made in trunk out to 1.5x tonight. If you're not interested in building trunk or using nightlies, try again with 1.5b6 (assuming we have one)

comment:5 Changed 12 years ago by jhujhiti

  • Milestone set to 1.50
  • Resolution invalid deleted
  • Status changed from closed to reopened

I'm going to reopen this and assign it to myself to make sure it doesn't get overlooked before 1.5. There hasn't been much work on the code that might cause this, so it's probably not really fixed anyway.

comment:6 Changed 12 years ago by jhujhiti

  • Owner set to jhujhiti
  • Status changed from reopened to new

comment:7 Changed 12 years ago by jhujhiti

  • Milestone changed from 1.50 to 1.51

comment:8 Changed 12 years ago by jhujhiti

  • Milestone changed from 1.51 to 1.50

comment:9 Changed 12 years ago by jhujhiti

  • Component changed from Transmission to libtransmission

comment:10 Changed 12 years ago by livings124

JeremyVisser?: Anything to report?

comment:11 Changed 12 years ago by jhujhiti

  • Resolution set to fixed
  • Status changed from new to closed

comment:12 Changed 12 years ago by livings124

  • Milestone 1.50 deleted

comment:13 Changed 12 years ago by JeremyVisser

livings124: Sorry, I am currently sick, so I've been unable to test.

jhujhiti: Why did you mark this as fixed? Which changeset fixed the bug?

comment:14 Changed 12 years ago by jhujhiti

r7839 in trunk and r7847 in 1.5x

Note: See TracTickets for help on using tickets.