From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: dbeberman@aicas.com
Subject: Re: [B.A.T.M.A.N.] batman-adv bug 149: odd broadcast behavior -- generated CRC errors
Date: Fri, 20 May 2011 10:37:52 +0200 [thread overview]
Message-ID: <201105201037.53737.sven@narfation.org> (raw)
In-Reply-To: <201105200955.27323.sven@narfation.org>
[-- Attachment #1: Type: Text/Plain, Size: 1342 bytes --]
Sven Eckelmann wrote:
> Hi,
>
> I would assume that you don't monitor the bug as you didn't answer the
> questions on irc. So here the part of the IRC communication which needs
> comments/answers from your side.
[...]
Just talked to Marek and we both are a little bit irritated by following part
of your first "mail":
> > Further, if the UDP packet is large enough to fragment into 2 packets, a
> > total of 6 packets are broacast, with only the very last packet being
> > broadcast without error.
We don't know what fragmentation you are talking here. batman-adv doesn't
fragment the broadcast packet, wifi shall not fragment the broadcast packet:
"only mpdus with a unicast receiver address shall be fragmented.
broadcast/multicast frames shall not be fragmented even if their length
exceeds dot11FragmentationThreshold" - ieee802.11-2007 page 255
So the only fragmentation seems to be the IP(v6) fragmentation - and this
would mean that batman-adv only sees two independent packets which it
rebroadcasts complete independent - therefore it doesn't make any sense that
only the last of 6 packets isn't destroyed by the resend mechanism.
Could you please exactly tell us on which layer and which situation you
experienced what behaviour and how you did your measurements.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2011-05-20 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 7:55 [B.A.T.M.A.N.] batman-adv bug 149: odd broadcast behavior -- generated CRC errors Sven Eckelmann
2011-05-20 8:37 ` Sven Eckelmann [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=201105201037.53737.sven@narfation.org \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=dbeberman@aicas.com \
/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