Why would you want to do this? Because when you do, the wireless LAN connection comes up automatically when you boot the machine. This is a really good idea if you are running any servers (e.g., the outrageously fun MPD). Of course it's a really bad idea to run a server off a wireless connection whether it comes up automatically or not, but sometimes you just can't snake cables where you want your machine to be. And if you're not running any servers, it spares you the bother of having to type in connection authorization at login. If you do a lot of roaming, then giving up NetworkManager (or the similar netapplet) may not be such a great idea; but if you don't, this approach may save you from some bother.
The only things I would add to what is posted in the Ubuntu forum are:
- You can include more that one interface in the /etc/network/interfaces file.
- If you use a network interface card that is removable (PCMCIA, USB, etc.) you may get better results if you specify it as
allow-hotplug
rather thanauto
. - If you do specify an interface as
allow-hotplug
rather thanauto
, issuing thesudo /etc/init.d/networking restart
command won't bring up the interface(s). To do that you will need to issueifup < the_name_of_the_interface >
# This file describes the network interfaces available on your systemOf course, your details will differ.
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
#auto eth0
iface eth0 inet dhcp
allow-hotplug ath0
#auto ath0
iface ath0 inet dhcp
wpa-driver madwifi
wpa-ssid ufart
wpa-ap-scan 1
wpa-proto WPA
wpa-pairwise TKIP
wpa-group TKIP
wpa-key-mgmt WPA-PSK
wpa-psk <>
No comments:
Post a Comment