Actions
Bug #3311
closed
After enabling save password permission racoon die with (core dumped)
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
IPsec
Target version:
-
Start date:
11/11/2013
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.1
Affected Architecture:
i386
Description
Hi all.
I'd configured IPSec, all was ok. But after enabling save password permission racoon die with (core dumped) message in system log.
Nov 11 16:25:00 kernel: pid 5200 (racoon), uid 0: exited on signal 11 (core dumped) Nov 11 16:24:01 php: /status_services.php: Forcefully reloading IPsec racoon daemon Nov 11 16:22:36 kernel: pid 81272 (racoon), uid 0: exited on signal 11 (core dumped) Nov 11 16:22:30 php: /status_services.php: Forcefully reloading IPsec racoon daemon
Whats happens in IPSec log:
Nov 11 16:24:56 racoon: INFO: login succeeded for user "darhel" Nov 11 16:24:56 racoon: user 'darhel' authenticated Nov 11 16:24:55 racoon: INFO: Using port 0 Nov 11 16:24:48 racoon: [Self]: INFO: ISAKMP-SA established x.x.x.x[4500]-109.188.125.39[9385] spi:e988589b3654344a:6148b7c1b37a035d Nov 11 16:24:48 racoon: INFO: Sending Xauth request Nov 11 16:24:48 racoon: INFO: NAT detected: PEER Nov 11 16:24:48 racoon: INFO: NAT-D payload #1 doesn't match Nov 11 16:24:48 racoon: [109.188.125.39] INFO: Hashing 109.188.125.39[9385] with algo #2 Nov 11 16:24:48 racoon: INFO: NAT-D payload #0 verified Nov 11 16:24:48 racoon: [Self]: [x.x.x.x] INFO: Hashing x.x.x.x[4500] with algo #2 Nov 11 16:24:48 racoon: [Self]: INFO: NAT-T: ports changed to: 109.188.125.39[9385]<->x.x.x.x[4500] Nov 11 16:24:48 racoon: INFO: Adding xauth VID payload. Nov 11 16:24:48 racoon: [Self]: [x.x.x.x] INFO: Hashing x.x.x.x[500] with algo #2 Nov 11 16:24:48 racoon: [109.188.125.39] INFO: Hashing 109.188.125.39[500] with algo #2 Nov 11 16:24:48 racoon: INFO: Adding remote and local NAT-D payloads. Nov 11 16:24:48 racoon: [109.188.125.39] INFO: Selected NAT-T version: RFC 3947 Nov 11 16:24:48 racoon: INFO: received Vendor ID: DPD Nov 11 16:24:48 racoon: INFO: received Vendor ID: CISCO-UNITY Nov 11 16:24:48 racoon: INFO: received Vendor ID: draft-ietf-ipsra-isakmp-xauth-06.txt Nov 11 16:24:48 racoon: INFO: received Vendor ID: draft-ietf-ipsec-nat-t-ike-02 Nov 11 16:24:48 racoon: INFO: received Vendor ID: draft-ietf-ipsec-nat-t-ike-02 Nov 11 16:24:48 racoon: INFO: received Vendor ID: draft-ietf-ipsec-nat-t-ike-03 Nov 11 16:24:48 racoon: INFO: received Vendor ID: draft-ietf-ipsec-nat-t-ike-04 Nov 11 16:24:48 racoon: INFO: received Vendor ID: draft-ietf-ipsec-nat-t-ike-05 Nov 11 16:24:48 racoon: INFO: received Vendor ID: draft-ietf-ipsec-nat-t-ike-06 Nov 11 16:24:48 racoon: INFO: received Vendor ID: draft-ietf-ipsec-nat-t-ike-07 Nov 11 16:24:48 racoon: INFO: received Vendor ID: draft-ietf-ipsec-nat-t-ike-08 Nov 11 16:24:48 racoon: INFO: received Vendor ID: RFC 3947 Nov 11 16:24:48 racoon: INFO: received broken Microsoft ID: FRAGMENTATION Nov 11 16:24:48 racoon: INFO: begin Aggressive mode.
So after "login succeeded" service dies.. After restart - same thing.
Updated by Koichi Tanaka about 12 years ago
deleted ipsec config, configured once more.. no more problems. sorry. strange thing.
cant find - how to delete my error report?
Updated by Chris Buechler about 12 years ago
- Status changed from New to Closed
if you can find a way to reliably replicate, please report back. I'll close for now, haven't seen that happen and doesn't appear to be replicable.
Updated by Jim Pingle almost 12 years ago
Looks like this might be the same as #3417
Actions