UDPGW

SUGGESTION

Please add support for running and managing a UDP gateway (UDPGW) on the server side, so that users can tunnel UDP traffic.

Configuration options:

1. UDPGW listen address and port (e.g. 0.0.0.0:7300).
2. Maximum clients, timeouts, and connection limits.
3. Automatic systemd service file for UDPGW.

This would make it much easier to use your dnstm, without asking users to install and configure UDPGW manually.

Client apps like NetMod support UDPGW for dnstt. adding this feature would help users a lot.

[FarmehrF]

I’ve been sketching how dnstm could ship UDPGW (managed binary + config + systemd), similar to microsocks. There are three realistic ways to source the actual server binary:

A — net2share release builds
Publish static udpgw artifacts (same idea as microsocks-build), pin URLs in dnstm’s BinaryDef, install/update like other tools.

B — existing implementation (e.g. BadVPN udpgw)
dnstm wraps an upstream binary / distro package + documents CLI flags. Fastest path for client compatibility, but pinning and multi-arch CI are messier unless we still mirror builds somewhere.

C — small dedicated Go udpgw in a separate repo
Full control of flags and protocol, easy static releases, but you own spec, security reviews, and maintenance.

@crazydi4mond Do you want net2share to own and publish a UDPGW server (A or C), or should dnstm integrate an existing binary first (B) and only add first-party builds later?