?
I have done the reboots and config checking and no dice.
 
I done lots of testing in the last little bit. 
 
Here are the boxes lets call them
Central 1 - Running 94.10
Central 2 - Running 95.4
 
Remote 1 - Running 94.10
 
 
I have an IPSec connection work for a long time between Central 1 and Remote 1.
Central 1 is setup to accept from mobile clients and Remote 1 is the mobile 
client.
When looking at Remote 1 I can see the proper SPDs in place (no matter if the 
ipsec link is actually up or down).
 
If I backup the config upgrade Remote 1 to 95.8, restore config, now the 
connection will no longer come up and I no longer will see any SPDs in the 
IPSec status.
I double checked to make sure all the options are still correct.
 
Now from a Host standpoint I can get Remote 1 (mobile client ) running 94.10 to 
connect into Central 2 running 95.4.  I'm guessing because with mobile clients 
you will never know the remote ip / lan block ahead of time.
 
Thanks
John
 
 
 
 
 

________________________________

From: Scott Ullrich [mailto:[EMAIL PROTECTED]
Sent: Sun 12/11/2005 2:11 PM
To: [email protected]
Subject: Re: [pfSense Support] IPSec Broken in 95.8 Embedded?



Nothing has changed so double check everything and reboot both endpoints.

On 12/11/05, John Cianfarani <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> Was using Ipsec tunnels both standard and mobile clients in 94.10 with it
> working fine.
>
> After the upgrade to 95.8 (also tried 95.4) tunnels will no longer come up.
>
> I did notice that there is no SPD defined anymore, I don't know if that is a
> cosmetic issue or a no policies are actually being applied.
>
> But I found this in the the IPSec Log
>
>
>
> Dec 11 13:41:18 racoon: DEBUG: pfkey X_SPDDUMP failed: No such file or
> directory
>
> Dec 11 13:41:18 racoon: DEBUG: get pfkey X_SPDDUMP message
>
>
>
> As always if you need any moew logs/debug let me know.
>
>
>
>
>
> Thanks
>
> John

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


<<winmail.dat>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to