Alice in Userland

the all-encompassing network script

instead of having my computer attempt to connect to the internet whether it’s there or not, which causes it to lag as the dhcpcd times out, I wrote a handy dandy bash script :3

#!/bin/sh

echo “scanning for wireless connections…”

#displaying networks in range
iwlist wlan0 scan|grep ESSID

#assign variables
HOMECHECK=`iwlist wlan0 scan|grep WirelessHomeNet`
HOMENET=” ESSID:\”WirelessHomeNet\”"
LSCHECK=`iwlist wlan0 scan|grep linksys`
LSNET=” ESSID:\”linksys\”"

#check for home network
if [ $HOMECHECK == $HOMENET ]
then
echo “found home network, connecting…”
sh /root/homenet
ping -c 3 google.com
echo “done.”
else
echo “home network not found.”

#check for linksys network
if [ $LSCHECK == $LSNET ]
then
echo “found linksys network, connecting…”
sh /root/linksys
ping -c 3 google.com
echo “done.”
else
echo “linksys not found.”
fi

fi

and what it’s doing here, is:

1. scans for networks in range and displays them to me, because I like seeing these things for myself
2. scans for networks in range again, and greps it for the string that indicates that it sees my home network’s ESSID, WirelessHomeNet, and saves that as the variable HOMECHECK
3. compares the variable HOMECHECK to my preset variable HOMENET (which contains the string that indicates my network is in range), and if they’re the same, it will:
   1. execute the script I wrote to connect to my home internet
   2. ping google to show me the connection is good

   but if they’re not the same, it will go about the same way, checking for a linksys connection, and then if it finds one,

   1. runs the script to connect to linksys
   2. pings google to verify the connection

Amazing, right? So in the end, if neither networks are available, it doesn’t run any of my network-connecting scripts, and therefore does not lag my computer at startup when this is run. :3