From: "Niccolò Belli" <darkbasic-DEeHIYRtcplPMsqi6aon0Q@public.gmane.org>
To: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: users-3+4lAyCyj6DkhV4RL1hkzWD2FQJk+8+b@public.gmane.org
Subject: Re: Strange issue with IPv6 through ipsec
Date: Fri, 02 Mar 2012 14:19:08 +0100 [thread overview]
Message-ID: <4F50C8CC.2040106@linuxsystems.it> (raw)
In-Reply-To: <4F4EBCE3.8040301-DEeHIYRtcplPMsqi6aon0Q@public.gmane.org>
Sorry for the dumb question, it isn't a bug and I found the answer using
dcpdump:
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
14:09:40.891358 IP6 a:b:c:301::1 > ff02::1:ff00:2: ICMP6, neighbor
solicitation, who has a:b:c:301::2, length 32
14:09:40.891708 IP6 a:b:c:301::2 > a:b:c:301::1: ICMP6, neighbor
advertisement, tgt is a:b:c:301::2, length 32
14:09:40.891727 IP6 a:b:c:301::1 > a:b:c:301::2: ICMP6, echo request,
seq 1, length 64
14:09:40.891778 IP6 a:b:c:301::2 > a:b:c:301::1: ICMP6, echo reply, seq
1, length 64
14:09:41.887406 IP6 a:b:c:301::1 > a:b:c:301::2: ICMP6, echo request,
seq 2, length 64
14:09:41.887478 IP6 a:b:c:301::2 > a:b:c:301::1: ICMP6, echo reply, seq
2, length 64
14:09:42.887391 IP6 a:b:c:301::1 > a:b:c:301::2: ICMP6, echo request,
seq 3, length 64
14:09:42.887440 IP6 a:b:c:301::2 > a:b:c:301::1: ICMP6, echo reply, seq
3, length 64
14:09:43.886647 IP6 a:b:c:301::1 > a:b:c:301::2: ICMP6, echo request,
seq 4, length 64
14:09:43.886716 IP6 a:b:c:301::2 > a:b:c:301::1: ICMP6, echo reply, seq
4, length 64
14:09:44.886636 IP6 a:b:c:301::1 > a:b:c:301::2: ICMP6, echo request,
seq 5, length 64
14:09:44.886687 IP6 a:b:c:301::2 > a:b:c:301::1: ICMP6, echo reply, seq
5, length 64
14:09:45.886651 IP6 a:b:c:301::1 > a:b:c:301::2: ICMP6, echo request,
seq 6, length 64
14:09:45.886722 IP6 a:b:c:301::2 > a:b:c:301::1: ICMP6, echo reply, seq
6, length 64
14:09:45.889830 IP6 fe80::211:d8ff:fed9:c01a > a:b:c:301::1: ICMP6,
neighbor solicitation, who has a:b:c:301::1, length 32
14:09:45.889866 IP6 a:b:c:301::1 > fe80::211:d8ff:fed9:c01a: ICMP6,
neighbor advertisement, tgt is a:b:c:301::1, length 24
I simply had to passthrough multicast link-local traffic.
I'm sorry but I'm really newbie to IPv6 :(
Regards,
Niccolò
prev parent reply other threads:[~2012-03-02 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 23:43 Strange issue with IPv6 through ipsec Niccolò Belli
[not found] ` <4F4EB820.1090607-DEeHIYRtcplPMsqi6aon0Q@public.gmane.org>
2012-03-01 0:03 ` Niccolò Belli
[not found] ` <4F4EBCE3.8040301-DEeHIYRtcplPMsqi6aon0Q@public.gmane.org>
2012-03-02 13:19 ` Niccolò Belli [this message]
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=4F50C8CC.2040106@linuxsystems.it \
--to=darkbasic-deehiyrtcplpmsqi6aon0q@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=users-3+4lAyCyj6DkhV4RL1hkzWD2FQJk+8+b@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.