From: Simon Wunderlich <sw@simonwunderlich.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] how to make IP layer handle the change of network topology
Date: Thu, 7 Aug 2014 10:32:05 +0200 [thread overview]
Message-ID: <201408071032.05730.sw@simonwunderlich.de> (raw)
In-Reply-To: <201408071029.36757.sw@simonwunderlich.de>
Bah, i hit the wrong button before finishing the mail :)
> Hi liu,
>
> > Hello, eveyone, I am learning the batman.adv recently.
> >
> > We know that batman.adv works on layer 2. When the network topology
> > change, batman.adv can know this change and handle it. But the IP layer
> > doesn't know that. How to make IP layer handle the change of network
> > topology?
>
> The IP layer does not need to know - to the upper layers, a batman-adv
> network appears to be a network where all nodes are just one hop away -
> although they might be more far away in practice. So if you insert an IP
> packet, it will get transported automatically to the right destination
> (provided batman-adv knows where that is), even over multiple hops.
>
> > For example, I have 3 mesh nodes, client node A, gateway node B and
> > geteway node C. A connects to internet via B. Then I shutdown B. I
> > guess A will switch to C as it's gateway node automatically. But it's
> > not so. A continuously send the ARP request packet to search the MAC
> > address of B. The default gateway is still B, not C.
>
> This will only work if the gateways IP stays the same. This could work like
> that:
> * connect B and C to the same LAN, and enable bridge loop avoidance in
> batman-adv
> * This LAN should have only one router to the internet (e.g. your ADSL
> modem).
> * bridge the batman-interface bat0 and you Ethernet interface eth0 using a
> linux bridge device
Please see our quick start guide for more information on the topic:
http://www.open-mesh.org/projects/batman-adv/wiki/Quick-start-guide#Mixing-
non-BATMAN-systems-with-batman-adv
>
> > So, how should I do to make the IP layer be aware of that the gateway has
> > swithed to another one?
By using bridges, you always send to the same gateway in your LAN, which does
not change IP or MAC addresses - so your clients don't need to be aware of the
topology change.
Cheers,
Simon
next prev parent reply other threads:[~2014-08-07 8:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 7:49 [B.A.T.M.A.N.] how to make IP layer handle the change of network topology liudows
2014-08-07 8:24 ` Antonio Quartulli
2014-08-07 8:57 ` Antonio Quartulli
2014-08-07 8:29 ` Simon Wunderlich
2014-08-07 8:32 ` Simon Wunderlich [this message]
2014-08-08 11:10 ` liu
2014-08-08 12:20 ` Simon Wunderlich
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=201408071032.05730.sw@simonwunderlich.de \
--to=sw@simonwunderlich.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 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.