From: Sven Eckelmann <sven@narfation.org>
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
Date: Wed, 06 Feb 2019 19:14:16 +0100 [thread overview]
Message-ID: <2382079.7bZRkTAdJY@sven-edge> (raw)
In-Reply-To: <015501d4be3c$d64ad290$82e077b0$@telegrid.com>
[-- Attachment #1: Type: text/plain, Size: 1917 bytes --]
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#Synchronization
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-06 18:14 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 [this message]
2019-02-06 18:47 ` beth.flippo
2019-02-06 19:03 ` Simon Wunderlich
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=2382079.7bZRkTAdJY@sven-edge \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=beth.flippo@telegrid.com \
--cc=s.pinsky@telegrid.com \
/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