Kel Modderman a écrit : > On Thursday 24 April 2008 00:39:07 giggzounet wrote: >> Kel Modderman a écrit : >>> Hi, >> Hi, >> >> thx for your quick answer! >> >>> Below you describe that you setup the "wpa-roam" scheme of wpasupplicant >>> package. When using this mode, _wpa_supplicant_ does the "link detection", >>> and >>> it notifies a listening wpa_cli daemon which in turn calls ifup/ifdown as >>> required. There is no use for ifplud in this mode, ifplugd will only get in >>> the >>> way. >>> >> Ok. I believe you that wpa_supplicant does the link detection and >> so...but how to tell the pc that wpa_supplicant must be launched when >> there is a possible connection...shall I write a script and launch it at >> boot ? > > You used the wpa-roam setup. Read the first paragraph of wpa_action(8) > (aka, "man wpa_action"), wpa_action is the script wpa_supplicant invokes > when using wpa-roam scheme. > > You set the master interface to be started auto or allow-hotplug in > /etc/network/interfaces like: > > allow-hotplug eth1 > iface eth1 inet manual > wpa-roam /etc/wpa_supplicant/conf > > iface default inet dhcp >
Ok, with allow-hotplug eth1 and ifplugd which does not handle of eth1 it works fine. Sorry...for that Thx again! >> I have read all the documentation of the package and I don't find >> anything on this subject : how is launched wpa_supplicant ? By me it is >> not launched. I must do it myself or enter "ifup eth1". >> >> I don't have any auto eth1...or something like that. >> In normal case when my pc is associated to an ap (for example an open >> network) ifplugd detects it and launch all. But in the case of ap using >> WPA, the pc doesn't associate automaticly...(perhaps there is an option...) >> >> Regards, >> Guillaume >> > > > Thanks, Kel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]