public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Predrag Balorda <predrag.balorda@gmail.com>
To: 'The list for a Better Approach To Mobile Ad-hoc Networking'
	<b.a.t.m.a.n@open-mesh.net>
Subject: [B.A.T.M.A.N.] Multiple wireless interfaces
Date: Fri, 18 Jan 2008 14:41:33 -0000	[thread overview]
Message-ID: <000301c859e0$3abb5100$b031f300$@com> (raw)
In-Reply-To: <200801151845.43446.lindner_marek@yahoo.de>

Ok. Here is something batman doesn't provision for - dual-interface setup where
you want to create a duplex link (tx on one and rx on another). Duplex link to
one other node is simple (and has to be done manually), but how would we go
about creating a duplex link to 2 or more nodes? Or one simplex link to
downstream node and one simplex link to upstream node?
Example:

A = B   C duplex link (for example I need to talk from B to A fast and I use
both interfaces to talk to A)
A - B - C simplex links (I use one interface to talk to A and one to talk to B)
A = B/B = C duplex links for all links (I talk to both A and C duplex, but not
at the same time of course)

How do we do this with batman easily and dynamically (without having to manually
mess around with routing tables etc)?


  parent reply	other threads:[~2008-01-18 14:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-15 11:20 [B.A.T.M.A.N.] Basic question Carlo Beccia
2008-01-15 11:43 ` Marek Lindner
2008-01-15 12:59   ` Carlo Beccia
2008-01-15 14:25     ` Simon Wunderlich
2008-01-15 14:41       ` Carlo Beccia
2008-01-15 15:08         ` Simon Wunderlich
2008-01-15 17:45           ` Marek Lindner
2008-01-16 11:38             ` Carlo Beccia
2008-01-18 14:41             ` Predrag Balorda [this message]
2008-01-18 14:46             ` [B.A.T.M.A.N.] RE: Multiple wireless interfaces Predrag Balorda
2008-02-11 10:03             ` Predrag Balorda
2008-02-11 12:00               ` Axel Neumann

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='000301c859e0$3abb5100$b031f300$@com' \
    --to=predrag.balorda@gmail.com \
    --cc=b.a.t.m.a.n@open-mesh.net \
    --cc=pele@balorda.com \
    /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