From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] mesh losing internal Ilayer3 connectivity
Date: Mon, 02 May 2016 16:54:56 +0200 [thread overview]
Message-ID: <2079546.oo0Mk8DjMd@bentobox> (raw)
In-Reply-To: <1462190269.1971.52.camel@biplane.com.au>
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
On Monday 02 May 2016 21:57:49 Karl Auer wrote:
> My apologies up front for a newbie question in this apparently very
> technical list. If there is a more appropriate list or forum please
> direct me to it.
>
> I'm running batman-adv (Chaos Calmer, r47065) on OpenWRT on the GL
> -AR150 platform.
Are you using v2016.1 or some older version of batman-adv? If you use
something like v2014.4.
What kind of layer 3 are you using? IPv4/IPv6/...? What is you current
configuration (for example are you have enabled DAT, BLA, ...). Did you check
what exactly goes over the air and what the device (the adhoc one)
receives/sends? What is what the data sent/received over the batman-adv
devices?
Did you hardcode the mac address of the batman-adv device or are you let it
change to a random value on each device creation? Is the device part of a
bridge or is the IP configured directly on the batman-adv device?
Are you sure that the conntrack for the masquerade over the mesh isn't broken?
Why are you masquerade over the mesh anyway?
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-05-02 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 11:57 [B.A.T.M.A.N.] mesh losing internal Ilayer3 connectivity Karl Auer
2016-05-02 14:54 ` Sven Eckelmann [this message]
2016-05-19 14:22 ` Nick Schaf
2016-05-20 7:23 ` Sven Eckelmann
2016-05-20 7:33 ` Antonio Quartulli
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=2079546.oo0Mk8DjMd@bentobox \
--to=sven@narfation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox