public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Randy Graham <surfbytes@gmail.com>
Subject: Re: [B.A.T.M.A.N.] batman over 802.15.4 .
Date: Tue, 20 Nov 2012 09:27:39 +0100	[thread overview]
Message-ID: <75191138.5RcUHhBkvt@bentobox> (raw)
In-Reply-To: <CAG_HyLz9B9r=u5jSw8xy+4rfG9anB6vqK+ggMGSmRossMCx4CQ@mail.gmail.com>

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

On Monday 19 November 2012 20:25:34 Randy Graham wrote:
[...]
> 1. Will batman-adv work over 802.15.4 ?
[...]
> 2. Can batman-adv work with either of these interfaces ?
> 
> I tried configuring these interfaces using 'batctl' but it complains
> that they are an unsupported type.
> 'iwconfig' reports these interfaces as having 'no wireless extensions'
> which I suspect is the issue.

No, batman-adv works on 802.3 compatible interfaces (aka ARPHRD_ETHER) which 
provide special mac behaviour. This has nothing to do with the wireless 
extensions (which are deprecated anyway).

> Please let me know if running b.a.t.m.a.n. over 802.15.4 is feasible.

802.15.4 has the type ARPHRD_IEEE802154 for its fake hard interfaces. So you 
need an "ethernet emulation" layer on top of it to use it with batman-adv. I 
don't know whether the mac layer works well enough in theory to be used with 
batman-adv.

Kind regards,
	Sven

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

  reply	other threads:[~2012-11-20  8:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-20  4:25 [B.A.T.M.A.N.] batman over 802.15.4 Randy Graham
2012-11-20  8:27 ` Sven Eckelmann [this message]
2012-11-20  9:24   ` Antonio Quartulli
2012-11-20 23:37     ` Randy Graham
2012-11-20 23:41       ` Antonio Quartulli
2012-11-20  8:45 ` Marek Lindner

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=75191138.5RcUHhBkvt@bentobox \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=surfbytes@gmail.com \
    /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