[B.A.T.M.A.N.] alfred init.d bugs

[B.A.T.M.A.N.] alfred init.d bugs

[Gui Iribarren]

alfred will refuse to start if bat0 doesn't exist yet

root@48cfeb:~# alfred -i br-lan -m -b bat0
Could not find transtable_global for interface bat0. Make sure it is a 
valid batman-adv soft-interface

at boot time this can create a race condition, since wifi interfaces can 
take longer to be brought up, making bat0 appear much later than the 
time alfred init.d script is run. In the following example, 4 seconds later.

Sun Nov  3 05:09:13 2013 kern.emerg /etc/rc.d/S99alfred: starting alfred
Sun Nov  3 05:09:13 2013 kern.emerg /etc/rc.d/S99alfred: starting batadv-vis
Sun Nov  3 05:09:13 2013 kern.emerg can't connect to unix socket: 
Connection refused
Sun Nov  3 05:09:13 2013 kern.emerg can't connect to unix socket: 
Connection refused
Sun Nov  3 05:09:17 2013 kern.info kernel: [   28.620000] batman_adv: 
bat0: Adding interface: wlan0ah.145
Sun Nov  3 05:09:17 2013 kern.info kernel: [   28.620000] batman_adv: 
bat0: Interface activated: wlan0ah.145
Sun Nov  3 05:09:17 2013 daemon.notice netifd: Interface 
'lm_wlan0ah_bata' is now up
Sun Nov  3 05:09:17 2013 kern.info kernel: [   29.060000] batman_adv: 
bat0: bridge_loop_avoidance: Changing from: disabled to: enabled
Sun Nov  3 05:09:17 2013 kern.info kernel: [   29.080000] batman_adv: 
bat0: distributed_arp_table: Changing from: enabled to: disabled

sending a patch for this in a minute, along with another bugfix which 
needs less explanation :)