aboutsummaryrefslogtreecommitdiffstats
path: root/group_vars
diff options
context:
space:
mode:
authorAsbjørn Sloth Tønnesen <asbjorn@labitat.dk>2021-09-06 18:13:20 +0000
committerAsbjørn Sloth Tønnesen <asbjorn@labitat.dk>2021-09-06 19:06:02 +0000
commit6856b82bdcd61ea25cac8bc64a9114d908e6ea9e (patch)
tree76f20db1cae32f1fcb86cd6603b398d441c45e9d /group_vars
parentb1904dcc2937c93408234311793302aedca859c4 (diff)
downloadlabitat-ansible-new-tor-exit-range.tar.gz
labitat-ansible-new-tor-exit-range.tar.xz
labitat-ansible-new-tor-exit-range.zip
space_server: add dedicated VLAN for Tor exit nodesnew-tor-exit-range
Move the Tor exit nodes to their own VLAN, and their own address space. Background for move ------------------- For the first Tor exit node, we where able to create inet6num object 2a01:4262:1ab:20::71/128. So we could assign a specific Tor abuse contact. When we added the second node it was no longer possible to create /128 inet6num objects, but only up to /64. We therefore need to move our Tor exit nodes to a dedicated address space. Connection tracking ------------------- Connection tracking is quite expensive, so it's better to only do it for Tor traffic, when we actually need it, which is only when internal clients need to access the servers. In the future conntrack could also be disabled for labicolo in general. Current stats ~~~~~~~~~~~~~ [root@space ~]# grep -v '185\.38\.175\.7[12] ' /proc/net/nf_conntrack | grep -v '2a01:4262:01ab:0020:0000:0000:0000:007[12]' | wc -l 4071 [root@space ~]# wc -l /proc/net/nf_conntrack 39138 /proc/net/nf_conntrack Currently 4071 out of 39138 connections are not Tor related. Also reading /proc/net/nf_conntrack is quite slow atm.: [root@space ~]# time cat /proc/net/nf_conntrack > /dev/null real 0m35.097s user 0m0.010s sys 0m28.114s Signed-off-by: Asbjørn Sloth Tønnesen <asbjorn@labitat.dk>
Diffstat (limited to 'group_vars')
0 files changed, 0 insertions, 0 deletions