('binary' encoding is not supported, stored as-is)
Hi Sam,
First, thanks for your help!
I Did some changes here and now I`v found a diferrent error...
May 23 13:33:18 vpngateway Pluto[11239]: "vpn" 200.192.47.43 #3: Issuer
CRL not found
May 23 13:33:18 vpngateway Pluto[11239]: "vpn" 200.192.47.43 #3: Issuer
CRL not found
May 23 13:33:18 vpngateway Pluto[11239]: "vpn" 200.192.47.43 #3: no
suitable connection for peer 'CN=suporte.trust.com.br'
May 23 13:34:00 vpngateway Pluto[11239]: "vpn" 200.192.47.43 #2: max
number of retransmissions (2) reached STATE_MAIN_R2
May 23 13:34:27 vpngateway Pluto[11239]: "vpn" 200.192.47.43 #3: max
number of retransmissions (2) reached STATE_MAIN_R2
May 23 13:34:27 vpngateway Pluto[11239]: "vpn" 200.192.47.43: deleting
connection "vpn" instance with peer 200.192.47.43
I`v tried to change the CN from the e-mail address to my hostname.. but
nothing yet.. Do know you what could be wrong !??? I've tried to search
on the mailing list archive but nothing helpful.. :((( I believe that is
a "little" problem... (for those people who realy undestand fresswan like you).
Thanks for your help!
Robson
> -----BEGIN PGP SIGNED MESSAGE-----
>
> On Thu, 23 May 2002 rgomes2_at_trust.com.br wrote:
>
> > Hello All,
> >
> > May 23 09:05:57 vpngateway Pluto[6876]: "RW_Cert_SecuredConnection"
> > 200.192.2.43 8: ignoring informational payload, type
> IPSEC_INITIAL_CONTACT
> > May 23 09:05:57 vpngateway Pluto[6876]: "RW_Cert_SecuredConnection"
> > 200.192.2.43 8: Peer ID is ID_DER_ASN1_DN: 'C=BR, ST=SP, L=S?o Paulo,
> > O=Trust Consultores, OU=Desenvolvimento, CN=rgomes_at_trust.com.br,
> > E=rgomes_at_trust.com.br'
> > ay 23 09:05:57 vpngateway Pluto[6876]: "RW_Cert_SecuredConnection"
> > 200.192.2.43 8: sent MR3, ISAKMP SA established
> > May 23 09:05:57 vpngateway Pluto[6876]: "RW_Cert_SecuredConnection"
> > 200.192.2.43 8: Informational Exchange message for an established ISAKMP
> > SA must be encrypted
>
> The Informational Exchange message is SSH Sentinel trying to tell
> FreeS/WAN that it has a problem. Check SSH Sentinel's logs to see what
> error it is encountering. In many cases, this sort of error
> indicates a certificate problem.
>
> Sam Sgro
> sam_at_freeswan.org
>
> -----BEGIN PGP SIGNATURE-----
> Version: 2.6.3ia
> Charset: noconv
> Comment: For the matching public key, finger the Reply-To: address.
>
> iQCVAwUBPO0aBkOSC4btEQUtAQF3BgQAr8bGQc5ZfSn9HyMI5U83ddKPO78CibSx
> +DpxIJqCrTSkC3wP3HlbRFdyJEGWCIK0WXiXkI18G5cd+i24Y2DkAmzPonIkYpHB
> JjJ9JPvAI+vo80PUQc/8rw0gKyC4TilKCCX8S9AaVXzH2M1kSCKf7NlYyRm2lB2w
> 9OCrrn+J4+w=
> =tYgN
> -----END PGP SIGNATURE-----
>
_______________________________________________
Users mailing list
Users_at_lists.freeswan.org
http://lists.freeswan.org/mailman/listinfo/users
This archive was generated by hypermail 2.1.3 : Mon Jul 29 2002 - 05:20:05 CEST