Arjan Oosting wrote:
Op vr, 09-06-2006 te 03:40 +0300, schreef Faidon Liambotis:
Hi,
Sorry for taking so long to respond to this bug report, even though I've
mailed some of you in private.
I wasn't sure of what to do and I was hoping that the -old/-ng situation
would resolve itself with the p
Faidon Liambotis wrote:
Hi,
Sorry for taking so long to respond to this bug report, even though I've
mailed some of you in private.
I wasn't sure of what to do and I was hoping that the -old/-ng situation
would resolve itself with the passing of time.
As madwifi upstream now recommends -ng as the
Op vr, 09-06-2006 te 03:40 +0300, schreef Faidon Liambotis:
> Hi,
> Sorry for taking so long to respond to this bug report, even though I've
> mailed some of you in private.
> I wasn't sure of what to do and I was hoping that the -old/-ng situation
> would resolve itself with the passing of time.
>
Hi,
Sorry for taking so long to respond to this bug report, even though I've
mailed some of you in private.
I wasn't sure of what to do and I was hoping that the -old/-ng situation
would resolve itself with the passing of time.
As madwifi upstream now recommends -ng as the stable version and
consid
Hi,
Arjan Oosting wrote:
> I am using the madwifi drivers (from madwifi-source) and I guess the
change
> from madwifi to madwifi-ng headers is the cause of this failure
> * Update madwifi headers to madwifi-ng, rev1390.
As (joint) maintainer of madwifi in debian (and madwifi-ng *out* of
debia
Package: hostapd
Version: 1:0.5.0-1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, after upgrading hostapd to version 0.5.0-1 it failed with
the following message:
Starting advanced IEEE 802.11 management: hostapdioctl[unknown???]: Operation
not supported
ioctl[unknown???
6 matches
Mail list logo