The original message was received at Wed, 19 Feb 2014 14:48:47 -0500
from paul@localhost
----- The following addresses had permanent fatal errors -----
<'[email protected]'>
(reason: 501 5.1.3 Bad recipient address syntax)
(expanded from: <'[email protected]'>)
----- Transcript of session follows -----
... while talking to [127.0.0.1]:
>>> DATA
<<< 501 5.1.3 Bad recipient address syntax
554 5.0.0 Service unavailable
Reporting-MTA: dns; bofh.nohats.ca
Arrival-Date: Wed, 19 Feb 2014 14:48:47 -0500
Final-Recipient: RFC822; '[email protected]'
Action: failed
Status: 5.1.3
Remote-MTA: DNS; [127.0.0.1]
Diagnostic-Code: SMTP; 501 5.1.3 Bad recipient address syntax
Last-Attempt-Date: Wed, 19 Feb 2014 14:48:48 -0500
--- Begin Message ---
On Wed, 19 Feb 2014, Sean Smith wrote:
Subject: [Swan] FW: IPSec VPN configuration issues. AVX instrucions not
detetced / stuck on DDNS phase 2
Also, in the secure and messages files I can see that Phase 1 completes,
but it seems to get stuck on EVENT_PENDING_DDNS. It does queue up
EVENT_PENDING_PHASE2 but never gets by the DDNS.
It's not really stuck there. Those are timed events that repeat.
Feb 19 09:45:31 localhost pluto[8835]: | *received whack message
Feb 19 09:45:31 localhost pluto[8835]: initiating all conns with
alias='aliantVPN'
Feb 19 09:45:31 localhost pluto[8835]: | * processed 0 messages from
cryptographic helpers
Feb 19 09:45:31 localhost pluto[8835]: | next event EVENT_PENDING_DDNS in 59
seconds
Feb 19 09:45:31 localhost pluto[8835]: | next event EVENT_PENDING_DDNS in 59
seconds
Feb 19 09:45:31 localhost pluto[8835]: | reaped addconn helper child
It looks like perhaps that connection did not load?
Run:
ipsec auto --add aliantVPN
ipsec auto --up aliantVPN
That should tell us more,
Paul
--- End Message ---
_______________________________________________
Swan mailing list
[email protected]
https://lists.libreswan.org/mailman/listinfo/swan
