Hello everyone
I tried the Internet of things to get an answer, but either I'm too stupid to find it or it isnt there (haha, good joke)
Sorry if this was asked a 100 times before...
I have a 1gbit symmetric connection at home and would like to donate 100mbit with my raspberry pi 3 model b. Since it has a 100mbit Network Interface, I'm limited to that anyways.
What Settings do I Need in my torcc to get the Maximum Speed? At the Moment I entered 12 Mbytes - which Shows up at 96 mb/s in Arm - is that correct and my understanding of things is just the opposite? Max Speed, I think, should be 12.7mb/s for a 100mbit Connection?
Sorry for bothering and thanks for the pointers.
Oh and since I'm bugging you anyways - would it be useful to add ORPort [IPv6] as well? (same port as for 4 i guess?)
On Wed, 12 Oct 2016 07:18:56 +0200 Manny felich@posteo.de wrote:
I have a 1gbit symmetric connection at home and would like to donate 100mbit with my raspberry pi 3 model b. Since it has a 100mbit Network Interface, I'm limited to that anyways.
What Settings do I Need in my torcc to get the Maximum Speed? At the Moment I entered 12 Mbytes - which Shows up at 96 mb/s in Arm - is that correct and my understanding of things is just the opposite? Max Speed, I think, should be 12.7mb/s for a 100mbit Connection?
mb is not a thing that exists; Mb is megabits: https://en.wikipedia.org/wiki/Megabit MB is megabytes: https://en.wikipedia.org/wiki/Megabyte
What you entered in torrc is currently correct. But since your board has a 100 Mbit interface anyway, it would be better if you just omit the bandwidth limit line entirely.
Also, actually hit anything remotely close to 100 Mbit, you'll absolutely have to run two instances of Tor. The Raspberry Pi 3 has 4 CPU cores, but each core on its own is not very fast. One copy of Tor only uses about 1 to 1.3 cores, so to fully utilize your hardware you need more than one. Ideally you'd set up four, but the Tor network will only accept two running from the same IPv4 address. It appears that these days there's a built-in script for that, see "man tor-instance-create".
The hardware in your raspberry is way too weak to be able to push 100 Mbit/s.
My guess is that Atlas will show somewhere just below 1 MByte for your relay.
I have tried to find cost effective hardware for a relay that is able to push around 100 Mbit/s. All the options I have looked at turned out to be a bit too expensive for my taste (and wallet). Either the initial cost or the energy usage is too high for such hardware for my purposes.
________________________________ From: tor-relays tor-relays-bounces@lists.torproject.org on behalf of Volker Mink volker.mink@gmx.de Sent: 12 October 2016 09:09 To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] RPi Relay Maximum Speed
So the best would be to use two raspis or your old gaming-workstation - depends on the costs for energy
Gesendet: Mittwoch, 12. Oktober 2016 um 07:55 Uhr Von: "Roman Mamedov" rm@romanrm.net An: Manny felich@posteo.de Cc: "Tor relays" tor-relays@lists.torproject.org Betreff: Re: [tor-relays] RPi Relay Maximum Speed On Wed, 12 Oct 2016 07:18:56 +0200 Manny felich@posteo.de wrote:
I have a 1gbit symmetric connection at home and would like to donate 100mbit with my raspberry pi 3 model b. Since it has a 100mbit Network Interface, I'm limited to that anyways.
What Settings do I Need in my torcc to get the Maximum Speed? At the Moment I entered 12 Mbytes - which Shows up at 96 mb/s in Arm - is that correct and my understanding of things is just the opposite? Max Speed, I think, should be 12.7mb/s for a 100mbit Connection?
mb is not a thing that exists; Mb is megabits: https://en.wikipedia.org/wiki/Megabit MB is megabytes: https://en.wikipedia.org/wiki/Megabyte
What you entered in torrc is currently correct. But since your board has a 100 Mbit interface anyway, it would be better if you just omit the bandwidth limit line entirely.
Also, actually hit anything remotely close to 100 Mbit, you'll absolutely have to run two instances of Tor. The Raspberry Pi 3 has 4 CPU cores, but each core on its own is not very fast. One copy of Tor only uses about 1 to 1.3 cores, so to fully utilize your hardware you need more than one. Ideally you'd set up four, but the Tor network will only accept two running from the same IPv4 address. It appears that these days there's a built-in script for that, see "man tor-instance-create".
-- With respect, Roman _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Remember, a relay has to download and upload as well, so your 100Mbps link would really only be able to _relay_ at 50Mbps anyway.
On Oct 12, 2016 4:17 AM, "Farid Joubbi" joubbi@kth.se wrote:
The hardware in your raspberry is way too weak to be able to push 100 Mbit/s.
My guess is that Atlas will show somewhere just below 1 MByte for your relay.
I have tried to find cost effective hardware for a relay that is able to push around 100 Mbit/s. All the options I have looked at turned out to be a bit too expensive for my taste (and wallet). Either the initial cost or the energy usage is too high for such hardware for my purposes.
*From:* tor-relays tor-relays-bounces@lists.torproject.org on behalf of Volker Mink volker.mink@gmx.de *Sent:* 12 October 2016 09:09 *To:* tor-relays@lists.torproject.org *Subject:* Re: [tor-relays] RPi Relay Maximum Speed
So the best would be to use two raspis or your old gaming-workstation - depends on the costs for energy
*Gesendet:* Mittwoch, 12. Oktober 2016 um 07:55 Uhr *Von:* "Roman Mamedov" rm@romanrm.net *An:* Manny felich@posteo.de *Cc:* "Tor relays" tor-relays@lists.torproject.org *Betreff:* Re: [tor-relays] RPi Relay Maximum Speed On Wed, 12 Oct 2016 07:18:56 +0200 Manny felich@posteo.de wrote:
I have a 1gbit symmetric connection at home and would like to donate 100mbit with my raspberry pi 3 model b. Since it has a 100mbit Network Interface, I'm limited to that anyways.
What Settings do I Need in my torcc to get the Maximum Speed? At the Moment I entered 12 Mbytes - which Shows up at 96 mb/s in Arm - is that correct and my understanding of things is just the opposite? Max Speed, I think, should be 12.7mb/s for a 100mbit Connection?
mb is not a thing that exists; Mb is megabits: https://en.wikipedia.org/wiki/Megabit MB is megabytes: https://en.wikipedia.org/wiki/Megabyte
What you entered in torrc is currently correct. But since your board has a 100 Mbit interface anyway, it would be better if you just omit the bandwidth limit line entirely.
Also, actually hit anything remotely close to 100 Mbit, you'll absolutely have to run two instances of Tor. The Raspberry Pi 3 has 4 CPU cores, but each core on its own is not very fast. One copy of Tor only uses about 1 to 1.3 cores, so to fully utilize your hardware you need more than one. Ideally you'd set up four, but the Tor network will only accept two running from the same IPv4 address. It appears that these days there's a built-in script for that, see "man tor-instance-create".
-- With respect, Roman _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Everyone should have full duplex by now.
So he has 200 mbit on a fast ethernet port.
Sent from my iPad
On 12 Oct 2016, at 14:20, Tristan supersluether@gmail.com wrote:
Remember, a relay has to download and upload as well, so your 100Mbps link would really only be able to _relay_ at 50Mbps anyway.
On Oct 12, 2016 4:17 AM, "Farid Joubbi" joubbi@kth.se wrote: The hardware in your raspberry is way too weak to be able to push 100 Mbit/s. My guess is that Atlas will show somewhere just below 1 MByte for your relay.
I have tried to find cost effective hardware for a relay that is able to push around 100 Mbit/s. All the options I have looked at turned out to be a bit too expensive for my taste (and wallet). Either the initial cost or the energy usage is too high for such hardware for my purposes.
From: tor-relays tor-relays-bounces@lists.torproject.org on behalf of Volker Mink volker.mink@gmx.de Sent: 12 October 2016 09:09 To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] RPi Relay Maximum Speed
So the best would be to use two raspis or your old gaming-workstation - depends on the costs for energy
Gesendet: Mittwoch, 12. Oktober 2016 um 07:55 Uhr Von: "Roman Mamedov" rm@romanrm.net An: Manny felich@posteo.de Cc: "Tor relays" tor-relays@lists.torproject.org Betreff: Re: [tor-relays] RPi Relay Maximum Speed On Wed, 12 Oct 2016 07:18:56 +0200 Manny felich@posteo.de wrote:
I have a 1gbit symmetric connection at home and would like to donate 100mbit with my raspberry pi 3 model b. Since it has a 100mbit Network Interface, I'm limited to that anyways.
What Settings do I Need in my torcc to get the Maximum Speed? At the Moment I entered 12 Mbytes - which Shows up at 96 mb/s in Arm - is that correct and my understanding of things is just the opposite? Max Speed, I think, should be 12.7mb/s for a 100mbit Connection?
mb is not a thing that exists; Mb is megabits: https://en.wikipedia.org/wiki/Megabit MB is megabytes: https://en.wikipedia.org/wiki/Megabyte
What you entered in torrc is currently correct. But since your board has a 100 Mbit interface anyway, it would be better if you just omit the bandwidth limit line entirely.
Also, actually hit anything remotely close to 100 Mbit, you'll absolutely have to run two instances of Tor. The Raspberry Pi 3 has 4 CPU cores, but each core on its own is not very fast. One copy of Tor only uses about 1 to 1.3 cores, so to fully utilize your hardware you need more than one. Ideally you'd set up four, but the Tor network will only accept two running from the same IPv4 address. It appears that these days there's a built-in script for that, see "man tor-instance-create".
-- With respect, Roman _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Last I heard, the Raspberry Pi was only capable of 100Mbps because the ethernet port is on the same bus as the USB ports, and the chipset used only supports 100Mbps. I could be wrong though.
On Oct 12, 2016 7:42 AM, "Markus Koch" niftybunny@googlemail.com wrote:
Everyone should have full duplex by now.
So he has 200 mbit on a fast ethernet port.
Sent from my iPad
On 12 Oct 2016, at 14:20, Tristan supersluether@gmail.com wrote:
Remember, a relay has to download and upload as well, so your 100Mbps link would really only be able to _relay_ at 50Mbps anyway.
On Oct 12, 2016 4:17 AM, "Farid Joubbi" joubbi@kth.se wrote:
The hardware in your raspberry is way too weak to be able to push 100 Mbit/s.
My guess is that Atlas will show somewhere just below 1 MByte for your relay.
I have tried to find cost effective hardware for a relay that is able to push around 100 Mbit/s. All the options I have looked at turned out to be a bit too expensive for my taste (and wallet). Either the initial cost or the energy usage is too high for such hardware for my purposes.
*From:* tor-relays tor-relays-bounces@lists.torproject.org on behalf of Volker Mink volker.mink@gmx.de *Sent:* 12 October 2016 09:09 *To:* tor-relays@lists.torproject.org *Subject:* Re: [tor-relays] RPi Relay Maximum Speed
So the best would be to use two raspis or your old gaming-workstation - depends on the costs for energy
*Gesendet:* Mittwoch, 12. Oktober 2016 um 07:55 Uhr *Von:* "Roman Mamedov" rm@romanrm.net *An:* Manny felich@posteo.de *Cc:* "Tor relays" tor-relays@lists.torproject.org *Betreff:* Re: [tor-relays] RPi Relay Maximum Speed On Wed, 12 Oct 2016 07:18:56 +0200 Manny felich@posteo.de wrote:
I have a 1gbit symmetric connection at home and would like to donate 100mbit with my raspberry pi 3 model b. Since it has a 100mbit Network Interface, I'm limited to that anyways.
What Settings do I Need in my torcc to get the Maximum Speed? At the Moment I entered 12 Mbytes - which Shows up at 96 mb/s in Arm - is that correct and my understanding of things is just the opposite? Max Speed, I think, should be 12.7mb/s for a 100mbit Connection?
mb is not a thing that exists; Mb is megabits: https://en.wikipedia.org/wiki/Megabit MB is megabytes: https://en.wikipedia.org/wiki/Megabyte
What you entered in torrc is currently correct. But since your board has a 100 Mbit interface anyway, it would be better if you just omit the bandwidth limit line entirely.
Also, actually hit anything remotely close to 100 Mbit, you'll absolutely have to run two instances of Tor. The Raspberry Pi 3 has 4 CPU cores, but each core on its own is not very fast. One copy of Tor only uses about 1 to 1.3 cores, so to fully utilize your hardware you need more than one. Ideally you'd set up four, but the Tor network will only accept two running from the same IPv4 address. It appears that these days there's a built-in script for that, see "man tor-instance-create".
-- With respect, Roman _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
okay, pls ignore my post.
2016-10-12 14:49 GMT+02:00 Tristan supersluether@gmail.com:
Last I heard, the Raspberry Pi was only capable of 100Mbps because the ethernet port is on the same bus as the USB ports, and the chipset used only supports 100Mbps. I could be wrong though.
On Oct 12, 2016 7:42 AM, "Markus Koch" niftybunny@googlemail.com wrote:
Everyone should have full duplex by now.
So he has 200 mbit on a fast ethernet port.
Sent from my iPad
On 12 Oct 2016, at 14:20, Tristan supersluether@gmail.com wrote:
Remember, a relay has to download and upload as well, so your 100Mbps link would really only be able to _relay_ at 50Mbps anyway.
On Oct 12, 2016 4:17 AM, "Farid Joubbi" joubbi@kth.se wrote:
The hardware in your raspberry is way too weak to be able to push 100 Mbit/s.
My guess is that Atlas will show somewhere just below 1 MByte for your relay.
I have tried to find cost effective hardware for a relay that is able to push around 100 Mbit/s. All the options I have looked at turned out to be a bit too expensive for my taste (and wallet). Either the initial cost or the energy usage is too high for such hardware for my purposes.
From: tor-relays tor-relays-bounces@lists.torproject.org on behalf of Volker Mink volker.mink@gmx.de Sent: 12 October 2016 09:09 To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] RPi Relay Maximum Speed
So the best would be to use two raspis or your old gaming-workstation - depends on the costs for energy
Gesendet: Mittwoch, 12. Oktober 2016 um 07:55 Uhr Von: "Roman Mamedov" rm@romanrm.net An: Manny felich@posteo.de Cc: "Tor relays" tor-relays@lists.torproject.org Betreff: Re: [tor-relays] RPi Relay Maximum Speed On Wed, 12 Oct 2016 07:18:56 +0200 Manny felich@posteo.de wrote:
I have a 1gbit symmetric connection at home and would like to donate 100mbit with my raspberry pi 3 model b. Since it has a 100mbit Network Interface, I'm limited to that anyways.
What Settings do I Need in my torcc to get the Maximum Speed? At the Moment I entered 12 Mbytes - which Shows up at 96 mb/s in Arm - is that correct and my understanding of things is just the opposite? Max Speed, I think, should be 12.7mb/s for a 100mbit Connection?
mb is not a thing that exists; Mb is megabits: https://en.wikipedia.org/wiki/Megabit MB is megabytes: https://en.wikipedia.org/wiki/Megabyte
What you entered in torrc is currently correct. But since your board has a 100 Mbit interface anyway, it would be better if you just omit the bandwidth limit line entirely.
Also, actually hit anything remotely close to 100 Mbit, you'll absolutely have to run two instances of Tor. The Raspberry Pi 3 has 4 CPU cores, but each core on its own is not very fast. One copy of Tor only uses about 1 to 1.3 cores, so to fully utilize your hardware you need more than one. Ideally you'd set up four, but the Tor network will only accept two running from the same IPv4 address. It appears that these days there's a built-in script for that, see "man tor-instance-create".
-- With respect, Roman _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On Wed, 12 Oct 2016 07:20:25 -0500 Tristan supersluether@gmail.com wrote:
Remember, a relay has to download and upload as well, so your 100Mbps link would really only be able to _relay_ at 50Mbps anyway.
The OP mentioned they have "1gbit symmetric connection at home", i.e. 1000 Mbit in, 1000 out.
Whether or not the Raspberry Pi will be limited to some value less than 100 Mbit when doing full duplex, is an interesting question; yes it uses a USB-based Ethernet chip, but that alone doesn't mean much, since the USB 2.0 is capable of up to 480 Mbit. It's a question of how efficient the actual used implementation is. Can be easily tested with "iperf -c ... -d".
Alternatively you can get a Gigabit NIC for USB, like described in http://www.jeffgeerling.com/blogs/jeff-geerling/getting-gigabit-networking
Hi!
On 12.10.2016 07:18, Manny wrote:
Oh and since I'm bugging you anyways - would it be useful to add ORPort [IPv6] as well? (same port as for 4 i guess?)
Yes, I've done this already. There are only a few number of IPv6 Clients, but I guess it would be useful. Most of the time, there are the same. I don't know why?
https://lists.torproject.org/pipermail/tor-relays/2015-May/007027.html
You cannot advertise the same DirPort on IPv4 and IPv6, but the ports could be the same.
Regards
On 13 Oct 2016, at 06:07, diffusae diffusae@yahoo.se wrote:
Hi!
On 12.10.2016 07:18, Manny wrote:
Oh and since I'm bugging you anyways - would it be useful to add ORPort [IPv6] as well? (same port as for 4 i guess?)
Yes, I've done this already. There are only a few number of IPv6 Clients, but I guess it would be useful. Most of the time, there are the same. I don't know why?
https://lists.torproject.org/pipermail/tor-relays/2015-May/007027.html
That mailing list post was about an IPv6 ExitPolicy bug that we fixed in 0.2.7. This is how it works now on Tor Exits:
For IPv4 and IPv6: ExitPolicy reject *:80
For IPv6 only: ExitPolicy reject6 *:80
You cannot advertise the same DirPort on IPv4 and IPv6, but the ports could be the same.
No current tor version uses an IPv6 DirPort to connect to the network.
Relays always use IPv4 to connect to the tor network, and they use IPv4 DirPorts to bootstrap.
Clients gained the ability to use IPv6 ORPorts for bootstrap in 0.2.8, and we made client bootstrapping ORPort-only in the same release.
So, in 0.2.7 and earlier, IPv6-only clients can use: * bridge IPv6 ORPorts by configuring a bridge with an IPv6 address.
And in 0.2.8 and later, IPv6-only clients can use: * bridge IPv6 ORPorts by configuring a bridge with an IPv6 address, or * authority, fallback directory, and relay IPv6 ORPorts by configuring: ClientUseIPv4 0 UseMicrodescriptors 0
(IPv6-only clients can't bootstrap using microdescriptors yet, see: https://trac.torproject.org/projects/tor/ticket/19608 )
This is experimental - being one of the rare IPv6-only clients on the network may harm your anonymity. (This is why you see the same few clients all the time.) But if your priority is local network censorship-evasion, then IPv6 might just work for you.
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------------
Hello!
Thanks a lot for your explanation.
It was a kind of misunderstanding the subject (Please enable IPv6 on your relay!) and also the instructions, what was written on the wiki (IPv6RelayHowto).
In other words, for non-exit relays, there is no need to enable IPv6 at this time, only if you use it as a bridge and/or as an IPv6-only client.
Regards
On 13.10.2016 01:46, teor wrote:
On 13 Oct 2016, at 06:07, diffusae diffusae@yahoo.se wrote:
Hi!
On 12.10.2016 07:18, Manny wrote:
Oh and since I'm bugging you anyways - would it be useful to add ORPort [IPv6] as well? (same port as for 4 i guess?)
Yes, I've done this already. There are only a few number of IPv6 Clients, but I guess it would be useful. Most of the time, there are the same. I don't know why?
https://lists.torproject.org/pipermail/tor-relays/2015-May/007027.html
That mailing list post was about an IPv6 ExitPolicy bug that we fixed in 0.2.7. This is how it works now on Tor Exits:
For IPv4 and IPv6: ExitPolicy reject *:80
For IPv6 only: ExitPolicy reject6 *:80
You cannot advertise the same DirPort on IPv4 and IPv6, but the ports could be the same.
No current tor version uses an IPv6 DirPort to connect to the network.
Relays always use IPv4 to connect to the tor network, and they use IPv4 DirPorts to bootstrap.
Clients gained the ability to use IPv6 ORPorts for bootstrap in 0.2.8, and we made client bootstrapping ORPort-only in the same release.
So, in 0.2.7 and earlier, IPv6-only clients can use:
- bridge IPv6 ORPorts by configuring a bridge with an IPv6 address.
And in 0.2.8 and later, IPv6-only clients can use:
- bridge IPv6 ORPorts by configuring a bridge with an IPv6 address, or
- authority, fallback directory, and relay IPv6 ORPorts by configuring: ClientUseIPv4 0 UseMicrodescriptors 0
(IPv6-only clients can't bootstrap using microdescriptors yet, see: https://trac.torproject.org/projects/tor/ticket/19608 )
This is experimental - being one of the rare IPv6-only clients on the network may harm your anonymity. (This is why you see the same few clients all the time.) But if your priority is local network censorship-evasion, then IPv6 might just work for you.
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 14 Oct 2016, at 08:05, diffusae punasipuli@t-online.de wrote:
Hello!
Thanks a lot for your explanation.
It was a kind of misunderstanding the subject (Please enable IPv6 on your relay!) and also the instructions, what was written on the wiki (IPv6RelayHowto).
In other words, for non-exit relays, there is no need to enable IPv6 at this time, only if you use it as a bridge and/or as an IPv6-only client.
No, that's not what I said. On non-exit relays, please enable the IPv6 ORPort. There's no need to enable an IPv6 DirPort.
Tim
Regards
On 13.10.2016 01:46, teor wrote:
On 13 Oct 2016, at 06:07, diffusae diffusae@yahoo.se wrote:
Hi!
On 12.10.2016 07:18, Manny wrote:
Oh and since I'm bugging you anyways - would it be useful to add ORPort [IPv6] as well? (same port as for 4 i guess?)
Yes, I've done this already. There are only a few number of IPv6 Clients, but I guess it would be useful. Most of the time, there are the same. I don't know why?
https://lists.torproject.org/pipermail/tor-relays/2015-May/007027.html
That mailing list post was about an IPv6 ExitPolicy bug that we fixed in 0.2.7. This is how it works now on Tor Exits:
For IPv4 and IPv6: ExitPolicy reject *:80
For IPv6 only: ExitPolicy reject6 *:80
You cannot advertise the same DirPort on IPv4 and IPv6, but the ports could be the same.
No current tor version uses an IPv6 DirPort to connect to the network.
Relays always use IPv4 to connect to the tor network, and they use IPv4 DirPorts to bootstrap.
Clients gained the ability to use IPv6 ORPorts for bootstrap in 0.2.8, and we made client bootstrapping ORPort-only in the same release.
So, in 0.2.7 and earlier, IPv6-only clients can use:
- bridge IPv6 ORPorts by configuring a bridge with an IPv6 address.
And in 0.2.8 and later, IPv6-only clients can use:
- bridge IPv6 ORPorts by configuring a bridge with an IPv6 address, or
- authority, fallback directory, and relay IPv6 ORPorts by configuring:
ClientUseIPv4 0 UseMicrodescriptors 0
(IPv6-only clients can't bootstrap using microdescriptors yet, see: https://trac.torproject.org/projects/tor/ticket/19608 )
This is experimental - being one of the rare IPv6-only clients on the network may harm your anonymity. (This is why you see the same few clients all the time.) But if your priority is local network censorship-evasion, then IPv6 might just work for you.
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------------
On 14.10.2016 00:54, teor wrote:
No, that's not what I said. On non-exit relays, please enable the IPv6 ORPort. There's no need to enable an IPv6 DirPort.
So, I wasn't totally wrong. I also guess, that it's useful. Only because of the IPv6 DirPort, I was unsure.
Thanks again, Reiner
Hi!
On 12.10.2016 07:18, Manny wrote:
Oh and since I'm bugging you anyways - would it be useful to add ORPort [IPv6] as well? (same port as for 4 i guess?)
Yes, I've done this already. There are only a few number of IPv6 Clients, but I guess it would be useful. Most of the time, there are the same. I don't know why?
https://lists.torproject.org/pipermail/tor-relays/2015-May/007027.html
You cannot advertise the same DirPort on IPv4 and IPv6, but the ports could be the same.
Regards
tor-relays@lists.torproject.org
-
diffusae -
diffusae -
Farid Joubbi -
Manny -
Markus Koch -
Roman Mamedov -
teor -
Tristan -
Volker Mink