From: Axel Neumann <axel@open-mesh.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] Tunnel problems...
Date: Thu, 18 Oct 2007 13:13:01 +0200 [thread overview]
Message-ID: <200710181313.02144.axel@open-mesh.net> (raw)
In-Reply-To: <000001c81164$7ec1c8d0$4100a8c0@meritechbrett>
Hello,
On Donnerstag 18 Oktober 2007, Brett Maurer wrote:
> I'm having a problem with bat0. It seems to be disconnecting and I cannot
> find the cause. My configuration is as follows:
> Version:
> 0.3 beta rv731
Are you sure the tunnel interface is called bat0. Because in 0.3-beta-rv731 it
should be called gate0. - but in batmand-exp it is called bat0.
> Scenario:
> A-----B-----GW-----PC
> A - is on 104.0.0.3 ath0 with -s 10.0.0.10
> B - is on 104.0.0.2 ath0 with -s 10.0.0.10
> GW - is on 104.0.0.1 ath0 and 10.0.0.1 eth0
>
> PC - is on 10.0.0.10
> I can see A routing through B to GW fine. The tunnel bat0 on A and B seems
> unstable though. I'm looking at VIS packets arriving at PC. It arrives for
> about 30 sec then stops for a while. It is not clear why the tunnel keeps
> disconnecting.
The current client-GW-tunnel implementation is observing the traffic from the
client point of view.
The client suspects a GW as unresponsive (black-hole) if data is send through
the tunnel from the client to the GW but no data is send the other way around
(tunnelled from the GW to the client).
Then the client waits for a while and if still no data arrives through the
tunnel, a timeout hits and automatically disconnects the client from the GW -
hoping that other available GW are more responsive.
This can be observed using debug-leve-3 on the client side.
The problem is that the mechanism assumes a bidirectional communication
between the mesh client node and a distant node behind the GW. Unfortunately,
this is not the case with your scenario when sending vis packets to a
visualization server.
In batmand-exp there is a --no-unresp-gw-check directive which disables this
feature. For node A try:
batmand --no-unresp-gw-check -r 3 -s 10.0.0.10 ath0
ciao
/axel
>
>
>
> If anyone can offer some advice, I'd much appreciate it.
next prev parent reply other threads:[~2007-10-18 11:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 8:54 [B.A.T.M.A.N.] Tunnel problems Brett Maurer
2007-10-18 11:13 ` Axel Neumann [this message]
2007-10-18 14:07 ` Marek Lindner
2007-10-18 14:28 ` a.anselmi
2007-10-18 15:02 ` Marek Lindner
2007-10-18 15:28 ` a.anselmi
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=200710181313.02144.axel@open-mesh.net \
--to=axel@open-mesh.net \
--cc=b.a.t.m.a.n@open-mesh.net \
/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.