On Monday 22 January 2007 23:31, Maik Zumstrull wrote:
> As of now, for no reason I can see, the dropouts have stopped.
>
> I have neither changed my WPA and ifupdown configuration nor upgraded
> directly related packages; but still, the problem is gone. I assume
> this is due to some package updat
On Tuesday 09 January 2007 11:30, Kel Modderman wrote:
> > > Package: gspca-source
> > > Severity: wishlist
> > >
> > > Hi,
> > >
> > > Could you please package the 1.00.11 version of gspca which addds
> > > support for the zc03
On Wednesday 10 January 2007 06:12, Torsten Werner wrote:
> Hi,
>
>
> the bug report is now almost 90 days old. Do you plan to package the
> newer driver?
What, this one?
http://packages.debian.org/unstable/graphics/gspca-source
I guess #392759 can be closed . . .
Thanks, Kel.
--
To UNSUBSC
> > Package: gspca-source
> > Severity: wishlist
> >
> > Hi,
> >
> > Could you please package the 1.00.11 version of gspca which addds
> > support for the zc0321 chipsets?
>
> Sure. Will do so as soon as I can.
>
New upstream has been prepared in pkg-spca5xx SVN on svn.d.o. A package will
be loca
On Tuesday 26 December 2006 00:45, Junichi Uekawa wrote:
> Package: madwifi-source
> Version: 1:0.9.2+r1842.20061207-3
> Tags: patch
>
>
> Hi,
>
> I needed Linux 2.6.20 support; attached is a dpatch file for support.
>
Thanks. proski (Pavel Roskin) from upstream has claimed this very task. I was
On Sunday 31 December 2006 20:46, Samuel Mimram wrote:
> Package: gspca-source
> Severity: wishlist
>
> Hi,
>
> Could you please package the 1.00.11 version of gspca which addds
> support for the zc0321 chipsets?
Sure. Will do so as soon as I can.
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAI
Hi Maik,
On Tuesday 19 December 2006 21:45, Maik Zumstrull wrote:
> Package: wpasupplicant
> Version: 0.5.5-4
>
> When using wpa_supplicant in roaming mode on current Debian madwifi
> (see attachment: package-versions), the connection drops every thirty
> seconds or so.
MadWifi sucks a bit in cer
Hi,
> $ sudo wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant.conf -Dwext
> -ifoo0 ioctl[SIOCSIWPMKSA]: No such device
> ioctl[SIOCSIWMODE]: No such device
> Could not configure driver to use managed mode
> ioctl[SIOCGIFFLAGS]: No such device
> Could not set interface 'foo0' UP
> ioctl[SIOCGIWR
severity 403301 important
thanks
Hi Matteo,
Lowered severity, this does not meet grave bug criteria, IMHO. The package
works fine with supported devices and did not cause you any harm.
On Saturday 16 December 2006 11:50, Matteo Croce wrote:
> Package: wpasupplicant
> Version: 0.5.5-4
> Severity
On Monday 18 December 2006 07:39, Kel Modderman wrote:
>For this reason, I changed the bug title.
Didn't change it, becasue we may still yet have bright ideas ;-)
Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi Eduard,
On Saturday 16 December 2006 19:14, Eduard Bloch wrote:
> I just hat to swear once again about wpa_supplicant. After consolidation
> of my config some weeks ago I have kept "wpa-essid" directions there,
> and I assumed that they are correct because nothing complained. However,
> it does
Hi Eduard,
On Saturday 16 December 2006 18:37, Eduard Bloch wrote:
> I just discovered that current wpa_supplicant just segfaults if the
> specified interface is not available at all. Here the log and strace
> log, as executed by ifup:
>
> ifup eth1=kpax
> ioctl[SIOCSIWPMKSA]: No such device
> ioc
On Thursday 14 December 2006 22:19, Thomas Kallenberg wrote:
> Could this be a driver issue? I have the same problem and I'm using the
> madwifi-svn driver with wpasupplicant driver from unstable and
> network-manager from etch.
It is almost 100% likely to be an issue with the madwifi driver.
>
>
Hi Henning,
On Thursday 14 December 2006 20:33, Henning Glawe wrote:
> I have configured a roaming wpa configuration on my laptop using
>
> allow-hotplug wlan0
> iface wlan0 inet manual
> wpa-driver wext
> wpa-roam /etc/wpa_supplicant.conf
>
> in /etc/network/interfaces.
>
>
On Tuesday 12 December 2006 03:17, Thomas Esselen wrote:
> Package: wpasupplicant
> Version: 0.5.5-3
> Severity: important
>
> Hi,
>
> please upgrade to a 0.6.0 snapshot since EAP-TTLS and encrypted passwords
> for the tunnelled identity do not work with earlier releases:
>
> * fixed EAP-PE
On Saturday 09 December 2006 08:00, Matt Brown wrote:
> The fix described in the third post is incorrect. The backported patches
> applied in -3 have already reordered this part of the code so that it
> works correctly with madwifi.
>
> Unfortunately that backport missed the final component of the
On Saturday 09 December 2006 06:33, Gerrit Jan Baarda wrote:
> Op maandag 4 december 2006 02:49, schreef Kel Modderman:
> > Not very helpful ouput.
> >
> > Please show your /etc/network/interfaces configuration, and output
> > of 'ifup --verbose ethX' where e
On Wednesday 06 December 2006 12:20, Sam Morris wrote:
> Package: wpasupplicant
> Version: 0.5.6-0
> Severity: wishlist
>
> Version 0.5.6 is available. I built an updated package that seems to work
> fine by simply uupdating and then removing the (incorporated-upstream)
> patch 'patch 11_erroneous_
On Wednesday 06 December 2006 08:25, Przemyslaw Bruski wrote:
> Hi Kel,
>
> > Of course you are right. However, sendsigs is run at sequence number 20,
> > and it kills the wpa_supplicant process.
>
> Not anymore - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367944.
> The maintainers have moved
On Tuesday 05 December 2006 10:30, Przemyslaw Bruski wrote:
> Package: wpasupplicant
> Version: 0.5.5-2
> Severity: normal
>
> Currently, wpasupplicant is stopped before unmountnfs.sh script is run.
> This means that the network connection for NFS mounts may be gone by the
> time we try to unmount
On Friday 20 October 2006 20:41, Per Olofsson wrote:
> Kel Modderman:
> > Try something like:
> >
> > for x in $INTERFACES; do
> > if test -x /sbin/wpa_action && \
> > wpa_action $x check; then
> > wpa_action $x stop
&g
tags 401413 patch
thanks
Hi Torquil,
On Sunday 03 December 2006 21:19, Torquil Macdonald Sørensen wrote:
> I am trying to connect to a wired network with IEEE8021X authentication.
Ok. Something I admit to having very little experience with.
> Thus I have no wpa-ssid line in /etc/network/interfa
tags 401441 moreinfo
thanks
Errm, helps when i use the correct bug number for manipulating tags (and
luckily the tag i sent to the worng bug report was not unrelevant).
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tags 400752 moreinfo
thanks
On Monday 04 December 2006 01:33, Gerrit Jan Baarda wrote:
> Package: wpasupplicant
> Version: 0.5.5-2
> Severity: important
>
> After upgrading to 0.5.5-3 my laptop (IPW2200) will not cannect to the
> WLAN anymore.
>
> Here's the output of ifup/down:
>
>
> wpa_sup
On Sunday 03 December 2006 12:11, Andreas Henriksson wrote:
> I can't reproduce your problem with spca5xx-source. How are you
> building?
>
> I've tried building the spca5xx-source in an unstable amd64 pbuilder,
> then installing the spca5xx-source package and building that with
> module-assistant
On Friday 01 December 2006 21:30, Bastian Blank wrote:
> tags 400752 moreinfo
> thanks
>
> On Wed, Nov 29, 2006 at 01:17:20AM +1000, Kel Modderman wrote:
> > Package: linux-modules-extra-2.6
> > Severity: wishlist
> > Tags: patch
> >
> > Please consider in
debianized by Erik Rigtorp <[EMAIL PROTECTED]> on
+Mon, 23 Feb 2004 17:48:38 +0100.
+
+This package is currently maintained by Andres Salomon <[EMAIL PROTECTED]>
+and Kel Modderman <[EMAIL PROTECTED]> as of Oct. 2006.
+
+It was downloaded from http://ndiswrapper.sourceforge.net/
+
+Th
was debianized by Kel Modderman <[EMAIL PROTECTED]> on
+Wed, 4 Oct 2006 12:35:59 +1000.
+
+It was downloaded from http://mxhaard.free.fr/download.html
+
+Upstream Author: Michel Xhaard <[EMAIL PROTECTED]>
+
+The following files contain multiple copyright holders:
+
+decoder/gs
ephen Birch <[EMAIL PROTECTED]>
-Kel Modderman <[EMAIL PROTECTED]>
-Otavio Salvador <[EMAIL PROTECTED]>
-Itay Ben-Yaacov <[EMAIL PROTECTED]>
-
-This package is licenced under the terms of the GNU General Public Licence.
-
-On Debian systems, the complete text of the GNU GPL
On Sunday 26 November 2006 00:45, Marc Haber wrote:
>> This looks like it would be an artifact of the problem you reported as
>> #386090. I don't think I can answer this with any integrity without further
>> information, as addressed on your previous bug report.
>
>I think that all information re
On Saturday 25 November 2006 20:51, Fathi Boudra wrote:
> There's something new in dmesg like "changing interface name":
> ndiswrapper version 1.28 loaded (preempt=no,smp=yes)
> ndiswrapper: driver sis163u (TRENDnet,11/20/2005,5.1.1039.1050) loaded
> wlan0: vendor: 'Wireless Driver'
> wlan0: ethern
On Thursday 16 November 2006 05:38, Anand Kumria wrote:
> I use the ipw2200 driver (from 2.6.18-rc2) and with the following in
> /etc/network/interface I can intermittedly associate but never get an IP
> address allocation via DHCP:
>
> iface wlan0 inet dhcp
> wpa-ssid MyWiFi
> wpa-
On Tuesday 14 November 2006 08:43, Kel Modderman wrote:
> Package: hostapd
> Version: 1:0.5.5-3
> Severity: grave
> Justification: renders package unusable
>
> The subtle changes between 0.5.5-2 and 0.5.5-3 have exposed a
> showstopping bug when used in conjunction with c
Package: hostapd
Version: 1:0.5.5-3
Severity: grave
Justification: renders package unusable
The subtle changes between 0.5.5-2 and 0.5.5-3 have exposed a
showstopping bug when used in conjunction with certain madwifi driver
versions (specifically 0.9.2+r1784.20061027-1 currently in debian).
This
Hi Ian,
On Monday 13 November 2006 03:20, Ian MacDonald wrote:
> Package: madwifi-source
> Version: 1:0.9.2+r1784.20061027-1
> Severity: important
>
> The following is from the buildlog after executing #m-a a-i madwifi
>
> dh_testroot
> dh_clean
> /usr/bin/make -C /usr/src/modules/madwifi clean \
at is
+responsible for copying required upstream contents into debian module
+source tarball staging area.
+
+ -- Kel Modderman <[EMAIL PROTECTED]> Sun, 12 Nov 2006 12:21:59 +1000
+
unionfs (1.3.20061029.0124+debian-1) unstable; urgency=low
* New upstream snapshot:
Package: trac
Version: 0.10-3
Severity: normal
I was struck by a baffling problem described at
http://trac.edgewall.org/ticket/3984
Summary: it is impossible to attach anything to the trac system with the
combination of trac 0.10 and python 2.4.4. Attempting to do so would
cause the following err
On Thursday 02 November 2006 08:55, Piotr Roszatycki wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Piotr Roszatycki <[EMAIL PROTECTED]>
>
> * Package name: rt73
> Upstream author : Paul Lin <[EMAIL PROTECTED]>
> Version : 1.0.3.6
> * URL :
> http://www.ralinktech.
On Wednesday 01 November 2006 02:22, Michael Biebl wrote:
> See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=342887
>
> Maybe we should add #342887 as blocker for this bug?
Looks like that is exactly why you have problems, interesting (and damn
frustrating!). Please do add that report as
Hi,
This is causing wpasupplicant to FTBFS (wpagui requires libqt4-dev). I'd love
to do some finishing touches to wpasuppliant before etch, but cannot while
this is blocking it.
Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTE
On Monday 30 October 2006 11:50, Michael Biebl wrote:
> Package: wpasupplicant
> Version: 0.5.5-2
> Severity: normal
>
> I tried the new modes of wpa_supplicant using /e/n/i.
> Using "wpa-conf /path/to/config" works fine but unfortunately blocks the
> boot process. But when I use the new roaming mo
On Tuesday 17 October 2006 01:22, martin f krafft wrote:
> Package: wpasupplicant
> Version: 0.5.5-2
> Severity: normal
>
> If I use ifupdown integration, wpa_supplicant starts up nicely as
> expected. It associates with the AP and then dhclient (called by
> ifup) tries to get a lease. However, if
On Sunday 29 October 2006 13:31, Nathaniel W. Filardo wrote:
> According to http://madwifi.org/ticket/925 this is fixed in r1755.
Yeah, I was the one who tested and applied the patch.
Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PR
On Sunday 22 October 2006 16:21, Nathaniel Wesley Filardo wrote:
> Package: madwifi-source
> Version: 1:0.9.2+r1710.20060914-1
> Severity: important
>
>
> SVN version 1710 contains outdated ath_hal code which on an Acer Aspire
> 5100 as well as other laptops containing (recent?) spins of the chipse
On Wednesday 18 October 2006 04:22, Brad Sawatzky wrote:
> On Tue, 17 Oct 2006, Kel Modderman wrote:
> > On Tuesday 17 October 2006 05:23, Moritz Muehlenhoff wrote:
> > > severity 386227 grave
> > > thanks
> > >
> > > > Package: spca5xx-sou
On Tuesday 17 October 2006 05:23, Moritz Muehlenhoff wrote:
> severity 386227 grave
> thanks
>
> On Tue, Sep 05, 2006 at 11:54:29PM -0400, Brad Sawatzky wrote:
> > Package: spca5xx-source
> > Version: 20060501-1
> > Severity: important
> > Tags: patch
> >
> >
> > Some v4l header information got shu
On Sunday 15 October 2006 19:57, Reinhard Tartler wrote:
> Kel Modderman <[EMAIL PROTECTED]> writes:
> >> I think http://madwifi.org/ticket/671 may be related, but 'sudo iwconfig
> >> ath0 FAU-VPN' in another shell as suggested in that ticket didn't help
On Sunday 10 September 2006 00:30, Marc Haber wrote:
> On Sat, Sep 09, 2006 at 11:07:20AM +1000, Kel Modderman wrote:
> > On Thursday 07 September 2006 14:45, Marc Haber wrote:
> > > wpasupplicant waits 60 seconds for the interface to associate with a
> > > network bef
On Tuesday 19 September 2006 21:25, Marc Haber wrote:
> On Tue, Sep 19, 2006 at 09:22:41PM +1000, Kel Modderman wrote:
> > On Tuesday 19 September 2006 05:43, Marc Haber wrote:
> > > when trying to connect to an Apple AirPort Express which is configured
> > > to all
On Monday 09 October 2006 04:36, Per Olofsson wrote:
> > You mentioned that you gave it a go, did you have any preliminary code?
> > (I don't care if its ugly/non-working, it may give a hint to what is
> > required).
>
> I think something like this for the file
> /etc/acpi/suspend.d/55-down-interfa
Package: wnpp
Severity: wishlist
Owner: Debian spca5xx Maintainers <[EMAIL PROTECTED]>
* Package name: gspca
Version : 01.00.04
Upstream Author : Michel Xhaard <[EMAIL PROTECTED]>
* URL : http://mxhaard.free.fr/index.html
* License : GPL
Programming Lang: C
On Wednesday 04 October 2006 01:24, Per Olofsson wrote:
> Kel Modderman:
> > This ifdown/ifup is unrequired with nicely behaved modules (eg ipw2200),
> > as they can sustain a link via wpasupplicant during suspend/resume cycle.
>
> Ah, yes, I have such a card and that works.
On Tuesday 03 October 2006 23:39, Per Olofsson wrote:
> Package: wpasupplicant
> Version: 0.5.5-1
> Severity: normal
>
> wpasupplicant currently does not work very well with acpi-support,
> when suspending/resuming the system. The problem is that acpi-support
> does ifdown on all interfaces when su
Package: powersaved
Version: 0.14.0-2
Severity: wishlist
Currently, powersaved has ipw2200 in a suspend blacklist, and it is
removed from kernel space before suspend and reinserted after resume. I
believe this is needlessly causing headaches for the end user, as
ipw2200 has supported suspend/resum
On Tuesday 03 October 2006 11:46, Chip Salzenberg wrote:
> Package: madwifi-source
> Version: 1:0.9.2+r1710.20060914-1
> Severity: grave
> Justification: renders package unusable
>
> The drivers seem to build OK for kernel 2.6.16-2-686, but when I try to
> actually use them, I get a raft of "disagr
On Sunday 24 September 2006 23:28, ste wrote:
> Package: ndiswrapper-source
> Version: 1.23-1
> Severity: grave
> Justification: renders package unusable
IMHO, this is not grave, but lets not worry about arguing that point . . .
>
> Building this module fails on 2.6.17-1 and 2.6.17-2 giving me th
On Sunday 24 September 2006 01:20, Eddy Petrisor wrote:
> Package: madwifi-tools
> Version: 0.svnr1697.0.9.2-1
> Severity: wishlist
>
> Hello,
>
> If one uses module-assistant to build the madwifi module, it will fail
> since it depends on madwifi-tools, which is unavailable from the
> archive. Ple
On Saturday 23 September 2006 02:10, David Pearce wrote:
> Package: ndiswrapper-source
> Version: 1.23-1
>
> After compilation with m-a, the resulting debian package has a recommends
> for kernel-image-`uname -r` which is no longer the naming convention used
> for kernel packages - instead I think
On Tuesday 19 September 2006 05:43, Marc Haber wrote:
> Package: wpasupplicant
> Version: 0.5.4-5
> Severity: normal
>
> Hi,
>
> when trying to connect to an Apple AirPort Express which is configured
> to allow both WPA and WPA2, it is necessary to manually set group and
> pairwise to TKIP. Otherwi
On Thursday 14 September 2006 01:15, martin f krafft wrote:
> This just a FYI: after a day of not being able to associate,
> I restarted my router and then the association worked, even without
> the patch you told me to apply. I guess what this means is that it's
> probably not just the driver's fa
On Tuesday 12 September 2006 04:26, Reuben Thomas wrote:
> Package: wpasupplicant
> Version: 0.5.4-5
> Severity: normal
>
> I have a stanza in my /etc/network/interfaces:
>
> #auto eth0
> iface eth0 inet manual
> pre-up modprobe ipw2100
> wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
>
>
On Monday 11 September 2006 19:24, martin f krafft wrote:
> Package: madwifi-source
> Version: 0.svnr1697.0.9.2-1
> Severity: important
>
> Ever since I upgraded to the madwifi-ng driver, it's become mostly
> unusable. I am using the latest 2.6.17 kernel from unstable. From
> time to time I get it
On Tuesday 05 September 2006 19:07, Marc Haber wrote:
> Package: wpasupplicant
> Version: 0.5.4-5
> Severity: normal
>
> Hi,
>
> with the following wpa_supplicant.conf.local, wpasupplicant does not
> associate to unencrypted networks, such as public Hot-Spots:
>
> network={
> id_str="wlan-o
On Saturday 09 September 2006 05:02, Helge Kreutzmann wrote:
> Package: wpasupplicant
> Version: 0.5.4-5
> Severity: minor
> Tags: patch
>
> In README.Debian you write /usr/share/doc/wpasupplicant/README.modes
> while in fact the file is compressed, hence
> /usr/share/doc/wpasupplicant/README.modes
On Thursday 07 September 2006 14:45, Marc Haber wrote:
> Package: wpasupplicant
> Version: 0.5.4-5
> Severity: minor
>
> Hi,
>
> wpasupplicant waits 60 seconds for the interface to associate with a
> network before trying the next. How to control this timeout?
Do you use ap_scan=2 or so?
>
> The
On Tuesday 05 September 2006 19:10, Marc Haber wrote:
> Package: wpasupplicant
> Version: 0.5.4-5
> Severity: normal
>
> When I am trying to use a public hotspot, I need to associate to an
> unencrypted network. This does not seem to work after wpasupplicant
> was once started (as it happens automa
On Thursday 07 September 2006 17:37, Michel Xhaard wrote:
> Le Mercredi 6 Septembre 2006 05:54, Brad Sawatzky a écrit :
> > Package: spca5xx-source
> > Version: 20060501-1
> > Severity: important
> > Tags: patch
> >
> >
> > Some v4l header information got shuffled around in kernel 2.6.18. The
> >
On Wednesday 06 September 2006 05:24, Andreas Janssen wrote:
> The missing functions log_action_begin and log_action_end were
> introduced in lsb-base 3.0-6.
Ok, thanks. wpasupplicant packaging has been updated accordingly.
Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "
On Wednesday 06 September 2006 03:32, Andreas Janssen wrote:
> Package: hostapd
> Version: 1:0.5.5-1
> Severity: serious
> Justification: Policy 3.5
>
>
> hostapd 0.5.5 needs init script functions that are not available
> in older versions of lsb-base. Running a backport on Sarge
> results in:
>
>
On Sunday 03 September 2006 22:41, Loïc Minier wrote:
> Hi,
>
> On Fri, Sep 01, 2006, Carlos Moffat wrote:
> > Just to check, I tried madwifi-ng-{source,tools} r1587 from
> > snapshot.debian.net. That one didn't work either. I had to go back to
> > r1500 to be able to connect again. I hope
On Monday 04 September 2006 00:28, Carlos Moffat wrote:
> On Sun, 2006-09-03 at 16:06 +0200, Loïc Minier wrote:
> > Hi,
> >
> > On Sun, Sep 03, 2006, Carlos Moffat wrote:
> > > I have two interfaces coming up: wifi0 and ath0. Both are up, as far as
> > > I can tell. Both have the same name
Hi Loic and Aurel,
On Monday 21 August 2006 21:20, Loïc Minier wrote:
> On Mon, Aug 21, 2006, Kel Modderman wrote:
> > Loic contacted me on IRC with a proposal to split the tools into an own
> > source package that would enter contrib, and thus be autobuilt. Is this
> > som
On Monday 28 August 2006 00:29, Celejar wrote:
> Wireless card is Trendware TEW443-PI. Chipset is Atheros AR5212 802.11abg
> NIC (rev 01). pciid is 168c:0013. Kernel is 2.6.12-1-386. 'madwifi-source'
> is 0.svnr1697.0.9.2-1.
>
> 'modprobe ath_pci autocreate=ap'; here's dmesg:
> > ath_hal: 0.9.17.2
On Sunday 27 August 2006 13:47, Celejar wrote:
> I've upgraded hostapd to 1:0.5.4-1 and I'm still getting the same error.
>
> Celejar
Please provide detailed information about your setup. The initial report is
lacking any functional information.
Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECT
On Tuesday 22 August 2006 18:06, Reinhard Tartler wrote:
> Kel Modderman <[EMAIL PROTECTED]> writes:
> > On Monday 21 August 2006 00:02, Reinhard Tartler wrote:
> >> This of course fails if the interface is controlled by wpa-roam aka
> >> /sbin/wpa_action.
On Wednesday 23 August 2006 20:42, Kel Modderman wrote:
> >
> > I'm launching wpasupplicant as:
> > # wpa_supplicant -c /tmp/wpa_supplicant.conf -i eth1 -dd -D ipw
> >
> > Any ideia?
>
> Use -D wext, *not* -D ipw.
Any news?
Kel.
--
To UNSUBSCRIBE, ema
On Friday 25 August 2006 04:48, Yitzhak Grossman wrote:
> Package: hostapd
> Version: 1:0.5.3-1
> Severity: important
>
>
> My madwifi is uptodate (0.svnr1697.0.9.2-1), but hostapd fails with
> these messages:
>
> Flushing old station entries
> madwifi_sta_deauth: addr=ff:ff:ff:ff:ff:ff reason_code
On Tuesday 22 August 2006 07:07, Daniel R. wrote:
> Package: wpasupplicant
> Version: 0.5.4-5
> Severity: normal
>
> Hello,
>
> The file README.modes.gz in /usr/share/doc/wpasupplicant provides a
> deep explanation of the new roaming mode (using the "wpa-roam" tag in
> /etc/network/interfaces' wire
On Wednesday 23 August 2006 20:04, Rui Pedro Lopes wrote:
> Package: wpasupplicant
> Version: 0.5.4-5
> Severity: normal
>
> Hi,
>
> For some time now I've been unable to use wpasupplicant with IEEE802.1x. I
> tried it with both ipw2100 and ipw2200 boards and it allways complaints
> about "Failing
On Monday 21 August 2006 19:59, Aurelien Jarno wrote:
> As already proposed to Loïc, I can upload the binary for amd64. I am
> already doing it for mipsel and I am subscribed to the PTS so I know
> where there is a new version. However, if at some point I forget to
> build the new version, just pin
On Monday 21 August 2006 19:18, Loïc Minier wrote:
> On Mon, Aug 21, 2006, Kel Modderman wrote:
> > So it requires a binary upload? I have an amd64 box if there is anyway my
> > binaries can be signed and trusted.
>
> I am afraid I really can't sponsor binary uploads
On Monday 21 August 2006 19:05, Loïc Minier wrote:
> Hi,
>
> On Mon, Aug 21, 2006, Kel Modderman wrote:
> > Yes it is, and I cannot tell why (and not enough experience to Just
> > Know(tm).
> >
> > Loic, is non-free stuff selectively built? Or is th
On Sunday 20 August 2006 04:03, Vladimir Suplin wrote:
> The madwifi-modules depends on the madwifi-tools which is
> unavalable in Debian's archieves on amd64.
Yes it is, and I cannot tell why (and not enough experience to Just Know(tm).
Loic, is non-free stuff selectively built? Or is there a re
On Monday 21 August 2006 00:02, Reinhard Tartler wrote:
> Package: wpasupplicant
> Version: 0.5.4-2
> Severity: wishlist
>
> Hi Kel,
>
> while tuning my suspend and resume scripts, I noticed that acpi-support
> contains code like this in
> /etc/acpi-support/suspend.d/55-down-interfaces.sh
>
> # Fin
On Tuesday 15 August 2006 20:46, Reinhard Tartler wrote:
> Package: madwifi-source
> Version: 0.svnr1697.0.9.2-1
> Severity: important
>
> After suspending/resuming with uswsusp, I don't get any association with
> wpa_supplicant. Here is a log of an wpa_cli session:
>
seen it all too often :(
>
On Wednesday 16 August 2006 07:11, Pedro Celestino dos Reis Rodrigues wrote:
> Package: ndiswrapper
> Severity: important
>
> Hi
> After some time of operation (from 1 to 8 days for me), ndiswrapper hangs
> and no more wireless operations are allowed.
>
> My syslog looks like this
> .
> Aug 15
On Monday 14 August 2006 02:31, Daniel Baumann wrote:
> Kel Modderman wrote:
> > I notice some of my ipw3945 efforts have been mentioned in ITP's. I'd
> > love to see my efforts go directly into debian. I do not have the
> > hardware, only a fair idea of how a
Hi Steinar,
I notice some of my ipw3945 efforts have been mentioned in ITP's. I'd love to
see my efforts go directly into debian. I do not have the hardware, only a
fair idea of how all the ipw3945 pieces should go together, so I'd love to
hand off my work to an interested party with the hardwa
reassign 382650 madwifi
thanks
Reassigning this bug to madwifi (hopefully), reasons are below:
On Saturday 12 August 2006 23:58, Martin Ziegler wrote:
> Subject: wpasupplicant: "wpa-driver wext" does not work for madwifi
> Package: wpasupplicant
> Version: 0.5.4-5
> Severity: minor
>
> *** Please
On Saturday 12 August 2006 22:40, Eduard Bloch wrote:
> #include
>
> * Kel Modderman [Sat, Aug 12 2006, 07:39:31PM]:
> > Hi Eduard,
> >
> > > Then I decided to play with the tools mentioned in README.modes.gz, I
> > > used wpa_passphrase, passed my e
Hi Eduard,
On Thursday 10 August 2006 18:46, Eduard Bloch wrote:
> Package: wpasupplicant
> Version: 0.5.4-5
> Severity: normal
>
> Hello,
>
> I was using previous versions of wpasupplicant (before ifupdown
> integration) with a self-made conf file containing a preshared key.
> Relevant contents:
On Thursday 10 August 2006 04:17, Reinhard Tartler wrote:
> Christoph Biedl <[EMAIL PROTECTED]> writes:
> > If you agree:
> > * In postinst: Check whether /e/n/i permissions are 660 or tighter and
> > offer to fix them if required.
>
> I don't really agree here, as I don't see the necessity to bu
On Monday 07 August 2006 23:18, Debian Bug Tracking System wrote:
> It has been closed by Luis <[EMAIL PROTECTED]>.
>
> Their explanation is attached below. If this explanation is
> unsatisfactory and you have not received a better one in a separate
> message then please contact Luis <[EMAIL PROTE
On Monday 07 August 2006 04:43, Anders Ellenshøj Andersen wrote:
> Package: wpasupplicant
> Version: 0.5.4-2
> Severity: minor
>
>
> When starting wpasupplicant via ifup/down I noticed that wpa_supplicant is
> started with options -P and -C. I was not able to find these options in the
> man page.
On Saturday 05 August 2006 20:23, Marco Nenciarini wrote:
> Package: ndiswrapper-common
> Version: 1.21-1
> Severity: important
>
> If you have dash as /bin/sh you get this error
>
> debian:/home/mnencia# dash -x /usr/sbin/ndiswrapper
> + set -e
> + LATEST=
> + LATEST=/usr/sbin/ndiswrapper-[^b]*
>
Hi Junichi,
Thanks for the tips. I probably applied at least two of those patches to
upstream. Also see:
http://lists.alioth.debian.org/pipermail/pkg-madwifi-maintainers/2006-August/000349.html
http://svn.debian.org/wsvn/pkg-madwifi/unstable/
This problem will be fixed momentarily.
Thanks, K
Package: splashy
Version: 0.1.8.1-3
Severity: wishlist
Hi, splashy is great.
The Kanotix[0] Live-CD is developing a themeset, it will also have a
splashy theme. We'd love to use it on the live-cd too. This would
require the ability to manually increment the progress bar. Currently, I
can see no m
Package: ftp.debian.org
Severity: normal
spca5xx-modules-i386 has been replaced by the superior spca5xx-modules source
package, so please get rid of it.
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Monday 31 July 2006 23:27, Lennart Poettering wrote:
> Package: hostapd
> Version: 1:0.5.3-1
> Severity: wishlist
>
> Please consider setting the hostapd.conf access mode to 600 by default,
> because it might contain passwords if used in WPA-PSK mode.
Thanks! I completely agree.
Faidon, what
On Sunday 30 July 2006 10:34, infernix wrote:
> Kel Modderman wrote:
> > It breaks the dependency on a locally installed package, that has no
> > dependencies or control data? Please further convince me that this is
> > actually a problem in the packaging of this module
501 - 600 of 749 matches
Mail list logo
