All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Lippautz <michael.lippautz@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: wpa-supplicant 0.6.7 interface functions broken
Date: Fri, 02 Oct 2009 15:38:43 +0200	[thread overview]
Message-ID: <4AC60263.7000908@gmail.com> (raw)

Hej all,

Just posting here because someone on irc told me it would be faster than
using the bugtracker.

wpa-supplicant 0.6.7 (as currently prefered by angstrom) is quite
unusable when used in an automatic startup sequence
(/etc/network/interfaces and its up/down scripts). It works when used as
standalone program though.

The problem(s):
wpa-supplicant-0.6.7/functions.sh:
* The variables WPA_SUP_BIN and WPA_CLI_BIN are pointing nowhere.
* WPA_SUP_LOGFILE="syslog" doesn't work because the -s flag is not
understood.
* Generally the -f flag (used for logging)  is not understood by
wpa_supplicant. Although --help shows that it should be.

Solution(?):
Version 0.6.9 looks fine concerning the scripts. Although i don't know
whether the syslog/file-logging flag are supported.

The script 'files/ifupdown.sh' also looks a bit weird using something
like (line 95 cont.):

|PHASE="pre-up"
echo "WPA: Configuring Interface"
case "$PHASE" in
...
|
Has this package been restructured? It looks like that the commit
http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=6aea479c251050e0d13ae01b98c7a35da393b41f
did screw things up because the partially wrong config files were set up
for this recipe.

Couldn't test 0.6.9 so far but maybe it should be set as prefered
version in the configs.
Bug is online at: http://bugs.openembedded.org/show_bug.cgi?id=5323

Regards,
Michael




                 reply	other threads:[~2009-10-02 13:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4AC60263.7000908@gmail.com \
    --to=michael.lippautz@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.