From: "Nicolás Echániz" <nicoechaniz@codigosur.org>
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.] routing loops on interconnected routers / adhoc + ethernet
Date: Sat, 03 Mar 2012 07:14:35 -0300 [thread overview]
Message-ID: <4F51EF0B.5070501@codigosur.org> (raw)
In-Reply-To: <201203031643.12912.lindner_marek@yahoo.de>
On 03/03/2012 05:43 AM, Marek Lindner wrote:
> On Saturday, March 03, 2012 16:16:15 Nicolás Echániz wrote:
>> Maerk thanks for your fast reply. In fact, that's how we started, that's
>> what I meant by:
>>
>> "We have also tried adding eth0 to bat0 and take it out of br-lan, which
>> also "works" but gives routing loops from time to time."
>>
>> but my english sometimes fails me :)
>
> Your English is quite good. To be honest I lost the overview about what
> interface is added where and what is connected how. Some people might be able
> to simply look at the uci config to understand the setup but I am not one of
> those. :-)
>
> Let me write down what I understood - feel free to correct me.
>
> some nodes -- node1 -- adhoc[wlan0-1] + ethernet[eth0] -- node2 -- more nodes
>
> Each node also has wlan0 for non-mesh clients but this is of no relevance at
> this point. What is eth1 for ?
in the node marisa-mr, eth1 is the WAN port of the router, that is not
being used as wan but just as a non-batman ethernet interface to connect
to a router inside the house.
> You are saying that from time to time the packets loop between node1 and node2
> using adhoc & ethernet to fly forth and back ?
exactly so.
>> Is this a known issue or should this not happen in a setup where both
>> interfaces are added to batman?
>
> You should not have loops either way but it is easy to build loops in
> complicated setups. At first we should understand your setup and
> configuration. Drawing a little picture that shows what interface is connected
> to what other interface also can help.
alright, I'll try some ascii art, but I'm afraid you'll find out my
english is better :P
(non-batman)
wlan0
|
------
| czuk |
------
/wlan1
/
/
/
/ 1500m
/
/
/
wlan1
---------- /
| cisterna |
---------- (batman enabled
| cabled clients)
wlan0 |
/ \ eth0
/ \ |
/ \ -------
/ \ | nogal |
/ 350m \ 600m / -------
/ \ --------wlan0
/ \ /
/ \ /
wlan0--------------wlan0-1
/ \
------------ ------------
| marisa-mr | 0m | marisa-blt |
------------ ------------ \
| \eth0__________________eth0/ wlan0
eth1 (non-batman)
(non-batman)
|
|
|
[in-house router]
where not indicated otherwise, links are between interfaces added to batman.
I hope it's understandable!
... at the moment I've disabled marisa-mr_wlan0 and everything works fine.
The routing loop problem appears when marisa-mr_wlan0 is enabled, as
shown in the drawing.
The setup makes more sense when you add the antennae information.
marisa-blt has a panel/sector antena, but marisa-mr has a 24dbi grid
pointed at cisterna, which in turn has another grid pointed back (on
wlan0) and a second grid (on wlan1) points at czuk on the opposite side,
where a grid points back.
I've drawn the "desired" links; the wireless portion is ad-hoc, so there
are many more links present between the nodes, in fact cisterna, czuk
and both marisa's can all "see" each other.
cisterna_wlan1 has a reasonable link through the back lobe of the grid
antenna to both marisa-blt_wlan0-1 and marisa-mr_wlan0.
If you'd like me to send any more information just ask please; and if
you get bored, I'll understand!!
--
NicoEchániz
next prev parent reply other threads:[~2012-03-03 10:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 7:39 [B.A.T.M.A.N.] routing loops on interconnected routers / adhoc + ethernet Nicolás Echániz
2012-03-03 7:53 ` Marek Lindner
2012-03-03 8:16 ` Nicolás Echániz
2012-03-03 8:43 ` Marek Lindner
2012-03-03 10:14 ` Nicolás Echániz [this message]
2012-03-03 10:24 ` Nicolás Echániz
2012-03-03 11:32 ` Marek Lindner
2012-03-04 2:30 ` Nicolás Echániz
2012-03-04 8:13 ` Marek Lindner
2012-03-04 9:32 ` Nicolás Echániz
2012-03-04 10:52 ` Marek Lindner
2012-03-18 6:31 ` Nicolás Echániz
2012-03-20 12:51 ` Marek Lindner
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=4F51EF0B.5070501@codigosur.org \
--to=nicoechaniz@codigosur.org \
--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.