I have more information regarding the reason why pluto crashes...
The last logs before crash are:
-----------------------------------------------------------------------------------------------------------------
Apr 20 17:32:31 base pluto[573]: | pfkey_lib_debug:pfkey_msg_parse:
parsing ext type=27(X-NAT-T-sport) remain=6.
Apr 20 17:32:31 base pluto[573]: | pfkey_lib_debug:pfkey_msg_parse:
remain=6 ext_type=27(X-NAT-T-sport) ext_len=1 parsing ext 0p0x8100130
with parser pfkey_x_ext_nat_t_type_parse.
Apr 20 17:32:31 base pluto[573]: | pfkey_lib_debug:pfkey_msg_parse:
Extension 27(X-NAT-T-sport) parsed.
Apr 20 17:32:31 base pluto[573]: | pfkey_lib_debug:pfkey_msg_parse:
parsing ext type=28(X-NAT-T-dport) remain=5.
Apr 20 17:32:31 base pluto[573]: | pfkey_lib_debug:pfkey_msg_parse:
remain=5 ext_type=28(X-NAT-T-dport) ext_len=1 parsing ext 0p0x8100138
with parser pfkey_x_ext_nat_t_port_parse.
Apr 20 17:32:31 base pluto[573]: | pfkey_lib_debug:pfkey_msg_parse:
Extension 28(X-NAT-T-dport) parsed.
Apr 20 17:32:31 base pluto[573]: | pfkey_lib_debug:pfkey_msg_parse:
parsing ext type=29(X-NAT-T-OA) remain=4.
Apr 20 17:32:31 base pluto[573]: | pfkey_lib_debug:pfkey_msg_parse:
remain=4 ext_type=29(X-NAT-T-OA) ext_len=1 parsing ext 0p0x8100140 with
parser pfkey_x_ext_nat_t_port_parse.
Apr 20 17:32:31 base pluto[573]: | pfkey_lib_debug:pfkey_msg_parse:
Extension 29(X-NAT-T-OA) parsed
-----------------------------------------------------------------------------------------------------------------
So I assumed that NAT-T is the reason for crash and commented
nat_traversal=yes... and yes, it does not crash anymore.
Thanks,
Andriy
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
