From: Peter Bieringer <pb@bieringer.de>
To: usagi-users@linux-ipv6.org
Cc: yasuyuki.kozakai@toshiba.co.jp, netdev@oss.sgi.com,
laforge@gnumonks.org, kaber@trash.net,
netfilter-devel@lists.netfilter.org
Subject: Re: (usagi-users 03187) Re: netfilter6: ICMPv6 type 143 doesn't match
Date: Sun, 09 Jan 2005 18:41:38 +0100 [thread overview]
Message-ID: <097631C1DDA76BD36ECBEFFD@gate.muc.bieringer.de> (raw)
In-Reply-To: <EA4274721EC980393BB13B5E@worker.muc.bieringer.de>
--On Saturday, January 08, 2005 12:45:14 PM +0100 Peter Bieringer
<pb@bieringer.de> wrote:
> 12:40:48.484375 fe80::****:**** > ff02::1: HBH (rtalert: 0x0000)
> (padn)[icmp6 sum ok] icmp6: multicast listener query max resp delay: 2000
> addr: :: [hlim 1] (len 36)
> 0x0000: 6000 0000 0024 0001 fe80 0000 0000 0000 `....$..........
> 0x0010: 0000 0000 **** **** ff02 0000 0000 0000 ................
> 0x0020: 0000 0000 0000 0001 3a00 0502 0000 0100 ........:.......
> 0x0030: 8200 a03a 07d0 0000 0000 0000 0000 0000 ...:............
> 0x0040: 0000 0000 0000 0000 027d 0000 .........}..
> 12:42:42.046741 fe80::200:**ff:fe**:**** > ff02::16: HBH (rtalert: 0x0000)
> (padn)[icmp6 sum ok] icmp6: type-#143 [hlim 1] (len 56)
> 0x0000: 6000 0000 0038 0001 fe80 0000 0000 0000 `....8..........
> 0x0010: 0200 **ff fe** **** ff02 0000 0000 0000 .....*..........
> 0x0020: 0000 0000 0000 0016 3a00 0502 0000 0100 ........:.......
> 0x0030: 8f00 a1d9 0000 0002 0300 0000 ff02 0000 ................
> 0x0040: 0000 0000 0000 0000 0001 0002 0300 0000 ................
> 0x0050: ff05 0000 0000 0000 0000 0000 0001 0003 ................
> I would be glad, if someone can more dig into and provide me patches for
> kernel and probably also for tcpdump.
I mentioned "tcpdump" here also because I played with tcpdump filters
around and found that while tcpdump displays "icmp6" packet, the filter
"icmp6" won't work at all, only the "ip6" filter matches.
Understandable, because the next protocol is "00" (hop-by-hop), but I don't
know whether this is well enough. My opinion is that tcpdump should be
improved to be more smarter (if possible).
Peter
--
Dr. Peter Bieringer http://www.bieringer.de/pb/
GPG/PGP Key 0x958F422D mailto: pb at bieringer dot de
Deep Space 6 Co-Founder and Core Member http://www.deepspace6.net/
next prev parent reply other threads:[~2005-01-09 17:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-25 17:47 netfilter6: ICMPv6 type 143 doesn't match Peter Bieringer
2004-12-27 4:17 ` Yasuyuki Kozakai
2004-12-27 9:02 ` YOSHIFUJI Hideaki / 吉藤英明
2005-01-02 9:12 ` netfilter6: ICMPv6 type 143 doesn't match (130 also not) Peter Bieringer
2005-01-08 11:45 ` (usagi-users 03180) Re: netfilter6: ICMPv6 type 143 doesn't match Peter Bieringer
2005-01-09 17:41 ` Peter Bieringer [this message]
2005-01-10 13:17 ` Olaf Kirch
2005-01-11 19:56 ` (usagi-users 03190) " Peter Bieringer
2005-05-05 19:53 ` Patrick McHardy
2005-05-05 20:20 ` Patrick McHardy
2005-05-05 21:34 ` David S. Miller
2005-05-05 22:26 ` David Stevens
2005-05-05 22:32 ` Patrick McHardy
2005-05-05 22:31 ` David S. Miller
2005-05-05 22:50 ` Patrick McHardy
2005-05-06 13:22 ` Herbert Xu
2005-05-06 14:39 ` Patrick McHardy
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=097631C1DDA76BD36ECBEFFD@gate.muc.bieringer.de \
--to=pb@bieringer.de \
--cc=kaber@trash.net \
--cc=laforge@gnumonks.org \
--cc=netdev@oss.sgi.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=usagi-users@linux-ipv6.org \
--cc=yasuyuki.kozakai@toshiba.co.jp \
/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;
as well as URLs for NNTP newsgroup(s).