From: Stephan Gatzka <stephan.gatzka@gmail.com>
To: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Cc: netdev@vger.kernel.org, linux1394-devel@lists.sourceforge.net,
davem@davemloft.net, stefanr@s5r6.in-berlin.de
Subject: Re: [net-next (TAKE 2) 0/4] IPv6 over Firewire
Date: Sun, 10 Feb 2013 13:48:20 +0100 [thread overview]
Message-ID: <51179714.6010706@gmail.com> (raw)
In-Reply-To: <51177B15.3030405@linux-ipv6.org>
> I have tested against MacOS X 10.5.8.
>
> ARP and ping works but unfortunately NDP does not seem to work.
>
> If I assign static NDP entry on Linux, ping6 ff02::1%fw0 from MacOS
> works well.
>
> I checked tcpdump on both side, and I guess this is because MacOS is
> broken; - tcpdump on Linux side complains that ICMP checksum is
> incorrect. - tcpdump on MacOS side says that length of Link-layer
> address option is 2 (16) instead of 3 (24).
Than I would assume that there is a bug in your new implementation.
RFC3146 section 8 states that the link layer option is of length 3. In
addition, my proof of concept implementation also worked with MacOS X
and I double checked the ndisc packets directly on the firewire line
using a firewire sniffing device (firespy).
Regards,
Stephan
next prev parent reply other threads:[~2013-02-10 12:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-10 9:02 [net-next (TAKE 2) 0/4] IPv6 over Firewire YOSHIFUJI Hideaki
2013-02-10 10:29 ` Stephan Gatzka
2013-02-10 10:48 ` YOSHIFUJI Hideaki
2013-02-10 12:48 ` Stephan Gatzka [this message]
2013-02-10 15:05 ` YOSHIFUJI Hideaki
2013-02-11 10:32 ` Stephan Gatzka
2013-02-11 13:13 ` YOSHIFUJI Hideaki
2013-02-12 19:46 ` Stephan Gatzka
2013-03-01 10:28 ` Stephan Gatzka
2013-03-01 19:44 ` Stephan Gatzka
2013-03-10 10:03 ` Stephan Gatzka
2013-02-13 12:45 ` Stephan Gatzka
2013-02-13 17:08 ` YOSHIFUJI Hideaki
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=51179714.6010706@gmail.com \
--to=stephan.gatzka@gmail.com \
--cc=davem@davemloft.net \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
--cc=yoshfuji@linux-ipv6.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.