[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #22429 [Applications/Tor Browser]: bridge: Add Lisbeth IPv6 address
#22429: bridge: Add Lisbeth IPv6 address
-----------------------------------------------+--------------------------
Reporter: dgoulet | Owner: tbb-team
Type: enhancement | Status: closed
Priority: Medium | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Normal | Resolution: fixed
Keywords: tbb-bridges TorBrowserTeam201706R | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-----------------------------------------------+--------------------------
Comment (by dcf):
Replying to [comment:4 gk]:
> Replying to [comment:3 dcf]:
> > Here is a patch. I tested the bridge line by itself in a torrc file,
but I wasn't able to test it in Tor Browser on an IPv6-capable system.
> >
> > When Tor Browser tries to use the bridge line on an IPv4-only system,
this is what appears in the log:
> > {{{
> > 06/01/2017 13:06:18.700 [NOTICE] DisableNetwork is set. Tor will not
make or accept non-control network connections. Shutting down all existing
connections.
> > 06/01/2017 13:06:18.700 [NOTICE] Opening Socks listener on
127.0.0.1:9150
> > 06/01/2017 13:06:20.600 [NOTICE] Bootstrapped 5%: Connecting to
directory server
> > 06/01/2017 13:06:20.600 [NOTICE] Bootstrapped 10%: Finishing handshake
with directory server
> > 06/01/2017 13:06:20.600 [WARN] Proxy Client: unable to connect to
2001:470:b381:bfff:216:3eff:fe23:d6c3:443 ("general SOCKS server failure")
> > 06/01/2017 13:06:25.400 [NOTICE] Closing no-longer-configured Socks
listener on 127.0.0.1:9150
> > 06/01/2017 13:06:25.400 [NOTICE] DisableNetwork is set. Tor will not
make or accept non-control network connections. Shutting down all existing
connections.
> > 06/01/2017 13:06:25.400 [NOTICE] Closing old Socks listener on
127.0.0.1:9150
> > }}}
>
> Hrm. That's not good. I assume Tor Browser is randomly choosing one
bridge the next time it starts (again) but we should be smarter here than
making the user believe Tor Browser is broken. dcf: Do you know whether
there is already a ticket anywhere for this issue?
When I did my test, I commented out all bridges except for the IPv6 one.
I'm guessing it would have worked (with only a warning in the log) if I
had left the others uncommented.
I don't know exactly how it works, but Tor Browser seems to choose more
than one bridge. For example, in my browser right now, the log mentions
GreenBelt, Azadi, MaBishomarim, cymrubridge31, Lisbeth, noether,
cymrubridge33, NX01, ndnop5.
In the past, we had a separate `fte-ipv6` option where the IPv6 addresses
were kept. Those IPv6 bridges were removed in #18976.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/22429#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs