Skip to contentSkip to conversation

use_count = 1 / device stuck on reboot or netifd restart

B.A.T.M.A.N. Ufo 2 participants 2 messages Feb 25, 2015

lore
Share & tools
lore

Ufo

author
#0 lore raw

in leipzig since months we have problems with batman-adv and these start/stop scripts or netifd-stuff.

we thought that this might be our own special problem, because we are using more than one batman-adv instance (separated by vlan).

but its still there, also on openwrt-cc-trunk, now also on our batman-adv super-gluon-node-servers (using fastd) on virtualized x86-openwrt.
so f.i. i can crash that system in a way by: etc/init.d/fastd stop

please help us and have a look at our local ticket number 23
https://github.com/freifunk/firmware-leipzig/issues/23

good luck
ufo

root@vpnb9:~# batctl -v
batctl 2014.4.0 [batman-adv: 2014.4.0]
root@vpnb9:~# fastd -v
fastd v17
root@vpnb9:~# cat /etc/openwrt_*
DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='Bleeding Edge'
DISTRIB_REVISION='r44497'
DISTRIB_CODENAME='chaos_calmer'
DISTRIB_TARGET='x86/kvm_guest'
DISTRIB_DESCRIPTION='OpenWrt Chaos Calmer r44497'
DISTRIB_TAINTS=''
r44497
Signature · 2 lines
---
Freifunk Leipzig http://leipzig.freifunk.net
#1 lore raw
Quoted 6 lines · On Wednesday, February 25, 2015 03:47:40 Ufo wrote:

in leipzig since months we have problems with batman-adv and these start/stop scripts or netifd-stuff.

we thought that this might be our own special problem, because we are using more than one batman-adv instance (separated by vlan).

Quoted 7 lines

but its still there, also on openwrt-cc-trunk, now also on our batman-adv super-gluon-node-servers (using fastd) on virtualized x86-openwrt.
so f.i. i can crash that system in a way by: etc/init.d/fastd stop

please help us and have a look at our local ticket number 23
https://github.com/freifunk/firmware-leipzig/issues/23

I looked into the ticket but there isn't much info on how to replicate the issue. What is the simplest openwrt setup with which you can see 'count' problem?

Please note, that I have zero experience with fastd and/or your firmware which is why I'd prefer to replicate the matter on plain OpenWrt.

Cheers,
Marek