My setup:
Snowflake Standalone proxy compiled with GO using their instructions running native on Ubuntu 22.04.4 LTS behind a home router. This machine’s primary purpose is to run work units (jobs) using the Berkley software BOINC. It’s 100% CPU bound running 24/7 on 32 cores. Hardly any network traffic so it’s a good marriage with Snowflake.
I use the following command and capture the logs which I analyze..
proxy -nat-retest-interval 0 -ephemeral-ports-range “65497:65534” -capacity 10 -unsafe-logging -verbose
Yes 2.5x is a good number because the proxy actually uses 2 ports per connection. I actually use more just because.
I wonder about “-metrics -metrics-address 0.0.0.0”. Why “0.0.0.0” the default is localhost on port 9999 and you need the geoip data in /usr/share/tor/ from either the Tor Browser or Tor Expert Bundle or a Tor relay install.
Not familiar with restricted-cone or not. Mine runs as unrestricted simply because I opened those ephemeral-ports on the router and forward them to the machine.
2025/12/06 22:33:21 Test WebRTC connection with NAT check probe server established! This means our NAT is unrestricted!
2025/12/06 22:33:21 NAT Type measurement: unknown → unrestricted
2025/12/06 22:33:21 NAT type: unrestricted
What does your log say? grep the log for the word restricted
1600 connections. WOW! Notice I only allow -capacity 10 but my connection is not 5 Gbps but 10/30 Mbps. I plan to up that -capacity at some point.
You set the capacity to 1600 but you never get to see how many users are actually connected. That would be on my wishlist. Also on my wishlist would be a way to up the capacity without stopping the proxy along with being able to start and stop the -metrics on the fly.
A quick and dirty way to see the number of users is in my tip:
I use my own scripts to find the actual number.