wpa_supplicant 1.0 fails to execute the 'up' routines.
gustav.schaffter at gmail.com
Mon Feb 3 17:05:38 EST 2014
Thanks for replying, Holger.
Your advice of using the -x was a good one. ;-)
I little bit more peekin' an' pokin' tells me that it's probably not a
problem within the /etc/network/if-up.d/wpasupplicant script. (BTW, this
'script' is a symbolic link to the 'real' script file
/etc/wpa_supplicant/ifupdown.sh which I believe is part of the
Anyway, AFAICU the problem lies somewhere in the ifupdown software.
start to understand that ifupdown may not be extremely well maintained
today. (My current version, 0.7.8, includes a copyright statement valid
It seems that Kyle Moffett, the author of the Blog entry is (was?) pretty
unhappy with the source code he finally found for ifupdown and that he
intended to do a 'Next Gen' version of ifupdown in Python. Unfortunately,
it looks like his initiative has stalled since about a year ago.
Wonder if I can somehow switch over to use the software in iproute2 instead
Anyway, Holger, thanks for your pointers. That was exactly what I needed.
P.S. Yes, Raspbian is a 'descendent' of Debian and built explicitly for the
Raspberry Pi computer.
On Mon, Feb 3, 2014 at 8:39 PM, Holger Schurig <holgerschurig at gmail.com>wrote:
> > Why do the 'up' echoes not show up?
> You're on Debian or it's lesser descendents (Ubuntu, laught). And
> their scripts are involved into your problem. It's not
> wpa_supplicant's fault what you see!
> Now, you can use "ifup -v" for verbose operation and/or put a "set -x"
> to get a trace near the beginning of /etc/network/if-up.d/<script>. It
> forgot the actual name, but <script> might probably be named
> wpasupplicant or similar.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the HostAP