Ok in this email my proposal patch. I've to sleep 4s if you have an ap + adhoc vifs. [ "$(echo $interface | awk '$0 ~ /^wlan[0-9]*/')" ] && sleep 4s For convenience I sleep only if an wlan was triggered. If you have only one interface in adhoc mode per radio 3 seconds are enought. bye ---------- Messaggio inoltrato ---------- Da: Marek Lindner <lindner_marek(a)yahoo.de&gt; Date: 11 febbraio 2012 11:08 Oggetto: Re: /lib/batman-adv/config.sh A: Filippo Sallemi <tonyputi(a)gmail.com&gt; On Friday, February 10, 2012 01:21:21 you wrote: > > Yeah - looks good. > > I still don't get why we don't need to wait 3/5 seconds anymore. Can you > > explain this ? > > No i'm wrong we need to wait 3 seconds... i think that the sleep call > could be moved to hotplug.d/99-batman-adv when an interface is added > to mesh interface. > I need some time. Ok - I left the "sleep 3s" in the file. I applied your config_bat/bat_config as well as the forgotten ap_isolation config fix. Since the for loop does not fix the wait problem why do you wish to change it? I am referring to your suggested change: # Load network config here just in case! config_load network for iface in $interfaces; do        # copy iface into ifname        local ifname=$iface        [ -f "/sys/class/net/$ifname/batman_adv/mesh_iface" ] || {                # if ifname was not found try to find it via uci config                config_get ifname $iface ifname                [ -f "/sys/class/net/$ifname/batman_adv/mesh_iface" ] || continue        }        [ "$ifname" = "$interface" ] && echo $mesh > /sys/class/net/$ifname/batman_adv/mesh_iface done bat_add_interface() and bat_del_interface() have the same loop but we only change one ? The only difference I can see is another added variable and not calling "uci -q -P/var/state get network.$iface.ifname". Why ? Cheers, Marek -- Filippo Sallemi

On Monday, February 27, 2012 01:49:44 Filippo Sallemi wrote: > Ok in this email my proposal patch. > I've to sleep 4s if you have an ap + adhoc vifs. > > [ "$(echo $interface | awk '$0 ~ /^wlan[0-9]*/')" ] && sleep 4s > > For convenience I sleep only if an wlan was triggered. If you have > only one interface in adhoc mode per radio 3 seconds are enought. What if somebody calls his interfaces in a different way ? As you know the name can freely be chosen.

Regards, Marek

On Monday, February 27, 2012 20:42:58 Filippo Sallemi wrote: > Il 27 febbraio 2012 09:11, Marek Lindner <lindner_marek(a)yahoo.de&gt; ha scritto: > > On Monday, February 27, 2012 01:49:44 Filippo Sallemi wrote: > >> Ok in this email my proposal patch. > >> I've to sleep 4s if you have an ap + adhoc vifs. > >> > >> [ "$(echo $interface | awk '$0 ~ /^wlan[0-9]*/')" ] && sleep 4s > >> > >> For convenience I sleep only if an wlan was triggered. If you have > >> only one interface in adhoc mode per radio 3 seconds are enought. > > > > What if somebody calls his interfaces in a different way ? As you know > > the name can freely be chosen. > > You can chose another name instead of wlan0 wlan0-1 wlan1 wlan1-1 eth0 eth1 > ...? Yes, you can. I thought you were doing it to after I saw your config: config 'mesh' 'mesh'       option 'interfaces' 'msh0' msh0 does not look like wlanX at all, wouldn't you say so ? Cheers, Marek

On Tuesday, February 28, 2012 16:06:44 Filippo Sallemi wrote: > Ok but i' dont wait for this. Hotplug was called when a new interface > is added. msh0 is no a real interface so when wlan0 is added I sleep 4 > seconds and check if wlan0 is part o batman-adv interfaces. Sorry, I don't understand. What do you mean with "msh0" is not a real interface ?

if the interface is not named wlan0?

This could be your wireless config file: config 'wifi-iface'        option 'device' 'radio0'        option 'ifname' 'msh0'        option 'mode' 'adhoc'        option 'ssid' 'mesh' Cheers, Marek