<div dir="ltr">Hi Noel,<div><br></div><div>These are the firewall rules of all hosts after establishing the tunnels (all the NFLOG rules will be removed eventually, they're currently used for debugging):</div><div><br></div><div><div>[alice] $ iptables -S </div><div>-P INPUT ACCEPT</div><div>-P FORWARD ACCEPT</div><div>-P OUTPUT ACCEPT</div><div>-N nixos-fw</div><div>-N nixos-fw-accept</div><div>-N nixos-fw-log-refuse</div><div>-N nixos-fw-refuse</div><div>-A INPUT -s <a href="http://10.0.0.0/24">10.0.0.0/24</a> -d <a href="http://10.0.0.1/32">10.0.0.1/32</a> -i eth1 -m policy --dir in --pol ipsec --reqid 1 --proto esp -j ACCEPT</div><div>-A INPUT -m addrtype ! --dst-type LOCAL -m policy --dir in --pol ipsec -j NFLOG --nflog-group 5</div><div>-A INPUT -m addrtype --dst-type LOCAL -m policy --dir in --pol ipsec -j NFLOG --nflog-group 5</div><div>-A INPUT -p udp -m multiport --dports 500,4500 -j NFLOG --nflog-group 5</div><div>-A INPUT -p ah -j NFLOG --nflog-group 5</div><div>-A INPUT -p esp -j NFLOG --nflog-group 5</div><div>-A INPUT -j nixos-fw</div><div>-A FORWARD -s <a href="http://10.0.0.0/24">10.0.0.0/24</a> -d <a href="http://10.0.0.1/32">10.0.0.1/32</a> -i eth1 -m policy --dir in --pol ipsec --reqid 1 --proto esp -j ACCEPT</div><div>-A FORWARD -s <a href="http://10.0.0.1/32">10.0.0.1/32</a> -d <a href="http://10.0.0.0/24">10.0.0.0/24</a> -o eth1 -m policy --dir out --pol ipsec --reqid 1 --proto esp -j ACCEPT</div><div>-A OUTPUT -s <a href="http://10.0.0.1/32">10.0.0.1/32</a> -d <a href="http://10.0.0.0/24">10.0.0.0/24</a> -o eth1 -m policy --dir out --pol ipsec --reqid 1 --proto esp -j ACCEPT</div><div>-A OUTPUT -m policy --dir out --pol ipsec -j NFLOG --nflog-group 5</div><div>-A OUTPUT -p udp -m multiport --dports 500,4500 -j NFLOG --nflog-group 5</div><div>-A OUTPUT -p ah -j NFLOG --nflog-group 5</div><div>-A OUTPUT -p esp -j NFLOG --nflog-group 5</div><div>-A nixos-fw -i lo -j nixos-fw-accept</div><div>-A nixos-fw -m conntrack --ctstate RELATED,ESTABLISHED -j nixos-fw-accept</div><div>-A nixos-fw -p icmp -m icmp --icmp-type 8 -j nixos-fw-accept</div><div>-A nixos-fw -j nixos-fw-log-refuse</div><div>-A nixos-fw-accept -j ACCEPT</div><div>-A nixos-fw-log-refuse -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -j LOG --log-prefix "rejected connection: " --log-level 6</div><div>-A nixos-fw-log-refuse -m pkttype ! --pkt-type unicast -j nixos-fw-refuse</div><div>-A nixos-fw-log-refuse -j nixos-fw-refuse</div><div>-A nixos-fw-refuse -j DROP</div></div><div><br></div><div class="gmail_extra">[carol] $ iptables -S </div><div class="gmail_extra">-P INPUT ACCEPT</div><div class="gmail_extra">-P FORWARD ACCEPT</div><div class="gmail_extra">-P OUTPUT ACCEPT</div><div class="gmail_extra">-N nixos-fw</div><div class="gmail_extra">-N nixos-fw-accept</div><div class="gmail_extra">-N nixos-fw-log-refuse</div><div class="gmail_extra">-N nixos-fw-refuse</div><div class="gmail_extra">-A INPUT -s <a href="http://10.0.0.0/24">10.0.0.0/24</a> -d <a href="http://10.0.0.2/32">10.0.0.2/32</a> -i eth1 -m policy --dir in --pol ipsec --reqid 1 --proto esp -j ACCEPT</div><div class="gmail_extra">-A INPUT -m addrtype ! --dst-type LOCAL -m policy --dir in --pol ipsec -j NFLOG --nflog-group 5</div><div class="gmail_extra">-A INPUT -m addrtype --dst-type LOCAL -m policy --dir in --pol ipsec -j NFLOG --nflog-group 5</div><div class="gmail_extra">-A INPUT -p udp -m multiport --dports 500,4500 -j NFLOG --nflog-group 5</div><div class="gmail_extra">-A INPUT -p ah -j NFLOG --nflog-group 5</div><div class="gmail_extra">-A INPUT -p esp -j NFLOG --nflog-group 5</div><div class="gmail_extra">-A INPUT -j nixos-fw</div><div class="gmail_extra">-A FORWARD -s <a href="http://10.0.0.0/24">10.0.0.0/24</a> -d <a href="http://10.0.0.2/32">10.0.0.2/32</a> -i eth1 -m policy --dir in --pol ipsec --reqid 1 --proto esp -j ACCEPT</div><div class="gmail_extra">-A FORWARD -s <a href="http://10.0.0.2/32">10.0.0.2/32</a> -d <a href="http://10.0.0.0/24">10.0.0.0/24</a> -o eth1 -m policy --dir out --pol ipsec --reqid 1 --proto esp -j ACCEPT</div><div class="gmail_extra">-A OUTPUT -s <a href="http://10.0.0.2/32">10.0.0.2/32</a> -d <a href="http://10.0.0.0/24">10.0.0.0/24</a> -o eth1 -m policy --dir out --pol ipsec --reqid 1 --proto esp -j ACCEPT</div><div class="gmail_extra">-A OUTPUT -m policy --dir out --pol ipsec -j NFLOG --nflog-group 5</div><div class="gmail_extra">-A OUTPUT -p udp -m multiport --dports 500,4500 -j NFLOG --nflog-group 5</div><div class="gmail_extra">-A OUTPUT -p ah -j NFLOG --nflog-group 5</div><div class="gmail_extra">-A OUTPUT -p esp -j NFLOG --nflog-group 5</div><div class="gmail_extra">-A nixos-fw -i lo -j nixos-fw-accept</div><div class="gmail_extra">-A nixos-fw -m conntrack --ctstate RELATED,ESTABLISHED -j nixos-fw-accept</div><div class="gmail_extra">-A nixos-fw -p icmp -m icmp --icmp-type 8 -j nixos-fw-accept</div><div class="gmail_extra">-A nixos-fw -j nixos-fw-log-refuse</div><div class="gmail_extra">-A nixos-fw-accept -j ACCEPT</div><div class="gmail_extra">-A nixos-fw-log-refuse -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -j LOG --log-prefix "rejected connection: " --log-level 6</div><div class="gmail_extra">-A nixos-fw-log-refuse -m pkttype ! --pkt-type unicast -j nixos-fw-refuse</div><div class="gmail_extra">-A nixos-fw-log-refuse -j nixos-fw-refuse</div><div class="gmail_extra">-A nixos-fw-refuse -j DROP</div><div><br></div><div class="gmail_extra"><div class="gmail_extra">[moon] $ iptables -S </div><div class="gmail_extra">-P INPUT ACCEPT</div><div class="gmail_extra">-P FORWARD ACCEPT</div><div class="gmail_extra">-P OUTPUT ACCEPT</div><div class="gmail_extra">-N nixos-fw</div><div class="gmail_extra">-N nixos-fw-accept</div><div class="gmail_extra">-N nixos-fw-log-refuse</div><div class="gmail_extra">-N nixos-fw-refuse</div><div class="gmail_extra">-A INPUT -m addrtype ! --dst-type LOCAL -m policy --dir in --pol ipsec -j NFLOG --nflog-group 5</div><div class="gmail_extra">-A INPUT -m addrtype --dst-type LOCAL -m policy --dir in --pol ipsec -j NFLOG --nflog-group 5</div><div class="gmail_extra">-A INPUT -p udp -m multiport --dports 500,4500 -j NFLOG --nflog-group 5</div><div class="gmail_extra">-A INPUT -p ah -j NFLOG --nflog-group 5</div><div class="gmail_extra">-A INPUT -p esp -j NFLOG --nflog-group 5</div><div class="gmail_extra">-A INPUT -j nixos-fw</div><div class="gmail_extra">-A FORWARD -s <a href="http://10.0.0.2/32">10.0.0.2/32</a> -d <a href="http://10.0.0.0/24">10.0.0.0/24</a> -i eth1 -m policy --dir in --pol ipsec --reqid 2 --proto esp -j ACCEPT</div><div class="gmail_extra">-A FORWARD -s <a href="http://10.0.0.0/24">10.0.0.0/24</a> -d <a href="http://10.0.0.2/32">10.0.0.2/32</a> -o eth1 -m policy --dir out --pol ipsec --reqid 2 --proto esp -j ACCEPT</div><div class="gmail_extra">-A FORWARD -s <a href="http://10.0.0.1/32">10.0.0.1/32</a> -d <a href="http://10.0.0.0/24">10.0.0.0/24</a> -i eth1 -m policy --dir in --pol ipsec --reqid 1 --proto esp -j ACCEPT</div><div class="gmail_extra">-A FORWARD -s <a href="http://10.0.0.0/24">10.0.0.0/24</a> -d <a href="http://10.0.0.1/32">10.0.0.1/32</a> -o eth1 -m policy --dir out --pol ipsec --reqid 1 --proto esp -j ACCEPT</div><div class="gmail_extra">-A OUTPUT -m policy --dir out --pol ipsec -j NFLOG --nflog-group 5</div><div class="gmail_extra">-A OUTPUT -p udp -m multiport --dports 500,4500 -j NFLOG --nflog-group 5</div><div class="gmail_extra">-A OUTPUT -p ah -j NFLOG --nflog-group 5</div><div class="gmail_extra">-A OUTPUT -p esp -j NFLOG --nflog-group 5</div><div class="gmail_extra">-A nixos-fw -i lo -j nixos-fw-accept</div><div class="gmail_extra">-A nixos-fw -m conntrack --ctstate RELATED,ESTABLISHED -j nixos-fw-accept</div><div class="gmail_extra">-A nixos-fw -p udp -m udp --dport 4500 -j nixos-fw-accept</div><div class="gmail_extra">-A nixos-fw -p udp -m udp --dport 500 -j nixos-fw-accept</div><div class="gmail_extra">-A nixos-fw -p icmp -m icmp --icmp-type 8 -j nixos-fw-accept</div><div class="gmail_extra">-A nixos-fw -j nixos-fw-log-refuse</div><div class="gmail_extra">-A nixos-fw-accept -j ACCEPT</div><div class="gmail_extra">-A nixos-fw-log-refuse -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -j LOG --log-prefix "rejected connection: " --log-level 6</div><div class="gmail_extra">-A nixos-fw-log-refuse -m pkttype ! --pkt-type unicast -j nixos-fw-refuse</div><div class="gmail_extra">-A nixos-fw-log-refuse -j nixos-fw-refuse</div><div class="gmail_extra">-A nixos-fw-refuse -j DROP</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 9 September 2017 at 15:34, Noel Kuntze <span dir="ltr"><<a href="mailto:noel.kuntze+strongswan-users-ml@thermi.consulting" target="_blank">noel.kuntze+strongswan-users-<wbr>ml@thermi.consulting</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
Check your iptables rules.<br>
<br>
Kind regards<br>
<br>
Noel<br>
<span><br>
On <a href="tel:09.09.2017%2014" value="+31909201714" target="_blank">09.09.2017 14</a>:06, Bas van Dijk wrote:<br>
> Dear list,<br>
><br>
</span>> (I accidentally sent a previous message <<a href="https://groups.google.com/forum/#%21topic/strongswan-users/2ytikPcg7jA" rel="noreferrer" target="_blank">https://groups.google.com/for<wbr>um/#%21topic/strongswan-users/<wbr>2ytikPcg7jA</a>> to the read-only <a href="mailto:strongswan-users@googlegroups.com" target="_blank">strongswan-users@googlegroups.<wbr>com</a> <mailto:<a href="mailto:strongswan-users@googlegroups.com" target="_blank">strongswan-users@googl<wbr>egroups.com</a>>. So let's try the real list.)<br>
<span>><br>
> I'm working on another NixOS strongswan test. This time I have two roadwarriors alice and carol that set up a connection to gateway moon. They request a virtual IP. The gateway moon assigns virtual IP addresses from a pool per roadwarrior containing a single IP address. Authentication is based on X.509 certificates. In order to test the tunnel alice and carol ping each other. The test configuration can be found in:<br>
><br>
> <a href="https://github.com/LumiGuide/nixpkgs/blob/strongswan-swanctl-pubkey-test/nixos/tests/strongswan-swanctl-pubkey.nix" rel="noreferrer" target="_blank">https://github.com/LumiGuide/n<wbr>ixpkgs/blob/strongswan-swanctl<wbr>-pubkey-test/nixos/tests/<wbr>strongswan-swanctl-pubkey.nix</a><br>
><br>
> The roadwarriors alice and carol can successfully establish a CHILD_SA with the gateway moon. The problem is that the roadwarriors can't ping eachother. <br>
><br>
> This is a tcpdump on alice while initiating the CHILD_SA and trying to ping carol:<br>
><br>
> [alice] $ tcpdump -s 0 -n -i nflog:5<br>
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode<br>
> listening on nflog:5, link-type NFLOG (Linux netfilter log messages), capture size 262144 bytes<br>
> # swanctl -i --child alice<br>
> 11:05:07.318185 IP 192.168.1.1.500 > 192.168.1.3.500: isakmp: parent_sa ikev2_init[I]<br>
> 11:05:07.318291 IP 192.168.1.3.500 > 192.168.1.1.500: isakmp: parent_sa ikev2_init[R]<br>
> 11:05:07.318296 IP 192.168.1.1.4500 > 192.168.1.3.4500: NONESP-encap: isakmp: child_sa ikev2_auth[I]<br>
> 11:05:07.318308 IP 192.168.1.1.4500 > 192.168.1.3.4500: NONESP-encap: isakmp: child_sa ikev2_auth[I]<br>
> 11:05:08.346181 IP 192.168.1.3.4500 > 192.168.1.1.4500: NONESP-encap: isakmp: child_sa ikev2_auth[R]<br>
> 11:05:08.346196 IP 192.168.1.3.4500 > 192.168.1.1.4500: NONESP-encap: isakmp: child_sa ikev2_auth[R]<br>
> # ping -c 1 10.0.0.2<br>
</span>> 11:05:15.898172 IP 192.168.1.1 > 10.0.0.2 <<a href="http://10.0.0.2" rel="noreferrer" target="_blank">http://10.0.0.2</a>>: ICMP echo request, id 1120, seq 1, length 64<br>
> 11:05:15.898200 IP 192.168.1.1 > 10.0.0.2 <<a href="http://10.0.0.2" rel="noreferrer" target="_blank">http://10.0.0.2</a>>: ICMP echo request, id 1120, seq 1, length 64<br>
> 11:05:15.898205 IP 192.168.1.1 > 192.168.1.3 <<a href="http://192.168.1.3" rel="noreferrer" target="_blank">http://192.168.1.3</a>>: ESP(spi=0xc6877d56,seq=0x1), length 136<br>
<span>><br>
> So it looks like the ping packet gets encapsulated and send to moon. This is the dump on moon:<br>
><br>
> [moon] $ tcpdump -s 0 -n -i nflog:5<br>
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode<br>
> listening on nflog:5, link-type NFLOG (Linux netfilter log messages), capture size 262144 bytes<br>
> 11:05:07.170190 IP 192.168.1.1.500 > 192.168.1.3.500: isakmp: parent_sa ikev2_init[I]<br>
> 11:05:07.170218 IP 192.168.1.3.500 > 192.168.1.1.500: isakmp: parent_sa ikev2_init[R]<br>
> 11:05:07.170221 IP 192.168.1.1.4500 > 192.168.1.3.4500: NONESP-encap: isakmp: child_sa ikev2_auth[I]<br>
> 11:05:07.170227 IP 192.168.1.1.4500 > 192.168.1.3.4500: NONESP-encap: isakmp: child_sa ikev2_auth[I]<br>
> 11:05:08.225827 IP 192.168.1.3.4500 > 192.168.1.1.4500: NONESP-encap: isakmp: child_sa ikev2_auth[R]<br>
> 11:05:08.225843 IP 192.168.1.3.4500 > 192.168.1.1.4500: NONESP-encap: isakmp: child_sa ikev2_auth[R]<br>
><br>
</span>> 11:05:15.777787 IP 192.168.1.1 > 192.168.1.3 <<a href="http://192.168.1.3" rel="noreferrer" target="_blank">http://192.168.1.3</a>>: ESP(spi=0xc6877d56,seq=0x1), length 136<br>
<span>><br>
> So moon receives the encapsulated ping message from alice but it never reroutes it to carol. Is this caused by a bad routing configuration? These are the routes on alice and her auto-generated swanctl configuration:<br>
><br>
> [alice] $ ip route list table 220<br>
</span>> <a href="http://10.0.0.0/24" rel="noreferrer" target="_blank">10.0.0.0/24</a> <<a href="http://10.0.0.0/24" rel="noreferrer" target="_blank">http://10.0.0.0/24</a>> via 192.168.1.3 dev eth1 proto static src 192.168.1.1 <br>
<span>><br>
> [alice] $ cat /etc/swanctl/swanctl.conf<br>
> connections {<br>
> alice {<br>
> children {<br>
> alice {<br>
</span>> remote_ts = <a href="http://10.0.0.0/24" rel="noreferrer" target="_blank">10.0.0.0/24</a> <<a href="http://10.0.0.0/24" rel="noreferrer" target="_blank">http://10.0.0.0/24</a>><br>
<span>> start_action = trap<br>
> updown = /nix/store/jdcviy5z25xamq35g8k<wbr>9qbdpskkx3w9g-strongswan-5.6.<wbr>0/libexec/ipsec/_updown iptables<br>
> }<br>
> }<br>
> local-main {<br>
> auth = pubkey<br>
> certs = aliceCert.der<br>
> id = alice<br>
> }<br>
> remote-main {<br>
> auth = pubkey<br>
> id = moon<br>
> }<br>
> remote_addrs = moon<br>
> version = 2<br>
> vips = 0.0.0.0<br>
> }<br>
> }<br>
><br>
> Routing table 220 is empty on moon. Is that how it's supposed to be? This is its auto-generated swanctl configuration:<br>
><br>
> [moon] $ cat /etc/swanctl/swanctl.conf <br>
> connections {<br>
> alice {<br>
> children {<br>
> alice {<br>
</span>> local_ts = <a href="http://10.0.0.0/24" rel="noreferrer" target="_blank">10.0.0.0/24</a> <<a href="http://10.0.0.0/24" rel="noreferrer" target="_blank">http://10.0.0.0/24</a>><br>
<span>> updown = /nix/store/jdcviy5z25xamq35g8k<wbr>9qbdpskkx3w9g-strongswan-5.6.<wbr>0/libexec/ipsec/_updown iptables<br>
> }<br>
> }<br>
> local-main {<br>
> auth = pubkey<br>
> certs = moonCert.der<br>
> id = moon<br>
> }<br>
> pools = alice<br>
> remote-main {<br>
> auth = pubkey<br>
> id = alice<br>
> }<br>
> version = 2<br>
> }<br>
> carol {<br>
> children {<br>
> carol {<br>
</span>> local_ts = <a href="http://10.0.0.0/24" rel="noreferrer" target="_blank">10.0.0.0/24</a> <<a href="http://10.0.0.0/24" rel="noreferrer" target="_blank">http://10.0.0.0/24</a>><br>
<div class="gmail-m_-29041415175895515HOEnZb"><div class="gmail-m_-29041415175895515h5">> updown = /nix/store/jdcviy5z25xamq35g8k<wbr>9qbdpskkx3w9g-strongswan-5.6.<wbr>0/libexec/ipsec/_updown iptables<br>
> }<br>
> }<br>
> local-main {<br>
> auth = pubkey<br>
> certs = moonCert.der<br>
> id = moon<br>
> }<br>
> pools = carol<br>
> remote-main {<br>
> auth = pubkey<br>
> id = carol<br>
> }<br>
> version = 2<br>
> }<br>
> }<br>
> pools {<br>
> alice {<br>
> addrs = 10.0.0.1<br>
> }<br>
> carol {<br>
> addrs = 10.0.0.2<br>
> }<br>
> }<br>
><br>
> I'm sure I'm not configuring something correctly. Can somebody point me in the right direction to get this test succeeding?<br>
><br>
> Regards,<br>
><br>
> Bas<br>
><br>
><br>
><br>
<br>
<br>
</div></div></blockquote></div><br></div></div>