On 17.04.2020 11:46, ylms wrote:
Hello Marco
On 4/17/20 11:32 AM, lists@for-privacy.net wrote:
On 17.04.2020 11:05, i forget:
On 17.04.2020 10:03, ylms wrote:
ORPort 443
- ORPort [YOUR:V6:IP]:443
So I should use ORPort twice, once for IPv4 and once for IPv6?
Yes. IPv4 only Port & IPv6 with brackets: [YOUR:V6:IP]:Port
## If you have multiple network interfaces, specify one for outgoing traffic to use. OutboundBindAddress IPv4 OutboundBindAddress [YOUR:IP:V6]
OK, I will add that.
What is the option "OutboundBindAddressOR" for? Should I use that too?
Normally not needed. Make all outbound non-exit (relay and other) connections originate from the IP address specified. This option overrides OutboundBindAddress for the same IP version.
OutboundBindAddress OutboundBindAddressOR OutboundBindAddressExit is only useful when you have multiple network interfaces or IP's.
SocksPort 0 BridgeRelay 1
## uncomment if you don't want torproject.org to know your bridge #PublishServerDescriptor 0
no, I want the relay to be distributed by the various services that torprojects.org is offering.
It's a good thing. Just wanted to point out the option.
ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy ServerTransportListenAddr obfs4 0.0.0.0:80
## The ServerTransportListenAddr line is dual stack friendly. ServerTransportListenAddr obfs4 [::]:80
So I'll add another line for IPv6 here too.
You only need it once. Change 0.0.0.0:80 to [::]:80. You then have IPv4 and IPv6. ServerTransportListenAddr obfs4 [::]:80
ExtORPort auto
CookieAuthentication 1 ExitPolicy reject *:* ExitPolicy reject6 *:* ClientUseIPv6 1
^^^^Not used. For Clients.
you're right, somehow I must have copied that over from somewhere.
#%include /etc/tor/torrc_family
^^^Not needed for Tor Bridge
OK.
//End of torrc
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays