From: Pawel Zawora <pzawora@interia.pl>
To: netfilter <netfilter@lists.netfilter.org>
Subject: IPSEC ping
Date: Thu, 24 Aug 2006 13:18:39 +0200 [thread overview]
Message-ID: <44ED8B0F.2070009@interia.pl> (raw)
Hello,
I ve a vpn tunnel (native 2.6, openswan)
I have the ipsec tunnel:
host_A [IP_A]<-->[router IP_router]-----------host_B [IP_B] host_C [ip_C]
left IP_A
right IP_B
rightsubnet IP_C
On host A:
ip xfrm policy show
src IP_A/32 dst IP_C/32
dir out priority 2080
tmpl src IP_A dst IP_C
proto esp reqid 16385 mode tunnel
openswans add routing
IP_C via IP_router dev eth1
tested with
iptables -A FORWARD/INPUT -s IP_C -j ACCEPT
iptables -A FORWAD/INPUT -d IP_C -j ACCEPT
and without any rules.
On host A:
ping -I IP_A IP_C give me no repspose...
When I try to use tcpdump I discover strange information
tcpdump -i eth1 -n src or dst IP_C
IP IP_C> IP_A: ICMP echo reply,
IP IP_C > IP_A: ICMP echo reply,
....
I cant see echo request!
but.......
tcpdump -i eth1 -n src or dst IP_B
IP IP_A > IP_B: ESP(spi....
IP IP_B > IP_A: ESP(spi....
IP IP_A > IP_B: ESP(spi....
IP IP_B > IP_A: ESP(spi....
.....
What is wrong?
What ping cannot see ICMP reply?
Why tcpdump do not show me ICMP request?
Thanks for any help
Pawel
----------------------------------------------------------------------
Zostan Chlopakiem Lata! >>> http://link.interia.pl/f1998
reply other threads:[~2006-08-24 11:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44ED8B0F.2070009@interia.pl \
--to=pzawora@interia.pl \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox