public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@web.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.] Multicast video over 2 node mesh
Date: Tue, 29 Jun 2010 01:51:35 +0200	[thread overview]
Message-ID: <20100628235134.GA25514@Sellars> (raw)
In-Reply-To: <AANLkTil7STjuod65b5gzPfIunyr81e0H8Bj0gsAWD-yQ@mail.gmail.com>

Hi Nathan,

On Mon, Jun 28, 2010 at 12:01:35PM -0500, Nathan Wharton wrote:
> On Mon, Jun 28, 2010 at 11:40 AM, Sven Eckelmann <sven.eckelmann@gmx.de> wrote:
> > Nathan Wharton wrote:
> >> I am having problems getting multicast video over my 2 node mesh.  I
> >> am building under openwrt and the version is 0.3.0-alpha rv1715.
> >
> > First thing: multicast is currently implemented over broadcast.
> >
> >> I have a lan bridge on each side.  If I directly add ath0 to the lan
> >> bridge the video works fine.  But since I want to mesh, I put ath0
> >> into bat0 instead, and then I put bat0 into the bridge.  This works
> >> for all my traffic that put across it so far except the multicast
> >> video.  A tcpdump comparison of both sides shows that after about 32
> >> packets data starts getting dropped.  The video is about 1Mbs.
> >
> > Simon changed to broadcast code some time ago. Maybe it is related. Can you
> > please try to use ethernet to transfer the data between the nodes (so bat0
> > should only have the ethernet device included). Just as test if it could be
> > related to midair collisions due to the broadcasts resends or if the broadcast
> > code as a general problem.
> 
> Connecting them via eth0 and putting eth0 in bat0 works fine, even though
> I could not set the mtu of my ethernet device to 1524.  The packets are only
> up to 1400 in size anyway.
Could you maybe compile batman-adv with extra debugging info and
especially have a look in this output for something like "old packet
received, start protection" please? As Sven said before, there've
been some additions in the code lately to prevent
never-ending-broadcast-storms if the air is very "messy" - and one
of them has been the "protected window" in rev. 1631. It would be
great if you could check if the problem was there in 1630 already.

Could you also check, if you might get the next 32 packets again
after 30 seconds?

It would also be interesting if the broadcast-throughput
has anything to do with it. Are you using the VLC player by any
chance? If I remember right, it can downsample the bitrate
on-the-fly.

And for the MTU stuff, you could set it to 1300 with ifconfig/ip
on both the sending and receiving host on the lan segment, just to
make sure (without touching any mtu's on the routers).

Cheers,
Linus

      reply	other threads:[~2010-06-28 23:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-28 16:29 [B.A.T.M.A.N.] Multicast video over 2 node mesh Nathan Wharton
2010-06-28 16:40 ` Sven Eckelmann
2010-06-28 17:01   ` Nathan Wharton
2010-06-28 23:51     ` Linus Lüssing [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=20100628235134.GA25514@Sellars \
    --to=linus.luessing@web.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