wallenstein/algo
1
0
Fork 0
mirror of https://github.com/trailofbits/algo.git synced 2025-08-10 23:03:03 +02:00
Code Issues Projects Releases Wiki Activity

Added Restoring Option

Browse source
This commit is contained in:
AnderCrafter 2019-04-29 14:18:33 +02:00 • committed by GitHub
parent b526f73881
commit 1fe1251870
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
docs/firewalls.md
View file

@ -14,6 +14,11 @@ Your AlgoVPN requires properly configured firewalls. The key points to know are:
During installation Algo configures the Linux [Netfilter](https://en.wikipedia.org/wiki/Netfilter) firewall on the server. The rules added are required for AlgoVPN to work properly. The package `netfilter-persistent` is used to load the IPv4 and IPv6 rules files that Algo generates and stores in `/etc/iptables`. The rules for IPv6 are only generated if the server appears to be properly configured for IPv6. The use of conflicting firewall packages on the server such as `ufw` will likely break AlgoVPN.
If you ever break the Firewall or need to reconfigure it (in Advanced Usage) you can use
https://pastebin.com/65v6siUK for IPv4
https://pastebin.com/r3S9ZRWN for IPv6
And Place the Content to /etc/iptables/rules.v4 (IPv4) and /etc/iptables/rules.v6 (IPv6).
On RHEL/CentOS the paths are /etc/sysconfig/iptables (IPv4) and /etc/sysconfig/ip6tables (IPv6)
### External Firewall
Most cloud service providers offer a firewall that sits between the Internet and your AlgoVPN. With some providers (such as EC2, Lightsail, and GCE) this firewall is required and is configured by Algo during a **cloud** deployment. If the firewall is not required by the provider then Algo does not configure it.