From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Layer 2 fragmentation
Date: Fri, 28 May 2010 00:12:40 +0800 [thread overview]
Message-ID: <201005280012.41540.lindner_marek@yahoo.de> (raw)
In-Reply-To: <20100527154236.GA26610@lunn.ch>
On Thursday 27 May 2010 23:42:36 Andrew Lunn wrote:
> We discussed this a while ago. Actually fragmentation should be
> considered the last resort. It if first better to try header
> compression, to make the frame small enough that it can be sent
> without fragmentation. I think you had a quick look at using the PPP
> compression code, but i guess it did not go any further.
>
> We only need to fragment when compression is not possible.
I read about the compression and I still think it is a good idea.
Unfortunately, it requires deep packet inspection and would only work for 99%
of the IPv4 traffic. Besides, both solutions do not exclude each other.
Regards,
Marek
prev parent reply other threads:[~2010-05-27 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 14:23 [B.A.T.M.A.N.] Layer 2 fragmentation Andreas Langer
2010-05-27 15:07 ` Andrew Lunn
2010-05-27 15:30 ` Marek Lindner
2010-05-27 15:42 ` Andrew Lunn
2010-05-27 16:12 ` Marek Lindner [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=201005280012.41540.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@lists.open-mesh.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