allow port to be configured with direct assignment #94
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes: #84
Rational:
In some environments (like docker) it is desirable to expose the tailscale port to increase direct connection success. By default ts-net when encountering a
0
port will pick a port at random. This is difficult for docker since the ports are not known.This work extends the node config to allow a node to gain a specific port, allowing for exposing in docker (or any other time where a user may wish to expose the port)
Steps to test:
Check out branch and run
xcaddy build --with github.com/tailscale/caddy-tailscale=$(pwd)
Run the following caddyfile with
TS_AUTHKEY
in environmentcurl http://test-caddy