<div>The attached file is ipsec log without klipsdebug and plutodebug. It can work when I ping <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://10.2.111.2/" target="_blank">10.2.111.2</a>, an ipsec server ip.
<br>The interesting thing is If I turn on klipsdebug and plutodebug, it seems it cannot work because I see no any log as follows: <br>"84 bytes from <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://10.2.111.2/" target="_blank">
10.2.111.2</a>: icmp_seq=0 ttl=253 time=50.0 ms"<br>Why?</div>
<div> </div>
<div>Thanks!<br><br><br> </div>
<div><span class="gmail_quote">2007/11/1, 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 Thu, 1 Nov 2007, ??? wrote:<br><br>> I have installed iproute2 package in my kernel, but the execute result is
<br>> still the same as before.<br><br>So do you no longer have "client route" errors in the logs? You only<br>provided the kernel logs, not the userland logs. Can you show a<br>successful IPsec SA established with plutodebug= and klipsdebug=
<br>disabled?<br><br>> The ping has something wrong. Please reference the<br>> attached log file, and give me some suggestions!<br><br>I don't see anything that looks wrong, but I hardly ever need to look<br>at kernel debugs, since most problems are userland problems.
<br><br>Paul<br></blockquote></div><br>