<DIV>Firstly, Thanks for your reply.</DIV><PRE>"Paul Wouters" paul@xelerance.com> ：
>On Fri, 21 Aug 2009, weiruyao wrote:
>
>> >This is a networking issue, not an openswan issue? Without openswan
>> >running on either end, can you ping 192.168.1.104? if that works, can
>> >you do "ipsec ikeping 192.168.1.104" ?
>> >
>> Withour openswan running on either end ,I can ping 192.168.1.104,but can't ipsec ikeping 192.168.1.104:
>> / $ ipsec ikeping 192.168.1.104
>> Sending packet to 192.168.1.104/500
>> 1 packets sent, 0 packets received. 100% packet loss
>> Only after I start openswan in both end ,ipsec ikeping 192.168.1.104 success:
>> / $ ipsec ikeping 192.168.1.104
>> v4 bind: Address already in use
>> Is it normall??
>
>You would need to run openswan on one end, and stop it on the end you are
>trying ipsec ikeping from.
yes,it is.I run openswan on 192.168.1.104,and I can ping 192.168.1.104,but can't ipsec ikeping 192.168.1.104:
/ $ ipsec ikeping 192.168.1.104
Sending packet to 192.168.1.104/500
1 packets sent, 0 packets received. 100% packet loss
Only after I start openswan in both end ,ipsec ikeping 192.168.1.104 success:</PRE><PRE>/ $ ipsec ikeping 192.168.1.104
v4 bind: Address already in use
>Once our GSoC livetest code has been merged into openswan, this is all
>automated for you and you should be able to use "ipsec livetest" to test
>your local network/firewall/mtu settings.
></PRE><PRE>I'll try tomorrow.
Paul,Thanks you again.</PRE><br><br><span title="neteasefooter"/><hr/>
<a href="http://www.yeah.net/?from=footer">没有广告的终身免费邮箱,www.yeah.net</a>
</span>