From: Stephan Gatzka <stephan.gatzka@gmail.com>
To: stephan.gatzka@gmail.com
Cc: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>,
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: Fri, 01 Mar 2013 20:44:07 +0100 [thread overview]
Message-ID: <51310507.7030904@gmail.com> (raw)
In-Reply-To: <511A9BFC.9010907@gmail.com>
Hi Yoshfuji,
> Nevertheless, there is some hope that I can try out your patch set
> during this week and find some insight why IPv6 does not work with
MacOS X.
Unfortunately, until now I did not find some time to try out your IPv6
over firewire implementation. But now I did.
I just fired a ping6 from my Linux box running your kernel.
Using a FireSpy device I sniffed directly on the firewire line and
dumped the ndisc packets. They look pretty well, I can't see any
problems. The only thing I can't really judge about is the ICMPv6
checksum. But wireshark says the checksum is correct.
The packets send from MacOS X also look good, but yes, their
(recalculated) checksum might be wrong. The wireshark running on my
receiving linux box does not agree with the checksum send by MacOS X.
Now I would also assume that MacOS X is wrong. To proof that you can
test your code against MacOS X with CHECKSUM_UNNECESSARY. I would assume
that your implementation will work then. Unfortunately I no longer have
the MacOS laptop available.
Regards,
Stephan
next prev parent reply other threads:[~2013-03-01 19:44 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
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 [this message]
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=51310507.7030904@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 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).