ipsec.conf macros

2011-11-14 Thread Jakob Alvermark
= 192.168.1.0/24 network_b = 192.168.2.0/24 network_list = { 192.168.1.0/24 192.168.2.0/24 } Is is supposed to work, or is it a bug? Or is there another way of doing it, am I doing it wrong? Thank you, Jakob Alvermark jakob.alverm...@bsdlabs.com BSDLabs AB Solna, Sweden 556759-7652

Re: IPSEC tunnels failing intermittently

2011-05-11 Thread Jakob Alvermark
Has anyone filed a bug report or should I send this to bugs@? Regards, Jakob Alvermark On 6 maj 2011, at 11:33, Jakob Alvermark wrote: A little more info: I have now ENCDEBUG enabled on both ends in the lab. When one tunnel fails I get the same error on both machines: May 4 12:27:55

Re: IPSEC tunnels failing intermittently

2011-05-06 Thread Jakob Alvermark
Henderson s...@spacehopper.org wrote: I see something similar which I've been trying to track down but not really succeeding. The thing we have in common is multiple subnets, I wonder if this is a factor... (and this setup has always been post-4.4 On 2011-05-02, Jakob Alvermark jakob.alverm

IPSEC tunnels failing intermittently

2011-05-02 Thread Jakob Alvermark
. ipsec.conf is very simple, just one line: ike esp from {192.168.1.9/24 172.16.1.0/24} to {192.168.31.0/24 192.168.32.254} local xxx.xxx.xxx.97 peer xxx.xxx.xxx.99 Public keys copied across, isakmpd started with flags -K -v Does anyone have any ideas about this? Thank you Jakob Alvermark jakob.alverm