Hi Junichi,
On Friday 28 July 2006 08:46, Junichi Uekawa wrote:
Package: module-assistant
Version: 0.10.6
Hi,
#!/bin/sh
set -e
SYSTEMMAP=/boot/System.map-_KVERS_
if [ -f $SYSTEMMAP ] ; then
depmod -ae -F $SYSTEMMAP _KVERS_
elif [ `uname -r` = _KVERS_ ]
On Wednesday 26 July 2006 19:43, Rui Pedro Lopes wrote:
Package: wpasupplicant
Version: 0.5.4-2
Severity: normal
Hi,
I've been having difficulties in using wpa supplicant with EAP-TTLS with
ipw2100. I believe that the problem is with some ioctl call:
# wpa_supplicant -iwlan -Dipw -c
Hi Paul,
I cannot see where in module-assistant that states or suggests the CC
environment variable is modified by it.
Specifically, I could not find any reference in:
/usr/share/doc/modules-assistant/HOWTO-devel
or
/usr/bin/module-assistant
I'd like to discuss this further though, and
Hi Fathi,
This seems like something that module-assistant could/should provide, so that
_all_ modules benefit, rather than a ndiswrapper specific hack.
If it turns out that ndiswrapper is actually at fault, and not just a victim
of some gcc transistion, then we can do something locally.
What
Hi Mike,
Will add a note about this to the NEWS file (along with a hint about using the
debian wpasupplicant ifupdown integration) and will consider this report
closed.
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
Package: rt2400-source
Version: 1.2.2+cvs20060620-1
Severity: important
Tags: patch
The module will fail with the following error:
make[1]: Entering directory `/home/kel/src/linux-2.6.17-kel-4'
CC [M] /home/kel/src/modules/rt2400/rtmp_main.o
/home/kel/src/modules/rt2400/rtmp_main.c:55: error:
One adjustment I did not make in the patch was the difference of default
ifname between debian and upstream.
Thanks, kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Just a follow up to mention that we do almost no driver auto-detection
currently, and that is also the stance of upstream:
http://hostap.epitest.fi/bugz/show_bug.cgi?id=57
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
Andreas Janssen wrote:
Package: hostapd
Version: 1:0.5.3-1
Severity: wishlist
A new upstream version of hostapd (0.5.4) has been released on 2006-06-20.
Please update the Debian package.
It has been prepared and should appear in the archive quite soon.
Thanks, Kel.
--
To UNSUBSCRIBE,
reopen 372208
|retitle |372208 Orinoco and wpa_supplicant not working with WEP
thanks
Hi,
I have a bad feeling about the included patch and would like to drop it
for a few reasons:
1. I currently experience problems with WEP and madwifi (using wext
ioctl's), and have had difficulty
Soeren Sonnenburg wrote:
On Fri, 2006-07-14 at 22:16 +1000, kelmo wrote:
Soeren Sonnenburg wrote:
On Fri, 2006-07-14 at 21:09 +1000, Kel Modderman wrote:
reopen 372208
|retitle |372208 Orinoco and wpa_supplicant not working with WEP
thanks
Hi,
I have a bad feeling about
Marco Nenciarini wrote:
Package: madwifi-source
Version: 0.svnr1679.0.9.1-1
Severity: important
This is not from debian, but from the staging repository.
madwifi-source cannot be built against kernel compiled with gcc-4.1
because it is more pedantic and -Werror option is passed to
Hi again,
I'd like to come up with a far more functional patch, that would allow
hostapd daemons to be initialised for multiple configuration files.
Please consider the already attached patch as bogus and not worth applying.
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Package: hostapd
Version: 1:0.5.3-1
Severity: wishlist
Tags: patch
The attached patch would allow the use of a hostapd.conf file !=
/etc/hostapd/hostapd.conf
It is configurable via the /etc/default/hostapd file.
The patch applies on top of the one attached to #376327.
Thanks, Kel.
-- System
Package: ndiswrapper-source
Version: 1.18-1
Severity: wishlist
Tags: patch
It'd be nice to make use of the now enhanced dh_installmodules rather
than rely on the handcrafted postinst.modules.in (#301424)
Attached is the trivial change to make that happen, however I've omitted
the changes to bump
Benjamin Leipold wrote:
Package: wpa_supplicant
Severity: wishlist
Since kernel 2.6.15 (i think so), the Intel Pro Wireless 2200
must be accessed via the wext driver. The man page doesn't mention
this fact.
Hi Benjamin,
The very first entry in the
Reinhard Tartler wrote:
On Tue, Jul 04, 2006 at 05:26:40AM +0200, Jacobo221 wrote:
init_wpa_supplicant() in /etc/network/if-pre-up.d/wpasupplicant should
not default to wired when $IFACE isn't in /proc/net/wireless'
contents because the first time the interface is set up after a boot
$IFACE
Daniel Huhardeaux wrote:
Kel Modderman wrote:
Daniel Huhardeaux wrote:
Kel Modderman wrote:
daniel huhardeaux wrote:
Package: wpasupplicant
Version: 0.4.8-2
Severity: minor
In the ifupdown script the VERBOSITY variable is not initialized.
A good feature would be to have a wpa-verbosity
(0
Jason Lunz wrote:
Package: wpasupplicant
Version: 0.5.4-1
Severity: minor
Tags: patch
This patch silences a minor shell error when running 'wpa_action iface
stop' in some cases.
Thanks, Jason.
This hack was already removed in current svn, and set -e was used to
report true exit status.
Elimar Riesebieter wrote:
On Thu, 15 Jun 2006 the mental interface of
Elimar Riesebieter told:
Package: madwifi-source
Version: 0.svnr1644.0.9.0-1
Severity: important
[...]
There are no news with madwifi-0.9.1
combined with wpa-supplicant 0.5.4. Are there any actions on this
bug?
Reinhard Tartler wrote:
Package: wpasupplicant
Version: 0.4.8-1
Severity: minor
forwarding bug from
https://launchpad.net/distros/ubuntu/+source/wpasupplicant/+bug/51493:
the script /etc/wpa_supplicant/ifupdown.sh uses the command env. Or this
command is in /usr/bin which might be not
Marc Haber wrote:
On Fri, Jun 30, 2006 at 01:04:59PM +0200, Marc Haber wrote:
I am going to try wpa-ap-scan 2 asap.
Successfully so. Association now happens instantly. Thanks for your
assistance.
Hey, that's great to hear!
I now have two proposals.
(1)
The documentation should
Package: rt2500-source
Version: 1.1.0+cvs20060420-3
Severity: wishlist
The rt2x00 project recently announced new legacy driver releases.
Latest BETA rt2500 driver: v1.1.0-b4, 20 June 2006
There are mostly a bunch of minor/trivial changesets since the last
snapshot was taken for debian
Package: hostapd
Version: 1:0.5.3-1
Severity: wishlist
Tags: patch
Attached patch uses lsb-base init functions library to enhance the
current hostapd init script.
A summary of changes:
* INIT INFO block as per LSB specs, containing description, runlevel
and should-start service information.
Marc Haber wrote:
On Mon, May 29, 2006 at 07:05:22AM +1000, Kel Modderman wrote:
Have you attempted using different ap_scan and scan_ssid values as
described in /usr/share/doc/wpasupplicant/examples/wpa_supplicant.conf.gz ?
As I am not using wpa_supplicant.conf but /etc/network
Marc Haber wrote:
On Fri, Jun 30, 2006 at 08:37:40PM +1000, Kel Modderman wrote:
Marc Haber wrote:
On Mon, May 29, 2006 at 07:05:22AM +1000, Kel Modderman wrote:
Have you attempted using different ap_scan and scan_ssid values as
described in /usr/share/doc/wpasupplicant
Kel Modderman wrote:
Marc Haber wrote:
On Fri, Jun 30, 2006 at 08:37:40PM +1000, Kel Modderman wrote:
Marc Haber wrote:
On Mon, May 29, 2006 at 07:05:22AM +1000, Kel Modderman wrote:
Have you attempted using different ap_scan and scan_ssid values as
described in
/usr/share/doc
Eric Lavarde wrote:
Package: madwifi
Severity: wishlist
Hi,
before migrating from Marlow's packages (http://debian.marlow.dk/) to
the ones from non-free, I really hesitated a long time because it was
not clear to me what the relation between the both is: they are named
exactly the same, but
Jason Lunz wrote:
Package: wpasupplicant
Version: 0.5.3+20060522-3
Severity: minor
Tags: patch
When wpa-conf (or wpa-roam) is used in /etc/network/interfaces, a call
to sed scans the given config file for the ctrl_interface. If it isn't
found, the WPA_SUP_CONF variable is overridden, dropping
Hi Reinhard
I am fine if you feel that this package needs more testing for a while,
however, I would like to point out what small problems occur if we roll
back to the 0.4 series of wpa_supplicant upstream:
* non-backwards compatible wpa_supplicant.conf options may disrupt
the end
Reinhard Tartler wrote:
Madwifi will eventually propagate to testing, and the wpa_supplicant
version in same archive will not support it.
You mean Version 0.svnr1644.0.9.0-2? Perhaps we can coordinate
transition of the two packages? On the other hand, we can tell users to
install
Modestas Vainius wrote:
In my opinion, `ifdown wlan0` (without =id_str) should do what `wpa_action
wlan0 stop` does now, i.e. bring current logical network (if wpa_supplicant
connected to any) down and kill wpa_supplicant friends.
This is quite impossible for me to provide via ifdown, I
Package: madwifi-source
Version: 0.svnr1644.0.9.0-2
Severity: normal
Due to http://madwifi.org/ticket/694, a svn checkout was used instead of
an exported source tree (or upstream supplied snapshot). This causes the
svnversion: Makefile target of madwifi to call svnversion (provided by
subversion)
Hi,
Just a follow up to this ticket to mention that this idea has been
extended in implemented in the current package. It takes the form of a
wpa_action shell script, and is described by the wpa_action(8)
manpage, http://users.tpg.com.au/sigm/misc/pkg-wpa/wpa_action.html
Comments and
Hi,
I sent some patches to upstream mailing list for consideration, one of
them describes the -g option in the wpa_supplicant manpage source:
http://lists.shmoo.com/pipermail/hostap/2006-June/013466.html
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
martin f krafft wrote:
Package: wpasupplicant
Version: 0.4.9-1
Severity: wishlist
I see little point in wpa_passphrase in /sbin. Please move it to
/bin or even /usr/bin.
The change has been made, but I'd rather think that wpa_passphrase makes
more point being in /usr/bin rather than
Elimar Riesebieter wrote:
Package: madwifi-source
Version: 0.svnr1644.0.9.0-1
Severity: important
I've got the following oops configuring ath0 on my powerbook (PPC architecture):
Jun 15 15:31:52 localhost kernel: Unable to handle kernel paging request for
data at address 0x003e005e
Jun 15
Mohammed Adnène Trojette wrote:
On Tue, Jun 13, 2006, Kel Modderman wrote:
Hi Mohammed,
Is this happening with latest versions (0.4.9 or 0.5.3 from experimental) ?
It works when I run
wpa_supplicant -c /etc/wpa_supplicant.conf -Dwext -dd -i eth1
where
/etc/wpa_supplicant.conf
Modestas Vainius wrote:
Package: wpasupplicant
Version: 0.5.3+20060522-2
Severity: wishlist
Hello,
In my opinion, `ifdown wlan0` (without =id_str) should do what `wpa_action
wlan0 stop` does now, i.e. bring current logical network (if wpa_supplicant
connected to any) down and kill
Modestas Vainius wrote:
Package: wpasupplicant
Version: 0.5.3+20060522-2
Severity: important
Tags: patch
Hello,
/sbin/wpa_action attempts to access /etc/network/ifstate file which does not
exist. A correct path is /etc/network/run/ifstate. The attached patch
fixes this.
Hi and thanks.
Modestas Vainius wrote:
2006 m. birelis 13 d., antradienis 15:05, ju-s rae.te:
I will try to work on that. It was planned but difficult to implement
cleanly.
Great.
I did hint to the manpage, I think . . . Help is always welcome too :-)
Yeah, you did. Just noticed while
[EMAIL PROTECTED] wrote:
I couldn't get it to set the SSID either.
The line
$WPA_CLI_BIN -p $WPA_COMMON_CTRL_IFACE -i $IFACE \
set_network $NW_ID ssid \$IF_WPA_SSID\ $TO_NULL
is supposed to set it, but doesn't work. If I remove the extra,
backslash escaped, quotes, so that it's just
Hi Mohammed,
Is this happening with latest versions (0.4.9 or 0.5.3 from experimental) ?
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Kel Modderman wrote:
Have you attempted using different ap_scan and scan_ssid values as
described in
/usr/share/doc/wpasupplicant/examples/wpa_supplicant.conf.gz ?
Thanks, Kel.
Any news? Latest versions still causing problems in this regard?
Kel.
--
To UNSUBSCRIBE, email to [EMAIL
Olivier Berger wrote:
Package: wpasupplicant
Version: 0.4.8-4
Severity: wishlist
Option -g is not documented in manpage.
Only wpa_supplicant --help says :
-g = global ctrl_interface
There are quite a few things missing from the manpages, I think.
I plan to send a few updates upstream for
severity 372208 wishlist
Soeren Sonnenburg wrote:
Package: wpasupplicant
Version: 0.5.3+20060522-1
If these patches are for the development version of wpa_supplicant,
should they not be merged into upstream CVS, so that next time I take a
snapshot, there is no need to carry along a large
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
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
Reinhard Tartler wrote:
On Fri, Jun 09, 2006 at 06:19:08PM +1000, Kel Modderman wrote:
If these patches are for the development version of wpa_supplicant,
should they not be merged into upstream CVS, so that next time I take a
snapshot, there is no need to carry along a large patch series
Soeren Sonnenburg wrote:
On Fri, 2006-06-09 at 10:48 +0200, Reinhard Tartler wrote:
On Fri, Jun 09, 2006 at 06:19:08PM +1000, Kel Modderman wrote:
If these patches are for the development version of wpa_supplicant,
should they not be merged into upstream CVS, so that next time I take
Soeren Sonnenburg wrote:
On Fri, 2006-06-09 at 19:50 +1000, Kel Modderman wrote:
Soeren Sonnenburg wrote:
On Fri, 2006-06-09 at 10:48 +0200, Reinhard Tartler wrote:
On Fri, Jun 09, 2006 at 06:19:08PM +1000, Kel Modderman wrote:
[...]
Soeren,
I do not object
Soeren,
I have uploaded a snapshot of pkg-wpa svn (tagged as UNRELEASED). It is
from the experimental branch and contains the wep-key-fix.
http://users.tpg.com.au/sigm/misc/pkg-wpa/
This snapshot also contains a huge update to ifupdown.sh, if anyone can
please take a look at those changes,
Hi Gregor,
The current wpasupplicant in experimental supports madwifi-ng.
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Have you attempted using different ap_scan and scan_ssid values as
described in /usr/share/doc/wpasupplicant/examples/wpa_supplicant.conf.gz ?
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Mohammed Adnène Trojette wrote:
Package: wpasupplicant
Version: 0.4.8-4
Severity: important
Hi,
this is a short time (around two weeks) since I do not manage to have
wpasupplicant work correctly through my /etc/network/interfaces
configuration.
Here it is:
| auto eth1
| iface eth1
Marc Haber wrote:
Adding wpa-wep-tx-keyidx 0 didn't help. Still takes like five minutes
before wpa_supplicant bothers to configure the key into the network
interface.
After doing ifup eth1=-wlan-some-site and the dhcp client timing out,
just waiting will make the interface associate eventually.
Mohammed Adnène Trojette wrote:
On Sat, May 27, 2006, Kel Modderman wrote:
Can I please see the output of ifup --verbose eth1 ?
Here it is:
| Configuring interface eth1=eth1 (inet)
| run-parts --verbose /etc/network/if-pre-up.d
| run-parts: executing /etc/network/if-pre
Marc Haber wrote:
On Sat, May 27, 2006 at 06:12:22PM +1000, Kel Modderman wrote:
Marc Haber wrote:
Adding wpa-wep-tx-keyidx 0 didn't help. Still takes like five minutes
before wpa_supplicant bothers to configure the key into the network
interface.
After doing ifup eth1=-wlan-some-site
Mohammed Adnène Trojette wrote:
On Sat, May 27, 2006, Kel Modderman wrote:
Everything seems okay there.
In your manual debugging attempts in the wpa_cli console, turn the
debugging on with 'level 0' or so, and see if there is a reason for
those constant de-association events.
When
Mohammed Adnène Trojette wrote:
On Sun, May 28, 2006, Kel Modderman wrote:
What wifi module and module version are you using?
I am using ipw2200
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.1.2
ipw2200: Copyright(c) 2003-2006 Intel Corporation
ipw2200: Detected Intel
Mohammed Adnène Trojette wrote:
On Sun, May 28, 2006, Kel Modderman wrote:
Please use:
wpa-passphrase myplaintextpsk
instead of wpa-psk, which is for hex strings.
Currently there is no way for ifupdown to differentiate hex strings from
plaintext, therefore we use a slightly different
Marc Haber wrote:
On Thu, May 25, 2006 at 06:59:54AM +1000, Kel Modderman wrote:
Thanks, I will apply something similar, but you can bet I won't be
echo'ing the psk at all . . .
I have thought about that and have settled for echoing it since
ifupdown can only be invoked by root
Marc Haber wrote:
Package: wpasupplicant
Severity: normal
Hi,
one of my networks is still WEP protected and has its SSID hidden. My
configuration:
iface wlan-some-site inet dhcp
wpa-driver wext
wpa-ssid some-ssid
wpa-key-mgmt NONE
wpa-wep-key0 deleted
Marc Haber wrote:
Package: wpasupplicant
Severity: wishlist
Tags: patch
Hi,
the attached patch improved debug output of the if-pre-up script.
Thanks, I will apply something similar, but you can bet I won't be
echo'ing the psk at all . . .
Thanks, Kel.
--
To UNSUBSCRIBE, email to
martin f krafft wrote:
Package: madwifi-source
Version: 0.svn20060207-5
Severity: important
The generated modules packages do not contain the changelog file.
Please change that as it is policy and should be done even though
the packages are not official packages.
Thanks you for spotting
Hi Le_Vert,
I know it is a bit too late, but I thought I'd just let you know that
spcaview has been prepared a long time ago at this location:
http://svn.debian.org/wsvn/pkg-spca5xx/spcaview/
Maybe there are some things in there that could help improve your
packaging of it.
Thanks, Kel.
Aurelien Jarno wrote:
Looks like Aurelien either said yes silently or already had a
package of his own. Either way rt2570 is in the NEW queue.
It's seems one message never get out of my SMTP server. So yes, there
is now a package in the NEW queue to support the rt2570 chip. It is
however
Arjan Oosting wrote:
Package: wpasupplicant
Version: 0.5.3-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I have just upgraded wpasupplicant to the version in experimental to
give it a try, but it fails to run and gives the following error
message:
Failed to register
Reinhard Tartler wrote:
We are talking here only about the cornercase of some random custom
scripts, which start wpa_supplicant using /etc/wpa_supplicant.conf
You mean we should leave 'zombie' files around on the filesystem on
package upgrades? Wouldn't that violate Policy?
And this also
Gregor Jasny wrote:
Package: wpasupplicant
Version: 0.5.2-3
Severity: wishlist
Tags: patch
Hi,
As long as madwifi-ng does not support wext, it would be nice if
wpa_supplicant would support madwifi-old and madwifi-ng.
I've attached two patches:
15_madwifing_1531_includes.dpatch
This are the
Ognyan Kulev wrote:
In /usr/share/doc/wpasupplicant/README.Debian.gz :
iface eth1 inet dhcp
wpa-conf managed
wpa-ap-scan 1
wpa-scan-ssid 1
# .. additional options for your setup, see README.modes
The line:
wpa-scan-ssid 1
should be:
Felix Homann wrote:
Justification: breaks the whole system
Please be a bit less dramatic with error descriptions/justifications ;-)
I tried upgrading wpasupplicant from 0.4.7-4 to 0.4.8-4 on a remote system
that is connected to the network via a WPA connection using wpa_supplicant.
The
Reinhard Tartler wrote:
On Tue, May 02, 2006 at 09:14:02PM +1000, Kel Modderman wrote:
Reason: /etc/wpa_suplicant.conf was renamed without warning.
Solution: Don't rename /etc/wpa_supplicant.conf on upgrade.
Okay, I can agree with this conclusion, somewhat. We are not supplying
Reinhard Tartler wrote:
On Tue, May 02, 2006 at 09:34:31PM +1000, Kel Modderman wrote:
We could surely keep the conffile in place, but would this really fix
the issue?
If you were invoking wpa_supplicant by an own script, pre-up or
manually, and you expected wpa_supplicant.conf
Felix Homann wrote:
And just in case Reinhard did not understand: If you
leave /etc/wpa_supplicant.conf in place on upgrades I regard the issue I
reported in Bug#365613 as fixed!
Clarification: only leave /etc/wpa_supplicant alone if its been edited,
remove the file if it has not changed
Reinhard Tartler wrote:
Since this issue won't break the system, but 'only' the wireless network
connection (which is grave enough in some cases), I really don't think
that 'critical' is appropriate. But thats certainly subject to personal
opinion.
I still think that this is kind of debconf
Sam Hocevar (Debian packages) wrote:
Package: wpasupplicant
Version: 0.4.8-3
Severity: wishlist
Maybe the configuration parser could be less strict. The following
for instance is invalid, just because of the spaces around =:
network = {
ssid = mynetwork
psk = wootwoot
}
Having
Reinhard Tartler wrote:
On Sun, Apr 30, 2006 at 08:07:12PM +0200, Elmar Hoffmann wrote:
when using an action script via wpa-action together with
wpa-action-timeout 0 in /etc/network/interfaces,
/etc/wpa_supplicant/ifupdown.sh busy loops as the continue in the test
for 0 timeout also skips
Celejar wrote:
I fiddled with 'iwconfig' a bit more and discovered that the 'repeater'and
'secondary' modes also don't seem to be supported. Here's a suggestion for a
note to acknowledge the issue:
Note: This version of the driver implements the Ad-Hoc, Managed (station /
client), Master
Gregor Jasny wrote:
Package: wpasupplicant
Version: 0.5.2-3
Severity: wishlist
Tags: patch
Hi,
As long as madwifi-ng does not support wext, it would be nice if
wpa_supplicant would support madwifi-old and madwifi-ng.
madwifi supports wext as of r1499.
http://madwifi.org/changeset/1499
Gregor Jasny wrote:
On Thursday 27 April 2006 13:34, Kel Modderman wrote:
madwifi supports wext as of r1499.
I've tried vanilla 2.6.16.11 + madwifi-ng r1531. The suppplicant is neither
working in wext mode nor in madwifi(ng). What revision of -ng are you using
with wext mode
Hi,
I suspect this problem may be stopping static wep keys from working
properly with the wext backend:
http://hostap.epitest.fi/bugz/show_bug.cgi?id=140
The patch has recently been added to the packages in pkg-wpa svn, any
testers please let us now if it corrects the issue.
Thanks, Kel.
celejar wrote:
Package: madwifi-source
Version: 0.svn20060207-4
Severity: normal
I am using madwifi with an Atheros AR5212 802.11abg (rev 01). 'ifdown
ath0' gives the following error:
Error for wireless request Set Mode (8B06) :
SET failed on device ath0 ; Invalid argument.
The same error
Matt Brown wrote:
Kel Modderman wrote:
Ok, thanks for reporting this issue (and sorry for a late reply!).
Could you please suggest some text for inclusion in the docs? (if not I
guess I could think of something :-) )
I did look into this the other day just to verify that it wasn't
celejar wrote:
Package: madwifi-source
Version: 0.svn20060207-4
Severity: normal
I am using madwifi with an Atheros AR5212 802.11abg (rev 01). 'ifdown
ath0' gives the following error:
Error for wireless request Set Mode (8B06) :
SET failed on device ath0 ; Invalid argument.
The same error
Celejar wrote:
On Wed, 26 Apr 2006 23:39:46 +1000
Kel Modderman [EMAIL PROTECTED] wrote:
Are you using madwifi-ng from upstream trunk? Or the version provided by
the debian package?
Kel.
Hi,
Thanks for the responses. I'm using the Debian package (as stated in the
original bug
Reinhard Tartler wrote:
retitle 304087 static wep broken on wext driver backend
tags 304087 pending
stop here
On Wed, Apr 26, 2006 at 07:09:38PM +1000, Kel Modderman wrote:
I suspect this problem may be stopping static wep keys from working
properly with the wext backend:
http
Robert Chéramy wrote:
Hi,
it would be great to have the rt2570 module supported under debian. I
used your package without big problems. The only thing I noticed is
the kernel complaining in dmesg:
rausb0 (WE) : Driver using old /proc/net/wireless support, please fix
driver !
Perhaps
Joerg Jaspert wrote:
Package: spca5xx-modules-i386
Severity: serious
Hi
Your binaries contain a line Recommends: spcacat, spcaview, spcaserv,
but Im unable to find those packages in Debian (or in Provides).
Thats against Policy 2.2.1.
Tags: wontfix
Despite the fact that madwifi-dev is non-free, it will soon be
disappearing from the madwifi packaging.
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Reinhard Tartler wrote:
On Wed, Apr 19, 2006 at 12:06:47AM +0200, Felix Homann wrote:
Since the radio is off, this attempt to bring the interface up will fail
but afterwards the inet line from the /bin/ip output will be gone.
Err, isn't this expected behavior?
Sure, but it
Reinhard Tartler wrote:
I cannot see that an important bug be brought up against a example only
script, also we cannot introduce the added depends of iproute,
especially if it is only required for an example only script, imo.
You're right. perhaps we should do that in the example action
Felix Homann wrote:
On Saturday 15 April 2006 18:12, Felix Homann wrote:
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
Here it fails saying:
No working leases in persistent database.
Exiting.
Failed to bring up wlan.
The device is not shown as up.
Felix Homann wrote:
Package: wpasupplicant
Version: 0.4.8-3
Severity: normal
If ifup fails on an interface configured to use wpasupplicant's managed
mode a wpa_supplicant process is left running in the background.
And the device is still marked as up in ifstate, so wpa_supplicant has
In pkg-wpa svn there is some workarounds for this, if you like, pull
wpasupplicant.ifupdown from there and test it.
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Kel Modderman wrote:
Aurelien Jarno wrote:
Package: madwifi
Version: 0.svn20060207-4 Severity: serious
Justification: no longer builds from source
Trying to builf madwifi version 0.svn20060207-4 on mipsel, I have seen
it now fails to build from source:
rm -rf debian/patched
/usr/bin/make
Aurelien Jarno wrote:
Package: madwifi
Version: 0.svn20060207-4
Severity: serious
Justification: no longer builds from source
Trying to builf madwifi version 0.svn20060207-4 on mipsel, I have seen
it now fails to build from source:
rm -rf debian/patched
/usr/bin/make -C tools clean
Hi,
I committed the following changeset to madwifi-ng svn:
http://madwifi.org/changeset/1499
This means this ticket is almost null and void, because madwifi-ng can
now use the wext backend to wpa_supplicant.
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
What would people say to providing an init daemon for wpasupplicant in a
separate binary package, for example, wparoamd or so?
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Kel Modderman wrote:
daniel huhardeaux wrote:
Package: wpasupplicant
Version: 0.4.8-2
Severity: normal
Using wpa-conf /path/to/wpasupplicant.conf in interfaces and having
options
there is working. Putting each option in interfaces file failed for 3
of them.
Here are outputs from
601 - 700 of 747 matches
Mail list logo
