From: johnzeng <johnzeng2013@yahoo.com>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: i have a question ? How many relay nodes can be supported at NetworkCoding ( mtu 1546 ) .
Date: Fri, 04 Nov 2016 20:30:02 +0800 [thread overview]
Message-ID: <581C7F4A.80104@yahoo.com> (raw)
Hello Dear Sir :
i read some detail about NetworkCoding , my understanding :
every relay node will detects neighbors packet at promisc mode and
combine these packet into a single transmission ,
and every relay mode will keep some usaful ( Ingoing: c8:3a:35:c9:ce:71
.... ) and they will add some encoded information into packet
( will send destination )
So we will run the part --- ip link set dev wlan0 mtu 1546 ( more than
1532 )
but i have a question ? How many relay nodes can be supported at
NetworkCoding ( mtu 1546 ) .
Thanks
Tiger
batctl nn
Node: c8:3a:35:c9:ce:71
Ingoing: c8:3a:35:c9:ce:71
Outgoing: c8:3a:35:c9:ce:71
[root@alarmpi ~]# batctl nc
enabled
[root@alarmpi ~]# batctl statistics
tx: 18
tx_bytes: 2076
tx_dropped: 32
rx: 767
rx_bytes: 33993
forward: 0
forward_bytes: 0
mgmt_tx: 7956
mgmt_tx_bytes: 542012
mgmt_rx: 3132
mgmt_rx_bytes: 222572
frag_tx: 0
frag_tx_bytes: 0
frag_rx: 0
frag_rx_bytes: 0
frag_fwd: 0
frag_fwd_bytes: 0
tt_request_tx: 0
tt_request_rx: 1
tt_response_tx: 1
tt_response_rx: 0
tt_roam_adv_tx: 0
tt_roam_adv_rx: 0
dat_get_tx: 2
dat_get_rx: 0
dat_put_tx: 0
dat_put_rx: 4
dat_cached_reply_tx: 0
nc_code: 0
nc_code_bytes: 0
nc_recode: 0
nc_recode_bytes: 0
nc_buffer: 17
nc_decode: 0
nc_decode_bytes: 0
nc_decode_failed: 0
nc_sniffed: 0
next reply other threads:[~2016-11-04 12:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 12:30 johnzeng [this message]
2016-11-04 13:33 ` i have a question ? How many relay nodes can be supported at NetworkCoding ( mtu 1546 ) 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
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=581C7F4A.80104@yahoo.com \
--to=johnzeng2013@yahoo.com \
--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 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.