From: Kalle Valo <kalle.valo@iki.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: python nl80211 code
Date: Tue, 01 Dec 2009 12:31:41 +0200 [thread overview]
Message-ID: <87638r6l4i.fsf@purkki.valot.fi> (raw)
In-Reply-To: <1259659425.32171.54.camel@johannes.local> (Johannes Berg's message of "Tue\, 01 Dec 2009 10\:23\:45 +0100")
Johannes Berg <johannes@sipsolutions.net> writes:
> On Tue, 2009-12-01 at 10:53 +0200, Kalle Valo wrote:
>> Hello,
>>
>> I want to run some tests through nl80211 and, as usual, I prefer to
>> use python for that. Are there any scripts/examples using nl80211 with
>> python available? Preferably with an open enough license.
>
> http://git.sipsolutions.net/pynl80211.git/
Thanks. This looks interesting but doesn't compile right now:
$ make
Checking netlink numbers:
check.r5cOZHc/check.c: In function 'main':
check.r5cOZHc/check.c:63: error: lvalue required as left operand of
assignment
check.r5cOZHc/check.c:78: error: 'NL80211_CHAN_MAX' undeclared (first
use in this function)
check.r5cOZHc/check.c:78: error: (Each undeclared identifier is
reported only once
check.r5cOZHc/check.c:78: error: for each function it appears in.)
check.r5cOZHc/check.c:80: error: lvalue required as left operand of
assignment
check.r5cOZHc/check.c:86: error: 'NL80211_RATE_MAX' undeclared (first
use in this function)
[...]
The parsing of nl80211 seems to fail. If I find some time, I try to
look at it.
> Doesn't have much of a license but was intended to be GPLv2, but there
> was only one commit from somebody other than me who'd probably relicense
> if needed.
That's good enough :)
--
Kalle Valo
next prev parent reply other threads:[~2009-12-01 10:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 8:53 python nl80211 code Kalle Valo
2009-12-01 9:23 ` Johannes Berg
2009-12-01 10:31 ` Kalle Valo [this message]
2009-12-01 11:24 ` Johannes Berg
2009-12-01 11:47 ` Kalle Valo
2009-12-01 11:50 ` Johannes Berg
2009-12-01 11:52 ` Kalle Valo
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=87638r6l4i.fsf@purkki.valot.fi \
--to=kalle.valo@iki.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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