My syslog is flooded with the message above.
Looking around I found in batctl o the same mac as originator as the next
root@da88:~# batctl o
[B.A.T.M.A.N. adv openwrt-2019.2-7, MainIF/MAC:
wlan1-mesh_252/78:a3:51:16:da:88 (bat0/7e:30:a4:a8:83:a9 BATMAN_IV)]
Originator last-seen (#/255) Nexthop [outgoingIF]
* 02:95:39:16:d9:ec 0.010s (239) 02:13:f2:16:d9:ec [eth0-2_252]
* 02:95:39:16:d9:e8 2.180s (202) 02:13:f2:16:d9:ec [eth0-2_252]
* 02:95:39:16:d9:48 0.660s (189) 02:13:f2:16:d9:ec [eth0-2_252]
* 02:13:f2:16:d9:ec 0.010s (238) 02:13:f2:16:d9:ec [eth0-2_252]
* dc:9f:db:0a:15:34 1.420s (193) 02:13:f2:16:d9:ec [eth0-2_252]
May this be the reason?
> On Aug 26, 2020 19:02, amuza <amuza(a)riseup.net> wrote:
>> How could I see through the command line other active nodes?
> This is a super important question and I'm not sure if the Babeld case have been documented anywhere yet, thanks for asking this!
> For the neighbours known by Batman-adv you can use the command:
> batctl o
> For the neighbours (and much other info) known by Babeld you can use:
> echo dump | nc ::1 30003
> Which sends a packet with the word "dump" to the same router at a door configured in /etc/config/babeld (if I remember correctly...) and shows the answer.
I keep mising that very nice BMX6 graph Luci had on LiMe 17.06. I get
very mcuh lost without it.
What does the following command exactly do?
I would like to understand its output.
LiMe master development (master rev. 19cc376 20201215_2028)
compiled with firstbootwizard selected but ubus-fbw inadvertently
Then I installed ubus-fbw via opkg which broke the image, device not
Then I compiled ubus-fbw also selected, device not accessible.
The reason for trying firstbootwizard is having the possibility to
configure the community mesh name without changing any file.
I have very limited experience with FirstBootWizard and lime-app.
I basically used them just to check that they do not fail terribly but not much more.
SAn, Marcos Gutierrez and German Ferrero (who I hope are reading this mailing list) are the ones who really know how those tools work or not work...
On Dec 16, 2020 11:22, Juergen Kimmel <juergenkimmel(a)gmail.com> wrote:
> Hi Ilario,
> is your opinion still valid?
> I read this:
> The LibreMesh team is happy to announce a new version of LibreMesh, 2020.1 "ExpansiveEmancipation"
> * first-boot-wizard, an optional helper to deploy and extend the network that is well integrated with the LimeApp.
> On the other hand selecting firstbootwizard and ubus-fbw breaks the image
> Am So., 13. Dez. 2020 um 22:28 Uhr schrieb Ilario Gelmetti <iochesonome(a)gmail.com>:
>> On 12/13/20 12:37 PM, Juergen Kimmel wrote:
>> > But without FirstBootWizard It's not possible to configure the network??
>> lime-app has limited configuration capabilities (intentionally), an
>> attempt of list of lime-app features can be found at
>> If you want to have full access to configuration you'll have to access
>> the router using SSH, add configuration lines in /etc/config/lime-node
>> and apply it with "lime-config" command.
>> The documentation for /etc/config/lime-node is on the documentation of
>> the website:
>> and in the lime-example.txt file which can be found online at
>> or on the router at
>> If you cannot connect to the router using SSH, check out the
>> documentation on the website:
>> lime-users mailing list
On 12/15/20 9:44 AM, ignifugo wrote:
> On 15/12/20 05:19, SAn via lime-users wrote:
>> The LibreMesh team is happy to announce a new version of LibreMesh, 2020.1 "ExpansiveEmancipation".
>> Three years of work, 882 commits, 23 developers, tons of bug fixes and improvements!
> Cold be really nice, have a publish place where is possible give a
> feedback of the users/communities about the update and the result...
Yesssss that would be great!
What do you propose?
> I'll write sure in our blog, after I'll pass the link.
Nice :D Thanks!