From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <51CB7254.7030907@altermundi.net> Date: Wed, 26 Jun 2013 19:59:32 -0300 From: Gui Iribarren MIME-Version: 1.0 References: <51CB60F0.6090604@wirelesspt.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [B.A.T.M.A.N.] single radio routers and ap/adhoc interfaces Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: The list for a Better Approach To Mobile Ad-hoc Networking On 06/26/2013 07:39 PM, jonsmirl@gmail.com wrote: > > It looks like OpenWRT trunk is broken. I just sent this out on the > OpenWRT list but I haven't received a response yet. When I loaded > Steve image the hardware worked as expected. Bleeding edge often hurts :-/ (Thanks for sending that report to openwrt-devel!) The last trunk i tried and didn't find blocker bugs was r36139 With r36655 we experienced severe instability of ath9k wifi, and rolled back to r36139. Haven't tried more recent trunks than that yet. hope that helps :) about ap/sta mode: On 06/26/2013 03:46 PM, Antonio Quartulli wrote:> On Wed, Jun 26, 2013 at 02:38:16PM -0400, jonsmirl@gmail.com wrote: >> Is it a bad idea to run batman over the STA/AP mode type interfaces? > > batman-adv supports it. From the batman-adv prospective there is no problem. The > important thing is that you know what you are doing and that you take care of > properly configuring the underlying layer (e.g. Isolation of the client should > be enabled, imho). We agree :) we use this approach with *ath9k_htc* devices (usb dongles) which still suffer bugs in adhoc mode. http://blog.altermundi.net/article/batman-adv-ap-mode-with-isolation-enabled/ Cheers!