Actions
Bug #362
closedbatctl l gives inaccurate feedback when compiled without debugfs
Start date:
08/02/2018
Due date:
% Done:
100%
Estimated time:
Description
I spotted this behaviour in batctl 2018.2 with batman 2018.2:
root@node72:~# batctl l Error - mesh has not been enabled yet Activate your mesh by adding interfaces to batman-adv
but with:
root@node72:~# batctl if ens20: active tap0: active
according to ecsv batctl can't access /sys/kernel/debug/batman_adv/bat0/ if debugfs is deactivated. (This is new default.)
Maybe the message could be more accurate to give a hint how to get batctl l working.
Actions