On 3/6/07, Jonatan Liljedahl <[EMAIL PROTECTED]> wrote:
BTW, regarding wifi support at boot...

Would it be possible to have it try wired ethernet first and wifi if it
succeeds? Also, it would be lovely if it choosed the "best" essid
(fastest, highest signal strength, and open), or prefer specific ones if
the user has specified some in an array?

As I have it now on my laptop, I always do these things manually since I
use wired eth to my LAN and wifi when away. It would be cool if it "just
worked". =)


Sorry for the delay.  I've been waiting to add WPA support but I might
as well send what I have to the list as a preview and receive
comments.  Attached are revised Network task and a new WirelessConfig
task.  To associate a ESSID to an interface add
<interface>_WirelessESSID="ESSID" to /S/Settings/NetworkOptions.  To
use a WEP key add: <interface>_WirelessWEPKey="hexkey".  These options
are passed to iwconfig

Regarding wired eth; try netplug [1] or ifplugd [2].  For choosing a
dynamic wifi essid, I feel that belongs in a desktop helper applet (ie
kwifimanager) rather than the boot tasks.  Mainly because the essid
can change as a machine is moved from location to location.
If your essid is static, it makes sense for the boot tasks.  Using an
essid of "any" lets the kernel choose a suitable ap.  How the kernel
decides the most suitable I don't know.

[1] http://www.red-bean.com/~bos/
[2] http://0pointer.de/lennart/projects/ifplugd/

--
Carlo J. Calica

Attachment: Network
Description: Binary data

Attachment: WirelessConfig
Description: Binary data

_______________________________________________
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel

Reply via email to