[GH-ISSUE #32] Customizable CTRL_PORT for tunnelto_server? #29

New issue

Closed

opened 2026-03-02 23:01:51 +03:00 by kerem · 1 comment

kerem commented

2026-03-02 23:01:51 +03:00

Owner

Originally created by @mxxk on GitHub (Nov 9, 2020).
Original GitHub issue: https://github.com/agrinman/tunnelto/issues/32

The environment variable CTRL_PORT is useful to override the control port used for the tunnelto client to connect to tunnelto_server, but there seems to be no equivalent to override the control port tunnelto_server binds to, as it is hardcoded:

github.com/agrinman/tunnelto@b3bb05709f/tunnelto_server/src/main.rs (L59)

github.com/agrinman/tunnelto@b3bb05709f/tunnelto_server/src/remote.rs (L7)

While not critical, it would be nice to set the tunnelto_server control port via an environment variable. 🙂

The larger context for doing this is https://github.com/mxxk/tunnelto-proxy, which provides a proxy configuration for multiplexing between control traffic (on the root domain) and tunnel traffic (on subdomains). Having something like this be integrated into tunnelto directly would be a very significant undertaking, and different from the current approach used by tunnelto.dev where the control traffic is expected at wormhole.tunnelto.dev (and presumably wormhole is in BLOCKED_SUB_DOMAINS), while all other (tunnel) traffic is expected at *.tunnelto.dev.

Originally created by @mxxk on GitHub (Nov 9, 2020). Original GitHub issue: https://github.com/agrinman/tunnelto/issues/32 The environment variable `CTRL_PORT` is useful to override the control port used for the `tunnelto` client to connect to `tunnelto_server`, but there seems to be no equivalent to override the control port `tunnelto_server` binds to, as it is hardcoded: https://github.com/agrinman/tunnelto/blob/b3bb05709fe59920e052553fd63df901fbd5598e/tunnelto_server/src/main.rs#L59 https://github.com/agrinman/tunnelto/blob/b3bb05709fe59920e052553fd63df901fbd5598e/tunnelto_server/src/remote.rs#L7 While not critical, it would be nice to set the `tunnelto_server` control port via an environment variable. 🙂 The larger context for doing this is https://github.com/mxxk/tunnelto-proxy, which provides a proxy configuration for multiplexing between control traffic (on the root domain) and tunnel traffic (on subdomains). Having something like this be integrated into `tunnelto` directly would be a very significant undertaking, and different from the current approach used by `tunnelto.dev` where the control traffic is expected at `wormhole.tunnelto.dev` (and presumably `wormhole` is in `BLOCKED_SUB_DOMAINS`), while all other (tunnel) traffic is expected at `*.tunnelto.dev`.