On Mon, 06.02.17 17:41, Patrick Schleizer (
patrick-ma...@whonix.org) wrote:
> systemd directive ListenStream and systemd-socket-proxyd is really useful.
>
> Let's say I want to redirect...
>
> ListenStream=80
> ListenStream=81
> etc.
>
> ExecStart=/usr/lib/systemd/systemd-socket-proxyd
>
> Is there during ExecStart some way to get the ListenStream port? I.e.
>
> ExecStart=/usr/lib/systemd/systemd-socket-proxyd 10.152.152.10:${PORT}
>
> I mean, if
> - ListenStream=80 -> ExecStart=/usr/lib/systemd/systemd-socket-proxyd
>
10.152.152.10:80
> - ListenStream=81 -> ExecStart=/usr/lib/systemd/systemd-socket-proxyd
>
10.152.152.10:81
> etc.
>
> Or can there be a wrapper that has access to the ListenStream port number?
>
> If you are wondering what I am trying to do... I am trying to port
> anon-ws-disable-stacked-tor from loads of mostly idle socat listeners to
> systemd socket activation. Ideally, rather elegantly without one systemd
> unit file per port redirection. [1] [2] [3] [4]
This is not supported. But if you send a PR that makes it possible to