add kitchen test case with IPv6 addresses #158
Labels
Comments
+ - name: t-guard-IPv6
+ driver:
+ network:
+ - ["private_network", {ip: "192.0.2.10"}]
+ - ["private_network", {ip: "198.51.100.10"}]
+ - ["private_network", {ip: "2001:db8::1"}]
+ - ["private_network", {ip: "2001:db8::2"}]
+ provisioner:
+ playbook: "test/integration/default/2publicIPs-guard-node.yml"VirtualBox 5.2.8 maybe this: |
|
I am afraid we can only try to work around this, since the issue is opened for 3 years in virtualbox. I was thinking about easy workaround by disabling IPv6 autoconfiguration, but since the process fails before shell provisioning is started, I cannot do it like that: sudo sysctl -w net.ipv6.conf.all.autoconf=0
sudo sysctl -w net.ipv6.conf.all.accept_ra=0Another attempt with disabling IPv6 autoconfiguration I made was using VirtualBox customizations but I couldn't find something useful there. This leads me worst possible workaround with provisioner and shell script which will assign IPv6 addresses to 2 already defined interfaces: - name: t-guard-IPv6
driver:
network:
- ["private_network", {ip: "192.0.2.10"}]
- ["private_network", {ip: "198.51.100.10"}]
provisioner:
playbook: "test/integration/default/2publicIPs-guard-node.yml"Vagrant.configure("2") do |config|
config.vm.provision "shell", inline: <<-SHELL
netif_list=$(ls -1 /sys/class/net)
for interf in ${netif_list}; do
if ip address show dev "${interf}" | grep '192.0.2.10'; then
ip address add "2001:db8::1/32" dev "${interf}"
elif ip address show dev "${interf}" | grep '198.51.100.10'; then
ip address add "2001:db8::2/32" dev "${interf}"
fi
done
SHELL
end |
|
thanks for this! did you test it? for which platforms? |
nusenu
referenced
this issue
Jul 1, 2018
before this commit we used a single IP address for all tor instances on a server for exiting if tor_dedicatedExitIP was enabled, with this commit multiple exit IP addresses are used. By distributing the traffic across multiple source IP addresses this should help reduce the negative effects of bad traffic spoiling the source IP for many tor users. There are two cases to consider: - user runs one tor instance per IP (tor_ports has one entry): "loop_idx" can be directly used as an index to the tor_available_public_ipv4/6 arrays - user runs two tor instances per IP (tor_ports has two entries): in this case we need to mangle "loop_idx" before we used it as an index to the IP address arrays This change includes also the kitchen test suites for this feature: t-exit-6publicIPs-dedicatedExitIP-2instPerIP t-exit-6publicIPs-dedicatedExitIP-singleInstPerIP
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Lets add a test case with IPv6 addresses by copying and extending
t-guard-2publicIPsIPv6 documentation IP range
https://tools.ietf.org/html/rfc3849
The text was updated successfully, but these errors were encountered: