public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: Jonathan Haws <jhaws@sdl.usu.edu>
Cc: b.a.t.m.a.n@lists.open-mesh.org, gary <guohuizou2000@sina.com>
Subject: Re: [B.A.T.M.A.N.] alfred and batadv-vis issue
Date: Thu, 18 Oct 2018 08:22:39 +0200	[thread overview]
Message-ID: <2254141.JEhYi27MYC@bentobox> (raw)
In-Reply-To: <02ef01d466a6$f0c629f0$d2527dd0$@sina.com>

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

On Donnerstag, 18. Oktober 2018 13:53:44 CEST gary wrote:
> I setup a testbed like this.  (BBN = backbone node)
> 
> Switch ---------->BBN1 --------------->MP1
>         |
> 		------->BBN2---------------->MP2
> 
> MP1 and MP2 may select BBN1 or BBN2 as gateway. 
> On both MP1 and MP2, I enable Alfred and batadv-vis as follows:
> alfred -i br0 -4 224.0.0.1 -m &
> batadv-vis -i bat0 -s

Looks like you are using the experimental IPv4 support which I don't want to 
actively support. So Jonathan Haws should take care of this.

> 
> when I run batadv-vis again on MP1, I can't get the info from MP2. 
> If I ping the ip address of MP2 from MP1, MP1 will get MP2's mac address by arp.
> And then I run batadv-vis again, I can get the data from MP2 now.
> 
> Is there any configure or method to get MP2's info without ping test?

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-10-18  6:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18  5:53 [B.A.T.M.A.N.] alfred and batadv-vis issue gary
2018-10-18  6:22 ` Sven Eckelmann [this message]
2018-10-22 17:36   ` Jonathan Haws
2018-10-23  3:02     ` gary
2018-10-23  4:04       ` Jonathan Haws
2018-10-23  6:29         ` Sven Eckelmann
2018-10-23  9:52           ` gary
2018-10-23 10:25             ` Sven Eckelmann
2018-10-23 13:50           ` Jonathan Haws
2018-10-23 14:06             ` Sven Eckelmann
2018-10-23 14:11               ` Jonathan Haws
2018-10-23 14:16                 ` Sven Eckelmann
2018-10-24 18:39                   ` Jonathan Haws
2018-10-25  6:15                     ` Sven Eckelmann
2018-10-25  9:06                       ` gary
2018-10-29 16:07                         ` Jonathan Haws
2018-10-29 16:48                           ` Sven Eckelmann
2018-10-29 17:25                             ` Jonathan Haws
2018-10-29 17:34                               ` Sven Eckelmann
2018-10-30  5:24                           ` gary
2018-10-30 14:20                             ` Jonathan Haws
2018-10-30 14:27                               ` Sven Eckelmann
  -- strict thread matches above, loose matches on Subject: below --
2018-10-25 13:40 Jonathan Haws

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=2254141.JEhYi27MYC@bentobox \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=guohuizou2000@sina.com \
    --cc=jhaws@sdl.usu.edu \
    /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