Added charon.initiator_only option which causes charon to ignore IKE initiation reque...
[strongswan.git] / testing / tests / ikev2 / rw-initiator-only / evaltest.dat
1 dave::cat /var/log/daemon.log::establishing IKE_SA failed, peer not responding::YES
2 carol::ipsec status 2> /dev/null::home.*ESTABLISHED.*carol@strongswan.org.*moon.strongswan.org::YES
3 moon:: ipsec status 2> /dev/null::rw\[1]: ESTABLISHED.*moon.strongswan.org.*carol@strongswan.org::YES
4 carol::ipsec status 2> /dev/null::home.*INSTALLED, TUNNEL::YES
5 moon:: ipsec status 2> /dev/null::rw[{]1}.*INSTALLED, TUNNEL::YES
6 carol::ping -c 1 PH_IP_ALICE::64 bytes from PH_IP_ALICE: icmp_req=1::YES
7 moon::tcpdump::IP carol.strongswan.org > moon.strongswan.org: ESP::YES
8 moon::tcpdump::IP moon.strongswan.org > carol.strongswan.org: ESP::YES