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: b.a.t.m.a.n@lists.open-mesh.org
Cc: beth.flippo@telegrid.com, 'Sven Eckelmann' <sven@narfation.org>,
	s.pinsky@telegrid.com
Subject: Re: [B.A.T.M.A.N.] Alfred problem reading other nodes
Date: Wed, 06 Feb 2019 20:03:09 +0100	[thread overview]
Message-ID: <6030797.OfDuFm2WhJ@prime> (raw)
In-Reply-To: <022801d4be4c$60a1dec0$21e59c40$@telegrid.com>

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

Hi Beth,

as Sven said, if both nodes are running in master mode then they should 
regularly synchronize their data. This happens by sending unicast (!) UDP 
packets to their respective link-local IPv6 addresses. In your dump, we can 
only see broadcasts of 4 bytes, most likely the announcements. But as you 
said, two different hosts are sending those announcements, so that part seems 
to work.

Since announcement from both ends are visible, it could still be that your 
firewall drops it. Did you try disabling the firewall completely (e.g. /etc/
init.d/firewall stop, iptable -F etc ...)?

If that doesn't help, the best way would be to instrument the code (recv.c as 
Sven suggested) to see if the announcements are received. we don't really have 
debug code there.

Cheers,
      Simon

On Wednesday, February 6, 2019 1:47:14 PM CET beth.flippo@telegrid.com wrote:
> We are using a gateworks board and built the latest version from their bsp
> but we had batman-adv, batctl and Alfred ipk built at version 2018.0.
> Batman and batctl are both working.
> 
> root@OpenWrt:~# uname -a
> Linux OpenWrt 4.4.0 #16 SMP Tue Jan 29 19:41:46 UTC 2019 armv7l GNU/Linux
> root@OpenWrt:~# cat /etc/openwrt_release DISTRIB_ID='Gateworks'
> DISTRIB_RELEASE='Gateworks Ventana 16.02@dd98aee-dirty'
> DISTRIB_REVISION='r48868'
> DISTRIB_CODENAME='designated_driver'
> DISTRIB_TARGET='imx6/generic'
> DISTRIB_DESCRIPTION='Gateworks Designated Driver Gateworks Ventana
> 16.02@dd98aee-dirty'
> DISTRIB_TAINTS='no-all busybox'
> root@OpenWrt:~#
> 
> 
> 
> -----Original Message-----
> From: Sven Eckelmann <sven@narfation.org>
> Sent: Wednesday, February 6, 2019 1:14 PM
> To: b.a.t.m.a.n@lists.open-mesh.org
> Cc: beth.flippo@telegrid.com; s.pinsky@telegrid.com
> Subject: Re: [B.A.T.M.A.N.] Alfred problem reading other nodes
> 
> On Wednesday, 6 February 2019 17.56.00 CET beth.flippo@telegrid.com wrote:
> [...]
> 
> > I am having a problem getting alfred retrieve info from other nodes.
> > I am running openwrt and alfred 2018.0.
> 
> Which OpenWrt version should that be? There is no release with 2018.0 and
> the current version in master is also newer.
> 
> > I am able to start the alfred server with no errors both from boot and
> > the command line.
> > 
> > root@OpenWrt:~# /etc/init.d/alfred restart
> > /etc/init.d/alfred: waiting 30 secs for br-lan address...
> > /etc/init.d/alfred: starting alfred
> > /etc/init.d/alfred: starting batadv-vis
> > 
> > I can see it with ps
> > 
> > 4290 root       816 S    /usr/sbin/alfred -i br-lan -m -b bat0
> > 
> > I can issue a set and then a receive and I see the value I set but
> > only locally.  It does not get any info from the other nodes in my
> > network.  They are all running alfred servers as master.
> 
> Have you checked whether process_alfred_announce_master (recv.c) rejects the
> incoming packet for some reason and thus doesn't add it to the server list?
> 
> If not, have you checked whether sync_data (send.c) really sends out the
> data via push_data to the remote server?
> 
> > I have added a firewall rule to open the port.
> > 
> > If I have 2 nodes running alfred and I run 'tcpdump -i br-lan udp port
> > 16962' - I see packets from the other node:
> > 
> > 16:21:49.279086 IP6 fe80::2d0:12ff:fe00:f0c7.16962 > ip6-allnodes.16962:
> > UDP, length 4
> 
> [...]
> 
> > I think these might be the master announcements but when I issue an
> > alfred -r # - I do not see any new messages in the tcpdump.
> 
> If all daemons are in server mode then they will not create a request via
> `alfred -r`. Instead, they regularly sync [1] their facts between each other
> (same port but different packet type).
> 
> Kind regards,
> 	Sven
> 
> [1]
> https://www.open-mesh.org/projects/alfred/wiki/Alfred_architecture#Synchroni
> zation


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

  reply	other threads:[~2019-02-06 19:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06 16:56 [B.A.T.M.A.N.] Alfred problem reading other nodes beth.flippo
2019-02-06 18:14 ` Sven Eckelmann
2019-02-06 18:47   ` beth.flippo
2019-02-06 19:03     ` Simon Wunderlich [this message]
2019-02-08 15:58       ` beth.flippo
2019-02-08 17:26         ` Sven Eckelmann

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=6030797.OfDuFm2WhJ@prime \
    --to=sw@simonwunderlich.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=beth.flippo@telegrid.com \
    --cc=s.pinsky@telegrid.com \
    --cc=sven@narfation.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