174 - now only the OpenConnect invocation takes over stdin itself, bash works again :slightly_smiling_face:
175 - "dead" namespaces will not be cleaned if there are PIDs running - however this does not apply to the vopono namespace cleaning itself up - i.e. if you use the same network namespace and vopono with different users at the same time then closing either one would still clean up the network namespace.
169 - aarch64 binaries and deb added to Github action
172 and #173 - UI code has been refactored into UIClient trait and clap ArgEnum enums are wrapped with the WrappedArg struct in args.rs
159 - with the --allow-host-access flag to access the local host (note the host IP address will likely be 10.200.1.1 (or 10.200.x.1 when running multiple vopono instances) - you must use that to access it from inside the network namespace).
131 - you can use --custom-netns-name to override the network namespace name, and --open-hosts should work for allowing access to the shadowsocks server for scripting.
152 - OpenVPN logs are now in ~/.config/vopono/logs/ by netns name, this seems to remove the warning.
Fixes:
174 - now only the OpenConnect invocation takes over stdin itself, bash works again :slightly_smiling_face:
175 - "dead" namespaces will not be cleaned if there are PIDs running - however this does not apply to the vopono namespace cleaning itself up - i.e. if you use the same network namespace and vopono with different users at the same time then closing either one would still clean up the network namespace.
169 - aarch64 binaries and deb added to Github action
172 and #173 - UI code has been refactored into UIClient trait and clap ArgEnum enums are wrapped with the WrappedArg struct in
args.rs159 - with the
--allow-host-accessflag to access the local host (note the host IP address will likely be10.200.1.1(or10.200.x.1when running multiple vopono instances) - you must use that to access it from inside the network namespace).131 - you can use
--custom-netns-nameto override the network namespace name, and--open-hostsshould work for allowing access to the shadowsocks server for scripting.152 - OpenVPN logs are now in
~/.config/vopono/logs/by netns name, this seems to remove the warning.