public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: "Martin Hundebøll" <martin@hundeboll.net>
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.] Network Coding testing.
Date: Sun, 15 Sep 2013 22:49:00 +0200	[thread overview]
Message-ID: <52361D3C.9080100@hundeboll.net> (raw)
In-Reply-To: <CAHQ_bghKkrNisgdgTQk2+MScz0BwAF2ESBKLjn90AHACdMKJ2g@mail.gmail.com>

Hi Ajeet,

On 2013-09-12 15:36, ajeet singh wrote:
> I am trying to test network coding functionality of batman-adv. I am
> facing some problems.
>
> Please find my topology information,
>
> I created network with three nodes ( ad-hoc),
>
> Node A --- Node B --- Node C
>
> I did following settings,
>
> --- Complied latest batman-adv. with NC enabled.
> --- I did all setting form
> http://www.open-mesh.org/projects/batman-adv/wiki/NetworkCoding
> --- Kept all nodes in promiscuous mode. (Nodes are working properly in
> this mode).
>
> When I started iperf (TCP) from node A to node C, Node B stopped
> responding after few seconds. B is not sending OGM to A and C.
>
> When I tested without NC everything work fine.
>
> Is there any additional settings required for NC test?

As we figured out on IRC, the problems were caused by the ath9k_htc 
chip/driver, which does not handle packet sizes larger than 1500 bytes 
that well. So changing the MTU of your bat0 interface to something like 
1480 solved the problem.

It is a bit weird though, cause my personal experience says that 
ath9k_htc can handle packets up to 1550 bytes, which batman-adv+NC 
shouldn't exceed. Maybe a quick inspection with tcpdump/wireshark can 
give us some numbers?

// Martin

-- 
Kind Regards
Martin Hundebøll
Frederiks Allé 99, 1.th
8000 Aarhus C
Denmark

+45 61 65 54 61
martin@hundeboll.net

      reply	other threads:[~2013-09-15 20:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-12 13:36 [B.A.T.M.A.N.] Network Coding testing ajeet singh
2013-09-15 20:49 ` Martin Hundebøll [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=52361D3C.9080100@hundeboll.net \
    --to=martin@hundeboll.net \
    --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