I noticed this bug a while ago and immediately though it was suggesting
to do a bad thing.
The fact that wpa_supplicant itself scans for networks and upon finding
them attaches to them, leads to that interfaces gets brought up because
of wpa_supplicant.
Implementing what is suggested would lead to an infinite loop if I not
misunderstand completely?
host# ifup eth0
[wpa_supplicant gets started] <-
|
[wpa_supplicant brings up eth0] ---
Maybe this will not be a problem in the most simple case, (Given that
the bug submitter had a working patch) but what happens when network
configuration starts to get complicated? When there are "up"-commands in
/etc/network/interfaces?
Maybe the thing to do is to skip starting wpa_supplicant as a service
from /etc/init.d and instead use the hotplug system. I.e. #295445
I am not completely sure on how this would work, but my feeling is that
it would be more correct.
If, like the bug submitter, one would not wan't to use the wireless
interface one could simply make sure not to load the kernel module.
--
/Martin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
