Hi again
I took another look at this problem, and now I'm even more convinced that
what we really need is IP_BIND_ADDRESS_NO_PORT. Here's why.
If torrc OutboundBindAddress is configured, tor calls bind(2) on every
outgoing connection:
https://gitlab.torproject.org/tpo/core/tor/-/blob/tor-0.4.7.12
All:
What is the status of Bug #7349 - Obfsbridges should be able to "disable" their
ORPort?
https://bugs.torproject.org/tpo/core/tor/7349
I recently setup a loadbalanced OBFS4 bridge and would prefer not to expose the
ORPort to the World.
I've noticed that some of the tasks to make this possible
David,
I'm in the process of trying to cross-compile snowflake for OpenWRT and
Entware. Are there any other dependencies to compile snowflake other than Go?
Do you know if it's possible to configure multiple pluggable transports with
different listeners within a single torrc?
Thanks, again.
Gary
Hi David
IP_BIND_ADDRESS_NO_PORT did not fix your somewhat similar problem in your
Haproxy setup, because all the connections are to the same dst tuple (i.e 127.0.0.1:ExtORPort).
The connect() system call is looking for a unique 5-tuple . In the Haproxy setup, the only free variable is
srcport ,
On Sat, Dec 10, 2022 at 05:19:43AM +, Gary C. New via tor-relays wrote:
> I'm in the process of trying to cross-compile snowflake for OpenWRT and
> Entware. Are there any other dependencies to compile snowflake other than Go?
The README should list dependencies. Setting GOOS and GOARCH should
On Sat, Dec 10, 2022 at 09:59:14AM +0100, Anders Trier Olesen wrote:
> IP_BIND_ADDRESS_NO_PORT did not fix your somewhat similar problem in your
> Haproxy setup, because all the connections are to the same dst tuple port>
> (i.e 127.0.0.1:ExtORPort).
> The connect() system call is looking for a un
