Sven Eckelmann wrote:
I think that you found a bug in batman-adv. Please add the wlan0 interface to /proc/net/batman-adv/interfaces when wlan0 is up.
Ok, problem is that the interface starts as IF_INACTIVE, then switches to IF_TO_BE_ACTIVATED when you activate it with ifconfig, but never reaches IF_ACTIVE. It should get the IF_TO_BE_ACTIVATED status in hardif_activate_interface and the IF_ACTIVE in schedule_own_packet. I would guess that this function is never called in that situation.
Following called-by tree: - schedule_own_packet - send_outstanding_bat_packet - new_aggregated_packet (indirect over worker queue) - add_bat_packet_to_list - schedule_own_packet (who sees the loop here?) - schedule_forward_packet - hardif_add_interface
I would guess that either schedule_own_packet must be moved to hardif_activate_interface or the worker queue must be started otherwise when hardif_activate_interface is called in hard_if_event. I would leave the that to Marek as he knows what side effects are problematic in that situation
Best regards, Sven