This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

rekey=no doesn't work?

Hi,

I have an scenario with ASL 6.3.03 and VPN road warrior connections. I have detected some problems when ASL tries to do the phase one renegotiations, so I tried to force it to never be the initiator. I found it is possible adding to the ipsec.conf file the line "rekey=no", but it doesn't work since when I restart the IPsec service it doesn't save my changes.

There must be something in the ASL that doesn't allow me to change the ipsec.conf file, do you know some way to manage this?. I really appreciate your help with this. Thanks.

-langoleer

This thread was automatically locked due to age.

Parents

0 NimmdirKeks over 18 years ago

Don't know what you mean, but par default, rekey is set to "no" with all the roadwarriors configurations. Seems that you are using a wrong config.
Cancel
Vote Up 0 Vote Down

Cancel
0 langoleer over 18 years ago in reply to NimmdirKeks

Hi thanks for you response,

I could show you that ASL6.303 tries to renegotiate the phase one, from a packet sniffing that I did. I just want that ASL never do that, just let it to the roadwarriors. Any further ideas?, thanks in advance.

-langoleer
Cancel
Vote Up 0 Vote Down

Cancel
0 NimmdirKeks over 18 years ago in reply to langoleer

Speaking roadwarrior config here. The "rekey=no" is set per default in those configs, if it is not present, you don't have a roadwarrior configured.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 NimmdirKeks over 18 years ago in reply to langoleer

Speaking roadwarrior config here. The "rekey=no" is set per default in those configs, if it is not present, you don't have a roadwarrior configured.
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data