Snowflake on OpenWRT as standalone proxy

[WofWca]

So, in summary, what is the problem that you are trying to solve at this point? It seems that you have managed to start Snowflake.

@bisir

What bothering me also is process of avoiding any VPN being possibly deployed on the router itself.

I’m pretty sure that binding to the WAN interface instead of the VPN’s interface is the way to bypass a VPN. As long as the “Kill-switch” feature (which prevents direct WAN traffic) is disabled.
Snowflake has the -outbound-address parameter, you could try to set it to your WAN address to bypass the VPN.

@bisir

There is a lot of communication with the brokers - thus it will split possibly the communication with broker through VPN and with client through WAN(?)

Although the broker will incorrectly count proxy country stats then (https://snowflake-broker.torproject.net/metrics), it is otherwise fine to use different IPs for broker communication and for serving clients.

@bisir

But interestingly wg show all is almost 1:1 for that period of time

Note that if take the Snowflake process as a whole and count its inbound / outbound traffic, you should expect to see a 1:1 ratio, because it’s just a proxy: it sends pretty much exactly as much as it receives.
See:

@Vort

these lines show numbers from proxy user perspective.
Users are more active at downloading than uploading, that’s why difference appear.

---

@bisir

And lastly - my snowflake reporting: “Type measurement: unknown → restricted = restricted”.

So maybe it’s not even for greater good.
How one could know if his Snowflake is a drag to the network (mainly to the broker) or adding actually some value?

“Restricted” doesn’t mean it’s a drag. The majority (97.7%) of Snowflake proxies are restricted (see the metrics), and this is expected. Generally if a proxy is able to serve clients, then it’s good for the network.