public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Gui Iribarren <gui@altermundi.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] single radio routers and ap/adhoc interfaces
Date: Wed, 26 Jun 2013 19:59:32 -0300	[thread overview]
Message-ID: <51CB7254.7030907@altermundi.net> (raw)
In-Reply-To: <CAKON4Ozy3ObsYRYTF71i4Ys7A4H5228xywXfjZxvfwrepUyjTQ@mail.gmail.com>

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!

      reply	other threads:[~2013-06-26 22:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-26 17:30 [B.A.T.M.A.N.] single radio routers and ap/adhoc interfaces jonsmirl
2013-06-26 18:02 ` Antonio Quartulli
2013-06-26 18:18   ` Steve Song
2013-06-26 18:36     ` jonsmirl
2013-06-26 18:45       ` Antonio Quartulli
2013-06-26 18:49       ` Steve Song
2013-06-26 18:56         ` jonsmirl
2013-06-26 19:01           ` Antonio Quartulli
2013-06-26 20:21             ` jonsmirl
2013-06-26 19:02           ` jonsmirl
2013-06-26 18:38     ` jonsmirl
2013-06-26 18:46       ` Antonio Quartulli
2013-06-26 21:45 ` cmsv
2013-06-26 22:39   ` jonsmirl
2013-06-26 22:59     ` Gui Iribarren [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51CB7254.7030907@altermundi.net \
    --to=gui@altermundi.net \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox