public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] 5Ghz ad-hoc network for batman-adv
Date: Fri, 06 Nov 2015 14:22:37 +0100	[thread overview]
Message-ID: <80380848.PJif3jmaAr@prime> (raw)
In-Reply-To: <004201d11893$53de6d00$fb9b4700$@itelsis.com>

[-- Attachment #1: Type: text/plain, Size: 1241 bytes --]

Hi Santiago,


On Friday 06 November 2015 14:02:01 Santiago Álvarez Álvarez wrote:
> Hi everybody,
> I've been working for some time in testing batman-adv protocol with several
> network topologies, and different network communications.  Right now, I'm
> trying to build a batman mesh network over 5GHz wireless modules. However,
> I'm getting errors when trying to configure the module to use one of the 5
> GHz channels.
> 
> I'm using a module with Ralink RT5572N chipset. Searching in internet, I've
> read a few comments suggesting that it's not possible to configure a 5ghz
> module in ad-hoc mode due to some kind of regulatory reasons.
> 
> Any of you have managed to get batman-adv working over a 5 ghz wireless
> network?

yes, batman-adv on 5 GHz works for us.

There are regulatory limitations for the higher 5GHz channels, but channel 
36-48 should have no restrictions for ad-hoc use - if your chip/driver 
supports it.

I would suggest to first look into getting Ad-Hoc mode working without batman-
adv before continuing any further. You might need other sticks, but there are 
definitely USB chips out there supporting Ad-Hoc (you may want to check out 
ath9k_htc based ones).

Cheers,
    Simon

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2015-11-06 13:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-06 13:02 [B.A.T.M.A.N.] 5Ghz ad-hoc network for batman-adv Santiago Álvarez Álvarez
2015-11-06 13:22 ` Simon Wunderlich [this message]
2015-11-06 13:26   ` Bastian Bittorf
2015-11-08 11:51     ` tjhowse
2015-11-08 18:22       ` Bastian Bittorf
2015-11-06 13:24 ` Markus Pargmann

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=80380848.PJif3jmaAr@prime \
    --to=sw@simonwunderlich.de \
    --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