From: Alexander Aring <alex.aring@gmail.com>
To: Henning Rogge <hrogge@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>, linux-wpan@vger.kernel.org
Subject: Re: 6lowpan with external radio
Date: Thu, 6 Nov 2014 18:08:33 +0100 [thread overview]
Message-ID: <20141106170830.GB32499@omega> (raw)
In-Reply-To: <CAGnRvupKzAbVpdokD3ix9fex0ZaTMtDH9dGZJpKWY2iyjw8_9A@mail.gmail.com>
Hi,
On Thu, Nov 06, 2014 at 06:00:49PM +0100, Henning Rogge wrote:
> On Thu, Nov 6, 2014 at 5:54 PM, Alexander Aring <alex.aring@gmail.com> wrote:
> > Hi,
> >
> > On Thu, Nov 06, 2014 at 05:33:51PM +0100, Henning Rogge wrote:
> >> I had a look at the fakelb driver,
> >>
> >> if I understand it right it just "connect" the raw-frame side of
> >> multiple 6lowpan interfaces with each other, right? So it might be
> >> part of the solution...
> >>
> >> the other part should be similar to the tun.c driver... unfortunately
> >> the tun driver got quite complex from what I can see.
> >>
> >
> > do you use a 802.15.4 radio? Then maybe the serial driver is something
> > like that what you searching for.
>
> No, its not a 802.15.4 radio... its mostly layer 1 and some "listen
> before talk/ALOHA" media access. I can send it raw frames (with a few
> header fields) and get everything the radio receives via serial port.
>
> A friend of mine suggested looking into 6lowpan instead of writing my
> own fragmentation/IP-compression/... scheme. The radio is very slow,
> so I need something efficient.
>
don't know how you can run 6LoWPAN on it. There exist 802.15.4 6LoWPAN
[0] and BTLE 6LoWPAN [1]. You need many L2 informations at 6LoWPAN level
for exmaple running IPv6 compression mechanism.
- Alex
[0] https://tools.ietf.org/html/rfc4944 - also see 6282 and 6775
[1] http://tools.ietf.org/html/draft-ietf-6lo-btle-03 (hope this is the newest one)
next prev parent reply other threads:[~2014-11-06 17:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 11:14 6lowpan with external radio Henning Rogge
2014-11-06 15:36 ` Marcel Holtmann
2014-11-06 16:33 ` Henning Rogge
2014-11-06 16:54 ` Alexander Aring
2014-11-06 17:00 ` Henning Rogge
2014-11-06 17:08 ` Alexander Aring [this message]
[not found] ` <CAP0sMCzn-cRSDi7GoeLPFKH868vdW+DJsC_ak-eZwT+GEbwwiA@mail.gmail.com>
2014-11-06 18:01 ` Henning Rogge
2014-11-06 18:13 ` Carlo Vallati
2014-11-06 18:28 ` Alexander Aring
2014-11-06 18:24 ` Alexander Aring
2014-11-06 19:34 ` Alexander Aring
2014-11-07 13:22 ` Carlo Vallati
2014-11-06 18:09 ` Carlo Vallati
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=20141106170830.GB32499@omega \
--to=alex.aring@gmail.com \
--cc=hrogge@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=marcel@holtmann.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