[tor-bugs] #6757 [Tor Client]: ClientPreferIPv6ORPort not honoured when running with bridges

[Tor Bug Tracker & Wiki]

#6757: ClientPreferIPv6ORPort not honoured when running with bridges
------------------------+---------------------------------------------------
 Reporter:  ln5         |          Owner:                    
     Type:  defect      |         Status:  needs_review      
 Priority:  normal      |      Milestone:  Tor: 0.2.4.x-final
Component:  Tor Client  |        Version:  Tor: 0.2.4.1-alpha
 Keywords:  ipv6        |         Parent:                    
   Points:              |   Actualpoints:                    
------------------------+---------------------------------------------------

Comment(by ln5):

 Replying to [comment:5 nickm]:
 > Replying to [comment:4 ln5]:
 > > Based on the assumption that we want i) a Bridge line with an IPv6
 > > address to imply ClientUseIPv6=1 and b) a Bridge line with an IPv6
 > > address for a given bridge listed before an IPv4 address for the same
 > > bridge to imply ClientPreferIPv6ORPort=1, I suggest two changes:
 >
 > Hm. I'm hoping that ClientUseIPv6 and ClientPreferIPv6ORPort in this
 context are meant bridge-specific, right?  That is, if a bridge has an
 Ipv6 address listed first, we don't necessarily want to prefer IPv6 for
 *all* bridges.

 ClientUseIPv6 is not bridge-specific. It's meant to mean that a client
 might use IPv6 for connecting to first hop, be it a bridge or not. I
 don't think that a user should have to set that if she's configured an
 IPv6 address as a bridge.

 With this patch, ClientPreferIPv6ORPort is not considered at all when
 it comes to picking address family for a bridge with both.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6757#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online