Lukasz Spaleniak wrote: The relevant policies are these:
> fw-wro:~# setkey -DP > 192.168.6.0/24[any] 10.1.0.0/24[any] any > in ipsec > esp/tunnel/195.205.11.34-195.205.101.2/unique#16453 > created: Jan 13 14:10:16 2008 lastused: > lifetime: 0(s) validtime: 0(s) > spid=2552 seq=1 pid=24325 > refcnt=1 ... > 192.168.6.0/24[any] 10.1.0.0/24[any] any > out ipsec > esp/tunnel/195.205.101.2-195.205.142.34/unique#16458 > created: Jan 13 14:10:16 2008 lastused: Jan 22 21:37:06 2008 > lifetime: 0(s) validtime: 0(s) > spid=2617 seq=9 pid=24325 > refcnt=1 Given that the netfilter policy match is not recognizing vpn->vpn traffic as matching the first policy, I guess you will need to augment the definition of the vpn zone as follows: hosts: #ZONE HOST(S) OPTIONS vpn eth0:192.168.6.0/24,195.205.11.34 ipsec vpn eth0:10.1.0.0/24,195.205.142.34 ipsec vpn eth0:192.168.10.0/24,84.40.238.125 ipsec vpn eth0:192.168.6.0/24, vpn eth0:10.1.0.0/24 vpn eth0:192.168.10.0/24 I notice that you don't have any SPs for the gateways themselves. So you should probably leave them out of the vpn zone definition altogether (although I left them in above). -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
