> Package: wpasupplicant
> Version: 0.6.10-2
> Severity: minor
>
> /etc/wpa_supplicant/ifupdown.sh even starts if no wlan device is
> available (at least with ifconfig).
> imo that is not necessary, instead it should only start if an actual
> wlan device is ifup'd.
N
ia D-Bus service activation (note the -u option)
- most likely by NetworkManager. It was definitely not started via the
ifupdown shell scripts.
>
> do you have maybe more helpful comments?
Closing the bug report, it is invalid.
Kel.
--
To UNSUBSCRIBE, email to debian-bugs-dist-req
if the fstab-decode command
> didn't exists.
That would be a waste of text/time in my opinion.
Kel.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
release so far
Thanks, Kel.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> On Mon, 2010-04-12 at 17:36 +1000, Kel Modderman wrote:
>> On Monday 12 April 2010 09:55:53 Matthew W. S. Bell wrote:
>> > /etc/ifplug/action.d/action_wpa
>> Only modifies interfaces using the wpa-roam/wpa_action stuff, which is
>> exactly
>> its intention.
> On Fri, 2010-08-27 at 10:15 +0200, Uwe Kleine-König wrote:
>
>> This might be related to
>>
>> http://thread.gmane.org/gmane.linux.debian.devel.kernel/54624/
>>
>> ? Any news there?
>
> Kel Modderman seems to have disappeared, haven't hear
API is considered to be unstable by other developers
and therefore was not well advertised nor documented when it was
integrated.
I agree with the patch but will let others decide and further discuss what
makes the enable/disable feature worth hiding for longer.
Thanks, Kel.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Or is there a
> 0.7 version of wpasupplicant packaged somewhere already?
>
> If there's anyway I can help with the update, please let me know.
Use debcheckout to grab what is in our packaging VCS - build the package
from that checkout. Feedback welcome.
Kel.
--
To UNSUBSCRIBE, email
> Hello Kel,
>
> i've opened an rfp for bootchart2 and Petter Reinholdtsen informed me
> that you have already started to package it but run out of time. So
> what's the status of the packaging process? Do you have something online
> somewhere?
I experimented with an a
> Jonathan Nieder wrote:
>
> Kel, would it be appropriate for wpasupplicant to avoid a strict
> dependency on libpcsclite, by using dlopen() maybe? (Note I am only
> asking if it would be appropriate; the actual work would fall on the
> shoulders of people with an interest
eap=PEAP
> identity="u...@domain.tld"
> password="password"
> }
>
> I collected some debug output (using -dd) which contains logs from when
> I first connected to this network, after loosing the connection the first
> time
> and sev
> Hi!
>
> I encountered this bug, too.
>
>>How does changing /etc/init.d/rc with the below patch modify behaviour?
> No, Kel, nothing changed. Sorry.
When I observed boot after modifying the signal trap, CTRL-C did not truncate
startpar's execution of boot scripts in ru
e could provide some guidance about
building the Madwifi modules using kernel-package.
- Nate >>
Hi Nate,
Did you look at this effort to document the preferred process of
installing madwifi?
/usr/share/doc/madwifi-source/README.Debian
If that is not sufficient or could be rephra
.
Thanks, Kel.
Jean-Marc Ranger wrote:
Hi Kel,
Due to a recently arrived ipw2200, I'm loosing some interest in
continuing to package the adm8211 code for Debian. Are you interessed
in taking the ownership of the ITP bug in Debian ?
Jean-Marc
The in-kernel wireless code is too turbulent righ
e this instability.
This version of the driver is the most stable offering from the madwifi
project however it is still tagged as beta code, so it is known to cause
instability on some hardware.
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Graham wrote:
It may be related to the inability of this module to do background
scanning, or it could just be a plain old bug in the code. Try using the
basic wireless-tools and refrain from using the graphical apps, and see
if you can reproduce this instability.
Hi Kel,
I'm
Graham wrote:
Hi Kel,
Thank you for the links.
Well, in my experience these gui apps for configuring wireless on linux
really cause more trouble than they are worth.
Maybe, but:
1. You and I are fine with console based configuration tools, but many
people, including the owner of
nd co-maintain this in a similar
fashion I'd be more than happy to help out.
acer-acpi module may also be of interest. (for amd64 users)
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
to use some of my efforts, I'd love to help out.
Please contact me if you are interested.
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
hese efforts.
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Jean-Marc Ranger wrote:
Hi Kel,
I'll definitely have a look at what you did. I'm fairly new at Debian
packaging, so I sure can learn from what you did.
My version of the 20050620 driver is available at
http://web.ncf.ca/jmranger/adm8211/ if you're interessed to have a
h1 was
only meant to be an example of usage, which is well documented in "man
interfaces". So I'll fix that oversight, thanks.
"ifrename"; install it, read up on it. That is the tool that can
reliably map interfaces to permanent aliases by mac adress (and other
ident
Bill Wohler wrote:
Kel Modderman <[EMAIL PROTECTED]> wrote:
The README would better use ath0 as an example instead of eth1.
Yes, that would clear things up a lot. I thought perhaps I was missing
something. I have been using ath0.
"ifrename"; install i
tl32(gtkam:5245): Unknown cmd fd(6) cmd(c00c5512){00} arg(fff990c8) on
/proc/bus/usb/003/008
ciao, piem
Thanks for your time piem, very appreciated!
The upstream authours have been informed and are now investigating.
Thanks, Kel.
Hi,
By the time I saw this, there were a volley of replies to this first
attempt at contact.
Stephen Birch wrote:
>Hi Kel and Itay
>
>One of the packages I have been planning for Debian is the spca5xx
>package for which I filed a ITP some time back. Since I believed my
>NM
>them obsolete.
>
>The package itself was uploaded to Debian on Saturday night by Otavio
>who helped review and polish the code, thanks Otavio.
>
>The biggest thankyou must go to Kel who did an absolutely first class
>job of creating this package in the first place. I
Hey Otavio,
Otavio Salvador wrote:
>Kel Modderman <[EMAIL PROTECTED]> writes:
>
>
>
>>Otavio, I did some more thinking about the recent revamp of the rules,
>>and i'd like to propose a small optimisation.
>>
>>
>
>I agree with all this
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
aimed this very task. I was
waiting paiently for him to return from his break ;-).
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
, fine, but don't be surprised by a reopen if the
> problem returns. :-)
Please keep it open until you're satisfied it is really gone.
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
wpa_msg verbose "force disconnect to assure that
> wpa_cli receives CONNECTED event" $WPA_CLI_BIN -P $WPA_CLI_PIDFILE -i
> $WPA_IFACE disconnect fi
> fi
> }
>
I nack this patch and propose that -W should be documented and fixed (it seems
to work
emote ap
> ifconfig x.x.1.y ip and route sta vap, ping remote ap with > 20% packet
> loss maybe use airodump-ng with mon vap or dont
> ifdown ap vap, sta vap, mon vap, wifi0
> modprobe -r ath-pci
> ...
> should BUG() with reboot necessary
>
I think VAP technology is still jus
On Tuesday 23 January 2007 10:18, thomas schorpp wrote:
> Kel Modderman wrote:
> > Hi,
> >
> > On Sunday 07 January 2007 23:03, tom schorpp wrote:
> >>Package: madwifi-source
> >>Version: 1:0.9.2+r1842.20061207-2
> >>Severity: important
> >&g
On Tuesday 23 January 2007 20:31, Ivan Zaera Avellon wrote:
> Hi Kel:
>
> It's OK for me to send you my configuration, but I need to know what you
> want exactly.
Your configuration looks fine.
buzzard:/home/kel#
wpa_supplicant -W -ieth1 -Dwext -c/etc/wpa_supplicant/wpa_supp
ate to 0.6.0.
I am sorry, a 0.6.X based wpasupplicant will not be in debian's archive until
after all the ETCH release fuss is over. Hopefully an upload to experimental
can be arranged though.
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
d before 'upping' it
again.
Perhaps adding a `ifconfig $WPA_IFACE down' on the line before `ifconfig
$WPA_IFACE up' in if_post_down_up would help in cases where iproute is not
installed.
In any case, ifdown should not exit until it has fully completed what it had
to do with the int
> If I dont do this, i can see with iwconfig, the "a"-mode is more often
> scanned by iwconfig than the "b/g"-mode
Interesting observation. and no real surprise to the madwifi people I think.
Scanning and mode changing is currently a big pile of mess for those familia
t -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[SIOCGIWRANGE]: No such device
ioctl[SIOCGIF
idea for whitelisting the currently supported options without introducing a
huge maintenance burden (the scripts are aready quite large, at least one
other person has made that quite clear to me). For this reason, I changed the
bug title.
Perh
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]
Its features are also well described here:
http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Linux.Wireless.drivers.802.11b.html#Arlan802
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
disrepair right now, iirc), it can be applied to the
current package.
Not many hints from his reply as to what the actual cause was. I may as well
ask him directly . . .
Thanks, Kel.
[1] http://lists.shmoo.com/pipermail/hostap/2006-December/014761.html
--
To UNSUBSCRIBE, email to [EMAIL PROT
ore ending the session.
> The time-stamps appear to be pretty useless since wpa_cli seems to
> dump its output in big chunks at a time.
>
> In the hope that I didn't just send this report and it turns out to be
> a small dumb misconfiguration on my part,
The attached files sh
s too late to squeeze into
etch. Patch is attached. Taken from http://trac.edgewall.org/changeset/4038
Thanks, Kel.
diff -Nrup trac-0.10.orig/trac/web/modpython_frontend.py trac-0.10/trac/web/modpython_frontend.py
--- trac-0.10.orig/trac/web/modpython_frontend.py 2006-07-27 04:00:02.0
tags 396055 + patch
thanks
Hi,
Please apply attached patch.
I think svenl's post above does not apply here, I saw the two files in the
orig.tar.gz of current package with my own eyes.
Kel.
diff -u unionfs-1.3.20061029.0124+debian/debian/rules unionfs-1.3.20061029.0124+debian/debian/
drop a
> TARGET=powerpc-be-elf into the /usr/src/modules/madwifi/Makefile.inc and
> rebuild madwifi.tar.bz2, and re-execute m-a a-i madwifi.
I forwarded this onto the upstream mailing list this morning[1] where Pavel
Roskin stated[2] this is a problem he wants
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
used now. It is the successor of spca5xx.
Thanks, Kel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
#x27; where ethX is the interface name of your NIC.
Also, you can add 'wpa-maint-debug 1' to your interfaces stanza, and copy and
paste the very verbose output of 'ifup ethX'.
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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]
27; and possibly
add 'wpa-maint-debug 1' and give mass output from ifupdown.sh|functions.sh
(set -x).
Thanks, Kel.
Index: functions.sh
===
--- functions.sh (revision 774)
+++ functions.sh (working copy)
@@ -188,11 +188,6 @@
if [
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
he wpa_supplicant process.
So, we can remove wpa-ifupdown alltogether when the daemon is not killed
prematurely by sendsigs. Until then, we opted to at least put down the
interface cleanly.
Any better ideas?
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "un
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
am)
> patch 'patch 11_erroneous_manpage_ref.patch'.
It has been prepared in our SVN trunk, but will probably be uploaded
post-etch, unless there is a compelling reason to do otherwise.
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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
s shortly. NMU diff is attached
Thanks very much.
Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
d in pkg-spca5xx SVN on svn.d.o. A package will
be located at the following location until it is uploaded:
http://users.tpg.com.au/sigm/debian/pkg-spca5xx/gspca_01.00.11-1.dsc
Otavio, could you please review and upload this when time permits?
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL
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
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
'wlan1'
> ndiswrapper (wrap_procfs_add_ndis_device:364) wlan1 alread registred?
> usbcore: registred new driver ndiswrapper
>
> Any clue to resolve the issue ?
Perhaps check /etc/udev/rules.d/z25_persistent-net.rules for anomolies.
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
;I think that all information requested in #386090 was delivered. Is
>there still something missing?
If I knew all the answers, you would be the first to know.
Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: linux-modules-extra-2.6
Severity: wishlist
Tags: patch
Please remove spca5xx. The gspca module (from same author) supercedes
it. Patch to include gspca will be in a seperate report.
Thanks, Kel.
diff -Nrup linux-modules-extra-2.6-2.6.18.orig/defines
linux-modules-extra-2.6-2.6.18
Package: linux-modules-extra-2.6
Severity: wishlist
Tags: patch
Please consider including the gspca module. Patch attached (based on
same structure spca5xx used).
gspca module should enter testing anytime now.
Thanks, Kel.
diff -Nrup linux-modules-extra-2.6-2.6.18.orig/defines
linux-modules
Package: linux-modules-extra-2.6
Severity: wishlist
Tags: patch
Please consider including ndiswrapper. Patch attached, based on existing
support for spca5xx.
Thanks, Kel.
diff -Nrup linux-modules-extra-2.6-2.6.18.orig/defines
linux-modules-extra-2.6-2.6.18/defines
--- linux-modules-extra-2.6
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? C
l.
This smells and sounds like a feature request for ifupdown, as there is no way
to tell if ifupdown has failed at some stage, because it returns no signal to
existing children, or even scripts waiting to be called.
Perhaps this request should be reassigned to ifupdown package?
Thanks, Kel.
--
properly initialized to do scanning.
Curious, does a "ifconfig wlan0 up" achieve same result as invoking scan via
wpa_cli?
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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?
at report as blocker for this problem.
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
1], that are maintained and bugfixed by a bunch
of cool hackers, and are the origin of the existing rt2400, rt2500, rt2570
and rt2x00 source packages already in debian?
Thanks, Kel.
[1] http://rt2x00.serialmonkey.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
should not pass into testing, where 0.5.5-2 is working perfectly.
Further information will follow.
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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
wpa-wep-key0 ABACADAEAF
wpa-wep-tx-keyidx 0
And although the above is a theroetically supported configuration (via the
wpasupplicant/ifupdown scripts) I still question why you would prefer this
method for a statically defined network when wireless-tools is all that is
required.
om.au/sigm/debian/pkg-madwifi/
http://users.tpg.com.au/sigm/debian/pkg-madwifi/madwifi_0.9.2+r2085.20070207-1.dsc
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tags 410113 moreinfo
thanks
On Thursday 08 February 2007 05:28, Torsten Werner wrote:
> Package: gspca-source
> Version: 01.00.12-1
> Severity: normal
>
> Hi,
>
> it does not build any more.
>
Attach some build output/proof please?
# Build the module
/usr/bin/make
he annoying hang,
> when devicenames are changed.
>
> Could you please package it?
As you wish, sire.
http://users.tpg.com.au/sigm/debian/ndis/
http://users.tpg.com.au/sigm/debian/ndis/ndiswrapper_1.37-1.dsc
Please let me know how/if it works for you.
Thanks, Kel.
--
To UNSUBSCRIBE, email to
Hi Neil,
Is ndiswrapper still unstable for you? or #332668 still valid?
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi Graham,
I am wondering, is the current madwifi still unstable as hell for you? Is this
bug still valid?
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi Andrea,
Is this also the case with:
http://users.tpg.com.au/sigm/debian/ndis/
http://users.tpg.com.au/sigm/debian/ndis/ndiswrapper_1.37-1.dsc
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
networks. If you do not understand what this means, start reading the
wpa_supplicant.conf(5) manpage now.
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
; activation, but you can install the attached wpa_supplicant.service to
> /usr/share/dbus-1/service/ anyway, for applications that use that
> mechanism.
Added.
Thanks, Kel.
Index: debian/changelog
===
--- debian/changelog (revisio
On Sunday 04 March 2007 16:17, Kel Modderman wrote:
> Hi Michael,
>
> On Saturday 03 March 2007 12:22, Michael Biebl wrote:
> > Hi,
> >
> > you will also very likely need the attached patch:
> > Debian does not use pam_console but uses group membership to contro
On Sunday 04 March 2007 21:17, Kel Modderman wrote:
> On Sunday 04 March 2007 16:17, Kel Modderman wrote:
> > Hi Michael,
> >
> > On Saturday 03 March 2007 12:22, Michael Biebl wrote:
> > > Hi,
> > >
> > > you will also very likely need the attached
k people would complain if we start
> wpa_supplicant by default.
Ack. I would complain ;-)
> On the other hand, if wpa_action could be made to reuse the running
> D-Bus enabled wpa_supplicant instance instead of spawning its own copy
> (dunno if that would be possible/sensible) it
so tightly.
Cons:
We must maintain and provide a tiny package.
Package must go through NEW again.
My opinion; I tend to lean towards providing the seperate binary package,
wpasupplicant-dbus, even though it would be tiny. The benefits seem to
overwhelme the old package maintaina
- remove keys
This bug report provides insufficient information to be helpful.
How do you start wpa_supplicant? With what settings? What is _exact_ output of
wpa_supplicant messages? Used -d debug option?
Kel.
I will make wireless-tools a Suggests, but not more. wpasupplicant certainly
does not need iwconfig and co. to function, therefore it is no dependency.
Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Friday 15 December 2006 18:19, Henning Glawe wrote:
> On Fri, Dec 15, 2006 at 01:33:12PM +1000, Kel Modderman wrote:
> > > the problem is, at least in my case, that the link is _down_
> > > afterwards, so wpasupplicant is not able to scan further. This seems to
> > &
oblem,
please describe your WPA setup a bit more:
How is wpa_supplicant started?
What is the content of your wpa_supplicant configuration, and where is it
located?
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tes wpa_supplicant
# processes before networking is stopped causing each
# network interface authenticated via a wpa_supplicant
# daemon to be terminated abrubtly.
HTH.
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> HTH, Uwe.
>
> Uwe,
> Thanks for the patch, i will FIX the next revision. As a lesson, i know now
> M$ could be better with MS :)
> regards
Thanks for picking that up already Michel. Funny bug ;-)
Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Sunday 01 April 2007 19:52, Bernhard wrote:
> Hello, Kel
>
> On my system, the WPA Supplicant is started manually in /etc/interfaces.
> My configuration of the network interface is shown in the following lines:
>iface eth2 inet dhcp
>pre-up wpa_supplicant -iet
omething the wpasupplicant package needs to provide in addition to just
supporting the dbus interface?
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
our problem, I cannot even make any
good changes or even suggestions about what you can do right now to make your
wifi equipment work in linux, other than ndiswrapper.
Thanks, Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
at to do.
That is just common sense anyway ;-)
Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
gt; make[4]: Leaving directory `/usr/src/linux-2.6.20.6'
> make[3]: *** [default] Error 2
> make[3]: Leaving directory `/usr/src/modules/ndiswrapper'
> make[2]: *** [binary-modules] Error 2
> make[2]: Leaving directory `/usr/src/modules/ndiswrapper'
> make[1]: *** [kdist_build] Error 2
> -
Then use the version from sid/unstable.
Kel.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
sage bus
> configuration file So I have done a "grep -ir netdev /etc/*" and I found
> that /etc/dbus-1/system.d/wpa_supplicant.conf have a reference to this
> group.
>
> So I don't known if this bug is a wpasupplicant bug or dbus bug...
wpasupplicant may provide that file,
On Friday 13 April 2007 23:07, Bernhard wrote:
> Hello, Kel
>
>
> I have changed my configuration in /etc/network/interfaces.
> The modified network configuration is in the attachement.
>
> After reboot, i have started the wpa supplicant in a root terminal:
>wpa_suppl
1 - 100 of 768 matches
Mail list logo
