testing: Use renamed systemd unit
While the alias is available after enabling the unit, we don't actually do that in our testing environment (adding a symlink manually would work too, then again, why not just use the proper name?).
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
sun::systemctl stop strongswan-swanctl
|
||||
alice::systemctl stop strongswan-swanctl
|
||||
venus::systemctl stop strongswan-swanctl
|
||||
sun::systemctl stop strongswan
|
||||
alice::systemctl stop strongswan
|
||||
venus::systemctl stop strongswan
|
||||
alice::iptables-restore < /etc/iptables.flush
|
||||
venus::iptables-restore < /etc/iptables.flush
|
||||
sun::iptables-restore < /etc/iptables.flush
|
||||
|
||||
@@ -3,9 +3,9 @@ venus::iptables-restore < /etc/iptables.rules
|
||||
sun::iptables-restore < /etc/iptables.rules
|
||||
moon::iptables -t nat -A POSTROUTING -o eth0 -s 10.1.0.0/16 -p udp -j SNAT --to-source PH_IP_MOON:1024-1100
|
||||
moon::iptables -t nat -A POSTROUTING -o eth0 -s 10.1.0.0/16 -p tcp -j SNAT --to-source PH_IP_MOON:2000-2100
|
||||
sun::systemctl start strongswan-swanctl
|
||||
alice::systemctl start strongswan-swanctl
|
||||
venus::systemctl start strongswan-swanctl
|
||||
sun::systemctl start strongswan
|
||||
alice::systemctl start strongswan
|
||||
venus::systemctl start strongswan
|
||||
sun::expect-connection nat-t
|
||||
alice::expect-connection nat-t
|
||||
alice::swanctl --initiate --child nat-t
|
||||
|
||||
Reference in New Issue
Block a user