Note: This archive passes through spamassassin. Every mail marked with the subject "*****SPAM*****" has exceed a certain threshold of spam-like behaviour.

Re: [Users] Problems using freeswan an sentinel

From: John A. Sullivan III (John.Sullivan_at_nexusmgmt.com)
Date: Mon Apr 22 2002 - 11:50:36 CEST

Next message: Wasiq N: "[Users] problems with KLIPS"
Previous message: Ralf G. R. Bergs: "[Users] Re: [Bugs] Re: IPSec (FreeS/WAN) over ATM (CLIP): Oops after secure connection has been established"
In reply to: Mrnokia: "[Users] Problems using freeswan an sentinel"
Next in thread: Andreas Steffen: "Re: [Users] Problems using freeswan an sentinel"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

I'm going to guess that there's a mismatch in your IP addresses but that
is an ignorant guess - John

On Sun, 2002-04-21 at 15:59, Mrnokia wrote:
> Hello together, im using freeswan with the x509 patch it is running,
> when i do a Diagnose with sentinel ssh it says all ok, when making a vpn
> connection it says folowing in the messages log :
> Apr 19 20:11:14 LxSrv1 Pluto[3437]: packet from 192.168.99.102:500:
> ignoring Vendor ID payload
> Apr 19 20:11:14 LxSrv1 Pluto[3437]: "rw1" 192.168.99.102 #26: responding
> to Main Mode from unknown peer 192.168.99.102
> Apr 19 20:11:15 LxSrv1 Pluto[3437]: "rw1" 192.168.99.102 #26: ignoring
> informational payload, type IPSEC_INITIAL_CONTACT
> Apr 19 20:11:15 LxSrv1 Pluto[3437]: "rw1" 192.168.99.102 #26: Peer ID is
> ID_DER_ASN1_DN: 'C=DE, O=Kool AG, CN=rw1'
> Apr 19 20:11:15 LxSrv1 Pluto[3437]: "rw1" 192.168.99.102 #26: sent MR3,
> ISAKMP SA established
> Apr 19 20:11:15 LxSrv1 Pluto[3437]: "rw1" 192.168.99.102 #27: responding
> to Quick Mode
> Apr 19 20:11:16 LxSrv1 Pluto[3437]: "rw1" 192.168.99.102 #27: IPsec SA
> established
> Apr 19 20:11:16 LxSrv1 Pluto[3437]: "rw1" 192.168.99.102 #26: ignoring
> Delete SA payload
> Apr 19 20:11:16 LxSrv1 Pluto[3437]: "rw1" 192.168.99.102 #26: received
> and ignored informational message
> Apr 19 20:11:46 LxSrv1 Pluto[3437]: "rw1" 192.168.99.102 #26: ignoring
> Delete SA payload
> Apr 19 20:11:46 LxSrv1 Pluto[3437]: "rw1" 192.168.99.102 #26: received
> and ignored informational message
> Apr 19 20:11:56 LxSrv1 Pluto[3437]: packet from 192.168.99.102:500:
> ignoring Vendor ID payload
> Apr 19 20:11:56 LxSrv1 Pluto[3437]: "rw1" 192.168.99.102 #28: responding
> to Main Mode from unknown peer 192.168.99.102
> Apr 19 20:11:57 LxSrv1 Pluto[3437]: "rw1" 192.168.99.102 #28: ignoring
> informational payload, type IPSEC_INITIAL_CONTACT
> Apr 19 20:11:57 LxSrv1 Pluto[3437]: "rw1" 192.168.99.102 #28: Peer ID is
> ID_DER_ASN1_DN: 'C=DE, O=Kool AG, CN=rw1'
> Apr 19 20:11:57 LxSrv1 Pluto[3437]: "rw1" 192.168.99.102 #28: sent MR3,
> ISAKMP SA established
> Apr 19 20:12:19 LxSrv1 Pluto[3437]: "rw1" 192.168.99.102 #28:
> Informational Exchange message for an established ISAKMP SA must be
> encrypted
>
> What did it mean and what is wrong ?
>
> Cu Sascha
>
>
>

-- John A. Sullivan III Group Technology Director Nexus Management +1 207-985-7880 John.Sullivan_at_nexusmgmt.com

_______________________________________________ Users mailing list Users_at_lists.freeswan.org http://lists.freeswan.org/mailman/listinfo/users

Next message: Wasiq N: "[Users] problems with KLIPS"
Previous message: Ralf G. R. Bergs: "[Users] Re: [Bugs] Re: IPSec (FreeS/WAN) over ATM (CLIP): Oops after secure connection has been established"
In reply to: Mrnokia: "[Users] Problems using freeswan an sentinel"
Next in thread: Andreas Steffen: "Re: [Users] Problems using freeswan an sentinel"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.3 : Mon Jul 29 2002 - 05:19:52 CEST