IPv6 bridges (without IPv4 ORPort but IPv4 connectivity)
Hi, I'm running relays on servers which have a single IPv4 address and many IPv6 addresses. I guess this is a common setup in nowadays hosting environments since you get IPv6 addresses for free. I'm wondering whether these additional (currently unused) IPv6 addresses could be usefull to run bridges on them. Even though there are reports that say bridges are blocked on an IP:port basis (not IP only) I would prefere to not use the IPv4 address for the bridge at all since there runs a public relay on it already (something that is blocked already). I would like to run a config with an IPv6 ORPort only. To see whether this is currently supported I read: https://trac.torproject.org/projects/tor/wiki/org/roadmaps/Tor/IPv6 https://trac.torproject.org/projects/tor/wiki/doc/IPv6RelayHowto unfortunately the page reads:
Note that you'll have to have an IPv4 OR port configured as well, or your bridge will bootstrap but leave its clients hanging at 50% (see #4847)
https://trac.torproject.org/projects/tor/ticket/4847 so my planned setup would not work I guess. A workaround would probably be to bind to IPv4 as well and ignore the fact that the IPv4 bridge wont be useable since it runs on the same IP as the public relay, but I'd rather wait for a fix of #4847. #4847 has the milestone set to unknown "0.2.???" If there are other options, please me know.
On 24 Apr 2016, at 02:51, erwin rolf <erwin.rolf@mailbox.org> wrote:
Hi,
I'm running relays on servers which have a single IPv4 address and many IPv6 addresses.
I guess this is a common setup in nowadays hosting environments since you get IPv6 addresses for free.
I'm wondering whether these additional (currently unused) IPv6 addresses could be usefull to run bridges on them.
Even though there are reports that say bridges are blocked on an IP:port basis (not IP only) I would prefere to not use the IPv4 address for the bridge at all since there runs a public relay on it already (something that is blocked already).
I would like to run a config with an IPv6 ORPort only.
To see whether this is currently supported I read:
https://trac.torproject.org/projects/tor/wiki/org/roadmaps/Tor/IPv6
https://trac.torproject.org/projects/tor/wiki/doc/IPv6RelayHowto
unfortunately the page reads:
Note that you'll have to have an IPv4 OR port configured as well, or your bridge will bootstrap but leave its clients hanging at 50% (see #4847)
https://trac.torproject.org/projects/tor/ticket/4847
so my planned setup would not work I guess.
A workaround would probably be to bind to IPv4 as well and ignore the fact that the IPv4 bridge wont be useable since it runs on the same IP as the public relay, but I'd rather wait for a fix of #4847.
#4847 has the milestone set to unknown "0.2.???"
You might be waiting some time, as we've already triaged tasks for the next Tor release 0.2.9, which comes out in 6 months. The relay's IPv4 address may be blocked in some jurisdictions, but not others. So it still could be useful for some users. And the bridge's IPv6 address is far less likely to be blocked, so it will be useful by itself. Please also note that you can have a maximum of 2 relays per IPv4 address (or a relay and a bridge), on different ports. Tim Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP 968F094B ricochet:ekmygaiu4rzgsk6n
> >
https://trac.torproject.org/projects/tor/ticket/4847
so my planned setup would not work I guess.
A workaround would probably be to bind to IPv4 as well and ignore the fact that the IPv4 bridge wont be useable since it runs on the same IP as the public relay, but I'd rather wait for a fix of #4847.
#4847 has the milestone set to unknown "0.2.???"
>
You might be waiting some time, as we've already triaged tasks for the next Tor release 0.2.9, which comes out in 6 months.
The relay's IPv4 address may be blocked in some jurisdictions, but not others. So it still could be useful for some users. And the bridge's IPv6 address is far less likely to be blocked, so it will be useful by itself.
Please also note that you can have a maximum of 2 relays per IPv4 address (or a relay and a bridge), on different ports.
Thanks for that reminder, so I cannot make use of all these unused IPv6 IPs anyway since I would have as many IPv4 IPs currently. It is no problem to wait since they are running relays already, but it is just a pitty that all these IPs are of no use. And last time I checked I was unable to get any IPv6 bridge via https://bridges.torproject.org/ (any pluggable transport). "Uh oh, spaghettios! There currently aren't any bridges available..." hoping for 0.2.10 in 2017.
participants (2)
-
erwin rolf -
Tim Wilson-Brown - teor