All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Simon Wunderlich <sw@simonwunderlich.de>,
	Daniel Golle <daniel@makrotopia.org>
Cc: battlemesh@ml.ninux.org, gnunet-developers@gnu.org,
	linux-wireless@vger.kernel.org
Subject: Re: [Battlemesh] wifibroadcast
Date: Tue, 25 Apr 2017 16:37:49 +0200	[thread overview]
Message-ID: <1493131069.2609.1.camel@sipsolutions.net> (raw)
In-Reply-To: <1806801.tVQKAhPZbv@prime>

On Sun, 2017-04-23 at 00:01 +0200, Simon Wunderlich wrote:

> What is missing (or at least I didn't find it
> and  implemented something on my own) is a library/function to build
> radiotap  headers (i.e. for writing). There are quite a few things to
> consider (padding, alignment, etc). 

Yeah, that could be done - but generally it's actually quite easy since
a given application will only have a given subset of radiotap
information it generates... wrapping all of that with some kind of
helper function could result in pretty bloated code.

> To make it useful, you would also need to build ieee80211 headers at
> the same time ...

I don't really agree - these can and should be separate IMHO.

Anyway, there isn't any such thing today.

johannes

      reply	other threads:[~2017-04-25 14:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANjd3nfeiGgaHMcgOyKOKhRRKEwnn43VgC4GRcw-fuCkCdg2zQ@mail.gmail.com>
     [not found] ` <2945991.ay5rM9MeUZ@prime>
     [not found]   ` <20170422153703.GE1681@makrotopia.org>
2017-04-22 22:01     ` [Battlemesh] wifibroadcast Simon Wunderlich
2017-04-25 14:37       ` Johannes Berg [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=1493131069.2609.1.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=battlemesh@ml.ninux.org \
    --cc=daniel@makrotopia.org \
    --cc=gnunet-developers@gnu.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sw@simonwunderlich.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.