On Wednesday 11 August 2010 16:23:22 Tim wrote:
On 11.08.2010 13:20, Sven Eckelmann wrote: [...]
what you could try is to setup the stuff by yourself using
http://open-mesh.net/wiki/batman-adv-quick-start-guide and test which command
may cause the problem (when it is batman-adv related).
I tried to configure it as described in the guide and I think I some kind of found the problem:
Before being able to add wlan0 to the batman interfaces, I need to create the interface wlan0 and to remove "option disabled 1" from /etc/config/wireless, because otherwise wlan will be disabled by default.
Way1: When removing "option disabled 1" first and then doing "/etc/init.d/network restart" I get the following message: "root@OpenWrt:/# /etc/init.d/network restart udhcpc (v1.15.3) started Sending discover... Configuration file: /var/run/hostapd-phy0.conf Segmentation fault Failed to start hostapd for phy0 root@OpenWrt:/# Sending discover... Sending discover..."
So you mean that the device has radio0 and wlan0, but not bat0 configured? And still it crashes? Is batman-adv loaded or unloaded completely in that situation (check `lsmod` output)?
It is not clear to me how batman-adv is involved when it is not loaded. But it is somewhat active when it is only loaded, but bat0 is not configured... because it has netdev notification enabled - which means that it gets informed about added and removed (and some other things) devices. It is maybe related to that.
If it is loaded, but doesn't get configured when it crashes then please onload batman-adv using `rmmod batman-adv` and try to restart the network (without the batman-adv stuff loaded or configured).
By the way, you seem to have shell access after that segfault. Could you please post the `dmesg` output after that segfault - thanks.
And please don't forget to write the complete version number of batman-adv which you are using (I can guess it using the backfire branch, but it is safer to get that information from you).
Best regards, Sven