public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: liu <liudows@aliyun.com>
Cc: 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: Fri, 8 Aug 2014 14:20:28 +0200	[thread overview]
Message-ID: <201408081420.28413.sw@simonwunderlich.de> (raw)
In-Reply-To: <53E4B02F.2040506@aliyun.com>

Hello Liu,

> Thanks for reply. I have tried to fix this problem followed by Simon's
> guide.  Unfortunately It stil doesn't work.I draw a pciture named
> 'topo.jpg' in the  attachment to describe my situation.
> 
> Gateway B and C are wired to router 192.168.1.1 through their 'WAN'
> interface. They are in the same LAN. 'bat0' and 'eth0' are bridged by
> 'br-lan' interface, and are assigned a mesh subnet IP address '10.130.1.x'.
> 
> Client A connected to B and C by mesh network. 'bat0' and 'wan' is
> bridged by 'br-wan' in Client A. 'br-wan' is assigned a subnet IP
> address by DHCP server in B or C, for example '10.130.1.138'.

You are still doing routing in that scenario. Instead, you should bridge all 
nodes in the same network, and they should be in the same IP subnet. If you 
configure another WAN, you are back to routing, which will not work for that 
scenario.

Please configure eth0, wan and bat0 in the same bridge (e.g. br-lan) on all 
devices. Don't configure other bridges. Then, your devices and your client 
should get an IP address from the 192.168.1.x subnet, and should be able to 
ping 192.168.1.1, even if node A fails.

Cheers,
     Simon

      reply	other threads:[~2014-08-08 12:20 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
2014-08-08 11:10     ` liu
2014-08-08 12:20       ` Simon Wunderlich [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=201408081420.28413.sw@simonwunderlich.de \
    --to=sw@simonwunderlich.de \
    --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