<div>Paul,</div>
<div> </div>
<div>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:
</div>
<div> </div>
<div>fatal error in "systema-systemb": ID "%any" cannot have RSA key.</div>
<div> </div>
<div>So I then modified the configuration file on systemb to include systema's actual ip <a href="http://100.100.110.2">100.100.110.2</a>. 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:
</div>
<div> </div>
<div>"systema-systemb" malformed payload in packet</div>
<div>| payload malformed after IV</div>
<div>| 66 45 9c 32 b7 02 68 4e</div>
<div>"systema-sytemb" #1: sending notification PAYLOAD_MALFORMED to <a href="http://100.100.110.2:4500">100.100.110.2:4500</a></div>
<div> </div>
<div>I appreciate your help with this very much!</div>
<div> </div>
<div> </div>
<div>Josh</div>
<div> </div>
<div><br><br> </div>
<div><span class="gmail_quote">On 2/8/07, <b class="gmail_sendername">Paul Wouters</b> <<a href="mailto:paul@xelerance.com">paul@xelerance.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Thu, 8 Feb 2007, Josh wrote:<br><br>> After further investigation I found the following in the logs:
<br>><br>> packet from <a href="http://100.100.110.2:500">100.100.110.2:500</a> initial Main Mode message received on<br>> <a href="http://192.168.1.3:500">192.168.1.3:500</a> but no connection has bee authorized.
<br>><br>> This is further that I have gotten but I am not sure how to proceed.<br><br>Your connection is very different from what you get, or the connection<br>failed to load. What does ipsec auto --add systema-systemb on
<br><a href="http://192.168.1.3">192.168.1.3</a> say?<br><br>Paul<br></blockquote></div><br>