Standalone Snowflake NAT type problem

zerologs · December 9, 2024, 10:21am

Hi All, thanks for all the replies I appreciate it. I found the problem which is quite odd but a user problem on my end not the snowflake proxy. I checked the port forwarding on the ISP/router and it checked out ok, ports are forwarded to the Google Wifi device.

The problem was on the Google wifi app where you port forward the ports to the snowflake proxy, the settings was gone and I don’t know why and I just re-entered the port values 32678 to 60999 saved it again.

I tested the ports using the Stun-NAT-Behaviour test and it worked and as of this writing I now have traffic on the snowflake proxy and is now back to unrestricted. I also adjusted the -capacity to 40, it used to be on the default which overwhelmed the RaspberryPi and crashed.

Network Flow: ISP modem/router → Google Wifi device → RaspberryPi Snowflake Proxy

github.com

pion/stun/blob/master/cmd/stun-nat-behaviour/README.md

# NAT behaviour discovery using STUN ([RFC 5780](https://tools.ietf.org/html/rfc5780))

This is an example of how to use the pion/stun package for client-side NAT
behaviour discovery. It performs two types of tests: one to determine the
client's NAT mapping behaviour, and one to determine the NAT filtering
behaviour.


### Usage
```sh
$ go install github.com/pion/stun/v3/cmd/stun-nat-behaviour@latest
$ $GOPATH/bin/stun-nat-behaviour [options] [--server IP:port]
```

If `$GOPATH` is unset it defaults to `~/go`

The default value `--server` is stun.voipgate.com:3478

Use `-h` to see all options

This file has been truncated. show original

Output from the Stun-NAT-Behaviour test.

INFO: 2024/12/08 23:47:16 Connecting to STUN server: stun.voipgate.com:3478
INFO: 2024/12/08 23:47:16 Local address: 0.0.0.0:47418
INFO: 2024/12/08 23:47:16 Remote address: 185.125.180.70:3478
INFO: 2024/12/08 23:47:16 Mapping Test I: Regular binding request
INFO: 2024/12/08 23:47:16 Sending to 185.125.180.70:3478: (20 bytes)
INFO: 2024/12/08 23:47:16 Response from 185.125.180.70:3478: (100 bytes)
INFO: 2024/12/08 23:47:16 Received XOR-MAPPED-ADDRESS: x.x.x.x:47418
INFO: 2024/12/08 23:47:16 Mapping Test II: Send binding request to the other address but primary port
INFO: 2024/12/08 23:47:16 Sending to 185.125.180.71:3478: (20 bytes)
INFO: 2024/12/08 23:47:16 Response from 185.125.180.71:3478: (100 bytes)
INFO: 2024/12/08 23:47:16 Received XOR-MAPPED-ADDRESS: x.x.x.x:47418
WARNING: 2024/12/08 23:47:16 => NAT mapping behavior: endpoint independent ←
INFO: 2024/12/08 23:47:16 Connecting to STUN server: stun.voipgate.com:3478
INFO: 2024/12/08 23:47:16 Local address: 0.0.0.0:33377
INFO: 2024/12/08 23:47:16 Remote address: 185.125.180.70:3478
INFO: 2024/12/08 23:47:16 Filtering Test I: Regular binding request
INFO: 2024/12/08 23:47:16 Sending to 185.125.180.70:3478: (20 bytes)
INFO: 2024/12/08 23:47:16 Response from 185.125.180.70:3478: (100 bytes)
INFO: 2024/12/08 23:47:16 Filtering Test II: Request to change both IP and port
INFO: 2024/12/08 23:47:16 Sending to 185.125.180.70:3478: (28 bytes)
INFO: 2024/12/08 23:47:17 Response from 185.125.180.71:3479: (100 bytes)
WARNING: 2024/12/08 23:47:17 => NAT filtering behavior: endpoint independent ←

This is what I’m looking for both NAT mapping and filtering are endpoint independent.
WARNING: 2024/12/08 23:47:16 => NAT mapping behavior: endpoint independent ←
WARNING: 2024/12/08 23:47:17 => NAT filtering behavior: endpoint independent ←

Finally I can put this problem to rest and let the Snowflake Proxy run for as long as it takes.