public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Antonio Quartulli <antonio@meshcoding.com>
To: b.a.t.m.a.n@lists.open-mesh.org, liudows@aliyun.com
Subject: Re: [B.A.T.M.A.N.] how to make IP layer handle the change of network topology
Date: Thu, 07 Aug 2014 10:24:03 +0200	[thread overview]
Message-ID: <53E337A3.3060801@meshcoding.com> (raw)
In-Reply-To: <53E32F6D.3010207@aliyun.com>

[-- Attachment #1: Type: text/plain, Size: 1532 bytes --]

Hi Lui,

there is no direct way to get a topology change in userspace unless you
want to parse the originator table (and even in that case you will only
see "local" changes).

The behaviour you described about the ARP packets is normal because the
IP layer does not know anything about changes happening at the
batman-adv layer. You need to handle them by yourself (if possible).

However it looks like you want to detect a "gateway change" rather than
a real "topology change".

Please check this link[1] out that is explaining how batman-adv tells
userspace about GW changes.

Cheers,


[1] http://www.open-mesh.org/projects/batman-adv/wiki/Uevent#Gateway-uevents

On 07/08/14 09:49, liudows wrote:
> 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?  
> 
> 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.  
> 
> So, how should I do to make the IP layer be aware of that the gateway has swithed to another one?  
> 
> Thanks! Best regards.  
> 
> liu  
> 

-- 
Antonio Quartulli


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]

  reply	other threads:[~2014-08-07  8:24 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 [this message]
2014-08-07  8:57   ` Antonio Quartulli
2014-08-07  8:29 ` Simon Wunderlich
2014-08-07  8:32   ` Simon Wunderlich
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=53E337A3.3060801@meshcoding.com \
    --to=antonio@meshcoding.com \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=liudows@aliyun.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