[Openswan Users] Configuration Help

[Josh]

Paul,

When I used the suggestion configuration information, there did not appear
to be any connection attempt from systema to systemb.  When I ran ipsec auto
--add systema-systemb  on systemb I received the following error:

fatal error in "systema-systemb": ID "%any" cannot have RSA key.

So I then modified the configuration file on systemb to include systema's
actual ip 100.100.110.2.  Then I ran  ipsec auto --add systema-systemb which
did not produce any errors.  Now when I restart ipsec on both systems I get
the following error:

"systema-systemb" malformed payload in packet
| payload malformed after IV
| 66 45 9c 32 b7 02 68 4e
"systema-sytemb" #1: sending notification PAYLOAD_MALFORMED to
100.100.110.2:4500

I appreciate your help with this very much!


Josh




On 2/8/07, Paul Wouters <paul at xelerance.com> wrote:
>
> On Thu, 8 Feb 2007, Josh wrote:
>
> > After further investigation I found the following in the logs:
> >
> > packet from 100.100.110.2:500 initial Main Mode message received on
> > 192.168.1.3:500 but no connection has bee authorized.
> >
> > This is further that I have gotten but I am not sure how to proceed.
>
> Your connection is very different from what you get, or the connection
> failed to load. What does ipsec auto --add systema-systemb on
> 192.168.1.3 say?
>
> Paul
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openswan.org/pipermail/users/attachments/20070209/59766608/attachment.html