public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: johnzeng <johnzeng2013@yahoo.com>
To: "Linus Lüssing" <linus.luessing@c0d3.blue>
Cc: 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.] i have a question ? How many relay nodes can be supported at NetworkCoding ( mtu 1546 ) .
Date: Wed, 09 Nov 2016 13:59:29 +0800	[thread overview]
Message-ID: <5822BB41.7060305@yahoo.com> (raw)
In-Reply-To: <20161109052815.GG3391@otheros>


Hello Dear Linus:

                            Ok , i see , i will test it in according to 
your advisement .


                            Thanks , have a good day with you


                            Tiger



于 2016年11月09日 13:28, Linus Lüssing 写道:
> On Wed, Nov 09, 2016 at 04:50:45AM +0100, johnzeng via B.A.T.M.A.N wrote:
>> Date: Wed, 09 Nov 2016 11:50:30 +0800
>> From: johnzeng <johnzeng2013@yahoo.com>
>> To: Simon Wunderlich <sw@simonwunderlich.de>
>> CC: b.a.t.m.a.n@lists.open-mesh.org, Sven Eckelmann <sven@narfation.org>,
>>   Martin Hundebøll <martin@hundeboll.net>
>> Subject: Re: [B.A.T.M.A.N.] i have a question ? How many relay nodes can be
>>   supported at NetworkCoding ( mtu 1546 ) .
>>
>>                               I can understand network coding , it will be
>> same as proxy or Intermediator at Layer 2 ,
> Maybe there is a complete misunderstanding what "network coding"
> is?
>
> Maybe an easier expression would be "packet mixing" or "magic packet
> mangling" [1].
>
> Any code that does something with networking is usually *not*
> "network coding" (at least in this context here).
>
> Have a look at the links Sven has provided earlier.
>
>>
>>                              Your meaning :  Batman-adv can build Similar
>> mechanism ( Intermediator )  via intermediator , it wil be  relay based real
>> application packet ( not relay based Broadcast packet)
> Just try it :-). Compile batman-adv *without network coding* with
> your A-B-C scenario and see how it magically works, too :-).
>
> Regards, Linus
>
>
> [1]: Please no expert hit me :D. I know, ultimately, network coding would
> replace packet based networks, if I remember Frank's talk
> in Leipzig correctly
>
> https://www.youtube.com/watch?v=yluj7e_rfVE


      reply	other threads:[~2016-11-09  5:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-04 12:30 i have a question ? How many relay nodes can be supported at NetworkCoding ( mtu 1546 ) johnzeng
2016-11-04 13:33 ` johnzeng
2016-11-05 14:28 ` [B.A.T.M.A.N.] " Sven Eckelmann
2016-11-07  7:37   ` Martin Hundebøll
2016-11-08 10:54   ` johnzeng
     [not found]   ` <mailman.63.1478602511.678.b.a.t.m.a.n@lists.open-mesh.org>
2016-11-08 19:14     ` [B.A.T.M.A.N.] " Simon Wunderlich
2016-11-09  3:50       ` johnzeng
2016-11-09  3:56         ` johnzeng
     [not found]         ` <mailman.87.1478663809.678.b.a.t.m.a.n@lists.open-mesh.org>
2016-11-09  5:33           ` Linus Lüssing
     [not found]       ` <mailman.86.1478663442.678.b.a.t.m.a.n@lists.open-mesh.org>
2016-11-09  5:28         ` Linus Lüssing
2016-11-09  5:59           ` johnzeng [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=5822BB41.7060305@yahoo.com \
    --to=johnzeng2013@yahoo.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=linus.luessing@c0d3.blue \
    /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