On Mon, Nov 09, 2020 at 03:45:05PM +0100, Andy Schopf wrote:
Hi SAn,
Am Mo., 9. Nov. 2020 um 14:25 Uhr schrieb Daniel Golle <
daniel(a)makrotopia.org>gt;:
On Mon, Nov 09, 2020 at 02:11:00PM +0100, Andy
Schopf wrote:
Hi SAn,
you are right. babeld is not started. I hav to start it manually in
/etc/init.d
with
./babeld trace
then I get an IP address.
This is strangely *not *working in the LuCI-Interface -> startup: with
restart or start/stop (no output in logread)
with the manual method above I get following:
Mon Nov 9 09:33:55 2020 daemon.warn procd: Seccomp support for
babeld::instance1 not available
Are you trying to start babled with seccomp (or seccomp-tracing)
support?
I am not aware of starting babeld with sccomp (I don't know what this is...
;-) )
Ok, that's a bit weird then. Please share the output of
env
as well as
cat /etc/init.d/babeld
as there needs to be something which tells procd to attempt using
seccomp.
I don't see any seccomp filter defined for
babled in
openwrt-routing/packages repo...?
Mon Nov 9 09:33:55 2020 daemon.err babeld[4253]:
Warning: couldn't
determine channel of interface wlan0-mesh_17.
Mon Nov 9 09:33:55 2020 daemon.err babeld[4253]: Warning: couldn't
determine channel of interface eth0_17.
Mon Nov 9 09:34:00 2020 cron.err crond[1330]: USER root pid 4288 cmd
((sleep $(($RANDOM % 30));
/etc/shared-state/publishers/shared-state-publish_vouchers &&
shared-state
sync pirania &> /dev/null)&)
Mon Nov 9 09:34:00 2020 cron.err crond[1330]: USER root pid 4289 cmd
((for
dataFile in /var/shared-state/data/* ; do
shared-state bleach $(basename
$dataFile .json); done &> /dev/null)&)
And every reboot no babeld :-(
A Problem of the openwrt snapshot maybe? (Build is from today)
I assume this is ath79/generic?
Nope this is a Rampis mt7620 device.
And which exact commit are you using?
where do I find this Information?
This is what I see on login:
OpenWrt SNAPSHOT, r14877-e267445510
Yes, that's the information I was looking for.
I can try to reproduce your problem on x86/64 in QEMU...
Thank you! :-D
>
> >
> > Regards
> > Andy
> >
> >
> > Am So., 8. Nov. 2020 um 01:48 Uhr schrieb SAn <spiccinini(a)altermundi.net
> >:
> >
> > > Hi Andy, it seems that babeld Is not running or not working properly.
> > > Check that it is running in all the nodes.
> > >
> > > Best
> > > SAn
> > >
> > > On November 6, 2020 10:38:25 AM GMT-03:00, Andy Schopf <
> > > andymcschopf(a)gmail.com> wrote:
> > > >Hi all,
> > > >
> > > >I have since a few days the Problem, that my mesh nodes get any ipv4
> > > >addresses.
> > > >So connected to the mesh node there is no way to the internet. Only
on
> > > >the
> > > >Gateway Nodes. There I see only ipv6 addresses in direction to the
> mesh
> > > >nodes. on the nodes the lime app shows no DNS and no ipv4/ipv6.
> > > >Any suggestions?
> > > >
> > > >Regards,
> > > >Andy
> > >
>
> > _______________________________________________
> > lime-users mailing list
> > lime-users(a)lists.libremesh.org
> >
https://lists.libremesh.org/mailman/listinfo/lime-users
>
> _______________________________________________
> lime-users mailing list
> lime-users(a)lists.libremesh.org
>
https://lists.libremesh.org/mailman/listinfo/lime-users
_______________________________________________
lime-users mailing list
lime-users(a)lists.libremesh.org
https://lists.libremesh.org/mailman/listinfo/lime-users