Il 28 febbraio 2012 09:21, Marek Lindner <lindner_marek(a)yahoo.de> ha scritto:
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
That msh0 is the name of logical network and wlan0 is the real name of
The part about wlan0 I understand - the question was what happens
if the interface is not named wlan0?
yes. if in your batman-adv
interface you put wlan0 (the real interface
name) you don't have to sleep.
The problem is that hotplug.d, when a new interface was added, at
99-batman-adv script time it try to check if the new interface (es.
wlan0) is part of batman-adv interface definitions so now if in your
batman-adv config file you have msh0, the script try to find the real
interface name of msh0 and it fail because it is not be knowned at
this time. The only way to get it to work properly is to wait for some
seconds (3 seconds if you have only one vif, 4 for 2 interface es
adhoc + ap).
This could be your wireless config file:
option 'device' 'radio0'
option 'ifname' 'msh0'
option 'mode' 'adhoc'
option 'ssid' 'mesh'