Closed qrkourier closed 2 years ago
Consider adding some sanity checks to the systemd unit file like ConditionDirectoryNotEmpty
Additionally, should we be steering users to the XDG Base Directory Specification?
@sabedevops Good stuff. I added that unit conditional and XDG_DATA_HOME
looks like something we should use with the (eventual) install package for this service unit, unless you see a specific way we could apply it in this manual install procedure.
For the purposes of this script, this can be done generically like this:
[ ! -z "$XDG_DATA_HOME" ] && ZITI_EDGE_TUNNEL_ID_DIR="$XDG_DATA_HOME/ziti-edge-tunnel" || ZITI_EDGE_TUNNEL_ID="$HOME/.ziti-edge-tunnel"
This may not align with current documentation and user expectations, so it may be worth ignoring at this time.
Also, please be advised the approach in this script is not bulletproof, since things like Kerberized NFS homedirs with root squashing will cause the service to fail due to permissions. Nonetheless, it's a great start @qrkourier
@dovholuknf Based on today's conversation about the older and newer Linux tunnelers we should refactor this document to position the preferred tunneler as such, and document the dwindling-few unique capabilities of the non-preferred tunneler ziti-tunnel
. You may assign this issue to me. :+1:
Some notes that we could fold-in to https://openziti.github.io/ziti/clients/tunneler.html#linux
ziti-edge-tunnel
ziti-tunnel
but has a superior approach to built-in DNSziti-tunnel
run
mode usestun
device IP routes to intercept service traffic and answer DNS viaresolvectl
netfoundry/ziti-edge-tunnel
systemd
installziti-tunnel
proxy
andhost
in addition totproxy
(IPtables intercepts)netfoundry/ziti-tunnel