Connecting to a wireless network from command-line
 

I run Ubuntu, and it has a nice GUI widget thing that connects me to my home wireless network when I boot. I don't have a problem with that. But suppose I don't start X, and boot to a recovery console for some reason, like I did recently when my graphics were broken after installing Karmic. In that case, my computer won't be connected to the wireless network until I log into X normally. So I can't apt-get anything or anything. It's very annoying. And I don't know how to connect to my wireless network.

I know my wireless network SSID, and I know my WEP key or WPA passphrase. How can I log onto the network with commandline tools? Is there some basic program that I can just run "networkmanager <myssid> <mywepkey>"? I looked at the iwconfig man page and I honestly couldn't figure out how to simply connect to my network.

Once I figure out how to connect to the network with command-line tools, where can I put an "autoconnect" script so that it will connect during startup, like it should anyway?

What I don't understand is, why the Ubuntu network manager nm-applet, doesn't just work as a front-end for more basic networking stuff. I don't see any reason why it should require you to start X before working; it could be a daemon that runs at startup, and there could be a config-file somewhere, but it doesn't even start running until I log onto gnome.

nm-applet is rubbish (the last time I looked) try uninstalling it and using wicd instead.

Otherwise, it is just a matter of editing your /etc/network/interfaces file to bring up the interface(s) you want at boot time. There are lots of HOWTOs on the net.

My wireless / wired just comes up at boot, and is ready to use as soon as I am logged on. I only use wicd if I am "roaming".

Come back with details of your interfaces file if you get stuck.

When I first switched to Ubuntu I was using the wireless manager that came with it which didn't really do a good job. Switched to wicd though and now it works great, no issues at all with it.

you would want wireless-tools

iwconfig
iwlist wlan0 scan
iwconfig wlan0 essid <my-router>
dhclient

Hi,

I setup a script for just that;

You can just copy the above an save into 'wlan.sh'. Be sure to setup the 'essid', 'key' & 'ap'. Then do a 'chmod +x wlan.sh'. Once you have it saved and proper permissions then just do;

Handy whenever you need to control the device for times like your experiencing.

:hattip:

Simple example of /etc/network/interaces for wireless device called wlan0 and access point using WEP encryption.

The line "auto wlan0" will ensure mean that the interace will come up automatically at boot.
You can manually bring it down with

and down with
NB. This is the way it's done in Debian, and therefore I assume Ubuntu.

HTH,

Evo2.

You know I have never had to do this. I have always just put in channel, key, and essid stuff. I wonder if its needed when your in a multi AP environment?

I've used this before when working in an office where a number or people were running their own wireless routers. However, in my case I put it in my /etc/network/interfaces in the form of:

Cheers,

Evo2.

Hi,

If your environment has multiple access points and signal quality variants then the above is the way to dictate the 'ap' to be used;

:hattip:

Thanks for all the advice. I'm not sure I understand every command but I will try to setup a file. What I don't understand is why the network manager applet doesn't just create this file for you. There are many gui tools that simply edit config files or run simple bash scripts.


I don't understand this syntax. What is ~/# and what is the ' after it?

MN is one of theose GUI tools that edits the config files. But it does it really really badly.

wicd however, "just works", (so long as MN hasn't completely messed up the interfaces file) :)

As does editing your interfaces file yourself (my preferred method). 90 seconds (and I type slowly compared to many) and the problem is solved.

made it a little more user friendly

#!/bin/bash
#
#10-26-09 13:30 gws
#setup the wlan0 device
#

read -p "Wireless SSID:" ssid
read -p "Wepkey:" wep_key
read -p "AP( 00:00:00:00:00:00 ):" ap

/sbin/ifconfig wlan0 192.168.1.18
/sbin/route add default gw 192.168.1.1
/sbin/iwconfig wlan0 essid $ssid
/sbin/iwconfig wlan0 key $wep_key
/sbin/iwconfig wlan0 ap $ap

Oops, missed this bit:
~ means "home" in this case root's home which is the directory /root

What he means is "as root ...

(a root shell has a prompt of "#" - try it now, open terminal sudo -i give your password when prompted, you are root, check the bash prompt has changed. exit or close terminal)

... give the command ./wlan.sh

The ./ means the file is in the current directory and wlan.sh is the script to be run.

HTH

I would like to point out that wicd now has a console based client, wicd-curses. Works great.

Hi,

In the past few weeks I've had a few problems with 'wicd 1.6.2.2'. I exclusively used the 'wicd-curses', one day I could not get a known (recognized) ap or any for that matter. I jumped through hoops to get it going. I had to removepkg then installpkg again. I even removed the stale files left behind from the previous install. It worked for a while but then lost everything again. I removed it for now. I don't move this machine and don't need the hassle. I can manually setup without a problem. I think the 'wicd-curses' was available for 1.6.2.1.

:hattip: