public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Hans-Werner Hilse <hw@haveyouseenthiscat.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Mesh hickups with 2014.3
Date: Thu, 11 Jun 2015 14:43:36 +0200	[thread overview]
Message-ID: <2dca4d7a596a3a7f250b2ef62cf9c3ec@hilses.de> (raw)
In-Reply-To: <1434025163.1056.73.camel@nord-west.org>

Hi,

Am 2015-06-11 14:19, schrieb Bjoern Franke:

> - gateway gets alfreddata from router

Continuously? So that directions seems fine then.

> - router pingable via batctl
> - ping via linklocal, ULA and public-IPv6 from gateway to router not
> possible

What does "not possible" mean? There's no reply?

> - other routers in the same mesh can ping it via ULA etc (connected via
> the same fastd-VPN)

So it's just the gateway that can't reach the "router"?

> Public-IPv6 is announced from a gateway via radvd into the mesh.

So even in that direction, NDP is fine. Seems only ICMPv6 echo requests 
are somewhat different then?

> Unfortunately we are out of ideas where we can search for the reason.

Look what's actually on the wire on both ends? Tcpdump and batctl 
tcpdump?

-hwh


  reply	other threads:[~2015-06-11 12:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11 12:19 [B.A.T.M.A.N.] Mesh hickups with 2014.3 Bjoern Franke
2015-06-11 12:43 ` Hans-Werner Hilse [this message]
2015-06-12 15:20   ` Bjoern Franke
2015-06-12 20:39     ` Hans-Werner Hilse
2015-06-11 13:20 ` Marek Lindner
2015-06-11 14:44   ` Bjoern Franke
2015-06-12  2:53     ` Marek Lindner
2015-06-12  4:32     ` Linus Lüssing
     [not found]       ` <1434121488.3296.8.camel@nord-west.org>
2015-06-12 20:33         ` Linus Lüssing
2015-06-14 10:20           ` Bjoern Franke

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=2dca4d7a596a3a7f250b2ef62cf9c3ec@hilses.de \
    --to=hw@haveyouseenthiscat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox