[gobolinux-users] configuration internet access

[Lucas C. Villa Real]

On 2/2/07, Carlo Calica <carlo at calica.com> wrote:
> Improving the network boot scripts for wireless is on my todo list.
> I'm pretty lucky that running dhcpcd on wlan0 just works for me.  I
> even have multiple APs and it has always chosen the one I want.
>
> I have a few questions.  First, the device needs to be up before
> setting essid?  Second, how long of a wait between setting essid and
> running dhcpcd?  Does increasing the dhcp timeout (dhcpcd -t # -h
> hostname rausb0) help at all?
>
> Adding iwconfig to NetworkOptions isn't a good idea.  Best way is to
> define some variables in NetworkOptions (say rausb0_WifiEssid and
> rausb0_WifiKey or maybe Wireless instead of Wifi, suggestions?)  Then
> add a function WirelessInterface() to Network task
> (/P/BootScripts/C/R/Tasks/Network) that calls iwconfig based on the
> variables.  Call WirelessInterface from NetworkInterface if either
> vars exist.  Anyone see a problem with that plan?

I also prefer to use a WirelessInterface() network task. However, I'd
modify /P/BootScripts/C/R/Tasks/Network in order to simply call
WirelessInterface, which would live in the Wireless-Tools package
then. Updating the Wireless-Tools package seems to be better than
touching BootScripts.

> I'd also like to create ifup and ifdown scripts as well.  Lucas, where
> should those live?

Aren't StartTask/StopTask WirelessInterface enough? Given that
currently one can use "StartTask Network <interface>", I'd just alias
ifup="StartTask Network" / ifdown="StopTask Network" instead, putting
these in some Environment file (Scripts seems to be a good candidate).

-- 
Lucas
powered by /dev/dsp