mainly used in start-up script
When we play with iptables aka firewall we might end up in situation, where we execute rule, which has unforseen impact - lock yourself out. Recovering from this situation is necessity.
How to:
- Enable reboot via SMS.
- Test all commands in shell first before putting them into Start-up script. This way the command will be wiped out, when unit is rebooted.
| package main | |
| import ( | |
| "flag" | |
| "fmt" | |
| "net/http" | |
| ) | |
| func main() { | |
| var port string |
| // per https://docs.npmjs.com/misc/scripts, npm exposes a bunch of variables to | |
| // the environment prefixed with npm_config_*, npm_package_* and npm_lifecycle_*. | |
| // Here's a list of all variables exposed in my setup. | |
| npm_config_access= | |
| npm_config_allow_same_version= | |
| npm_config_also= | |
| npm_config_always_auth= | |
| npm_config_argv='{"remain":[],"cooked":["run","foo"],"original":["run","foo"]}' | |
| npm_config_auth_type=legacy |
If you don't know what Wireguard is, well, you should. It's fast, easy to setup and highly configurable. We will configure Wireguard for multiple users with various restrictions using iptables.
This should fit most setups (not mine though 😉)
| #!/bin/bash | |
| set -euo pipefail | |
| IF=<if> | |
| URL="https://wirehub.org/<user>/n/<net>/device/<id>/download?invite_code=<code>" | |
| TMPFILE="$(mktemp)" | |
| SPLITDIR="$(mktemp -d)" | |
| DEST=/etc/wireguard/"$IF".conf | |
| cleanup() { | |
| rm -f "${TMPFILE}" |
