David,
I was successfully able to get Snowflake cross-compiled and installed for
OpenWRT and Entware as a package.
# opkg install ./snowflake_2.4.1-1_armv7-2.6.ipk
Installing snowflake (2.4.1-1) to root...
Configuring snowflake.
# opkg info snowflake
Package: snowflake
Version: 2.4.1-1
Depend
On Saturday, December 10, 2022, 7:23:28 AM PST, David Fifield
wrote:
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>
On Saturday, December 10, 2022, 8:01:15 AM MST, David Fifield
wrote:
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 th
I wrote some tests[1] which showed behaviour I did not expect.
IP_BIND_ADDRESS_NO_PORT seems to work as it should, but calling bind
without it enabled turns out to be even worse than I thought.
This is what I think is happening: A successful bind() on a socket without
IP_BIND_ADDRESS_NO_PORT enable
> I urge you to run an experient yourself, if these observations are not
> what you expect. I was surprised, as well.
Very interesting. I'll run some tests.
We do agree that IP_BIND_ADDRESS_NO_PORT should fix OPs' problem, right?
With it enabled, there's no path to inet_csk_bind_conflict which is
Also see this patch, which introduces net.ipv4.ip_autobind_reuse:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4b01a9674231a97553a55456d883f584e948a78d
Enabling net.ipv4.ip_autobind_reuse allows the kernel to bind SO_REUSEADDR
enabled sockets (which I think they are
