<div>Dear Paul:</div>
<div>I have installed iproute2 package in my kernel, but the execute result is still the same as before. The ping has something wrong. Please reference the attached log file, and give me some suggestions!</div>
<div> </div>
<div>Thanks in advance!</div>
<div> </div>
<div>Jacky Lee<br><br> </div>
<div><span class="gmail_quote">2007/10/22, Paul Wouters <<a href="mailto:paul@xelerance.com">paul@xelerance.com</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On Sat, 13 Oct 2007, ??? wrote:<br><br>> the attached log files are x86/ARM result<br>> the arm version still can't ping????
<br><br>I looked at the log files. A few things I see:<br><br>"management": prepare-client command exited with status 3<br><br>Which looks like a busybox ip/route command that does not support<br>what we need. Install a proper iproute2 package.
<br><br>Next, I see:<br><br>arm_ipsec_nat_out.txt:pluto[273]: NAT-Traversal: ESPINUDP(2) not supported by ke<br>rnel for family IPv4<br>arm_ipsec_nat_out.txt:pluto[273]: NAT-Traversal port floating turned off<br>arm_ipsec_nat_out.txt:pluto[273]: NAT-Traversal is turned OFF due to lack of KER
<br>NEL support: 0/0<br><br>So one end does not support NAT-T. Which means you applied the KLIPS patch, but<br>not the NAT-T patch.<br><br>Paul<br>--<br>Building and integrating Virtual Private Networks with Openswan:<br>
<a href="http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155">http://www.amazon.com/gp/product/1904811256/104-3099591-2946327?n=283155</a><br></blockquote></div><br>