Just a snippet from the manpage: lifetime time number timeunit; Define a lifetime of a certain time which will be proposed in the phase 1 negotiations. Any proposal will be accepted, and the attribute(s) will not be proposed to the peer if you do not specify it (them).They can be individually specified in each proposal.
So by default if you dont specify a lifetime, racoon accepts every proposal in phase1 offered by the client/remote side. So defining a lifetime would interfere with the default behavior. E.g. if you propose a lifetime in phase1 and the client has a different one, the chance is big that the initial assocation fails - not in your case so the remote concentrator is probably also setup to be not that picky about the lifetime. Unfortunately i dont have right now cisco equipment but i will try to get a pix for a few bucks and do a longtime test in my lab. Any ideas where to get one cheap is greatly appreciated. PS: the problem event queue overflowed will get fixed in the next release 0.8. Unfortunately that might not be the reason for the problem. Thanks Stefan -- Stefan Bauer ----------------------------------------- PGP: E80A 50D5 2D46 341C A887 F05D 5C81 5858 DCEF 8C34 -------- plzk.de - Linux - because it works ---------- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
