Booting with AirPort on YDL 2.3

[Andrew Hodel]

Or you can do what I do,


if [ $(id -u) !=3D "0" ]; then
echo "You must be the superuser to run this script" >&2
exit 1

else
echo -n "Network Name > "
read network

        if [ $network =3D=3D "d" ]; then
        network=3D"2fa7e8"
        fi

sleep 1
echo "Probing Airport"
/sbin/modprobe airport

sleep 1
echo "Configuring Eth1 with Network Name $network"
/sbin/iwconfig eth1 essid "$network"

sleep 1
echo "Restarting Network Services"
/etc/rc.d/init.d/network restart

sleep 1
echo "Network Restarted with Eth1 Configured"
fi

And either run this script each time you start your computer, usind d for=
=20
default when you are at home, and putting in another network name when yo=
u=20
aren't at home.  This is good because you do not always use the same base=
=20
station, and you dont always need airport on.  You could modify this scri=
pt a=20
and start it automatically with rc.local.

Andrew Hodel

On Tuesday 01 October 2002 12:41, Jussi-Pekka Mantere wrote:
> Some tips on getting AirPort to load at startup before rc.local is run
> under YDL 2.3 (with 2.4.x kernel.)
>
> In the doc
> http://www.yellowdoglinux.com/support/solutions/ydl_general/
> airport24.shtml it is suggested that AirPort networking be loaded from
> /etc/rc.d/rc.local. This is not always optimal, as some services
> require networking to be up before rc.local is run.
>
> To bring up AirPort in the proper boot sequence, the following setup
> works:
>
> - load AirPort support in rc.modules:
>
> $ cat > /etc/rc.modules << EOF
> #! /bin/sh
>
> /sbin/modprobe airport
> EOF
>
> - make it executable:
>
> $ chmod a+x /etc/rc.modules
>
> - create the interface config file with AirPort network settings:
>
> $ cat > /etc/sysconfig/network-scripts/ifcfg-eth1 << EOF
> NAME=3Dlocalhost
> DEVICE=3Deth1
> IPADDR=3D
> BOOTPROTO=3Ddhcp
> ONBOOT=3Dyes
> NETMASK=3D
> GATEWAY=3D
> ESSID=3D"My Network Name"
> KEY=3DDEADBEAF
> EOF
>
> All available AirPort interface options are listed in
> /etc/sysconfig/network-scripts/ifup-wireless .
>
> If any of the above files exist, it's probably a good idea to use vi
> instead of cat...
>
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general@lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general