Unfortunately it works so poorly in my specific configuration, works so poorly with secured access points, that the primary tutorials for Ubuntu push users in the direction that I took. It's a damned shame that it doesn't work as seemlessly and easily as it does in the OSS embedded GTK Maemo, but NetworkManager really didn't work for me.
-Sean
On Sat, Aug 30, 2008 at 10:43 PM, Justin Dugger [email protected] wrote:
On Sat, Aug 30, 2008 at 1:23 AM, Sean Crago [email protected] wrote:
I've got a well defined interfaces file (follows in the PS), but neither my Ubuntu laptop nor my Ubuntu desktop manages to create a wireless link on boot.
Anyone got an easy fix? I'll gripe and moan until the universe dies its heat death about the age and maturity of Linux not being reflected at all in luser-friendly GUI wifi configuration out of the box (or until it's fixed), but this should be what those apps are doing under the hood, and even it's not working right.
# The loopback network interface auto wlan0 eth0 lo iface lo inet loopback
# The primary network interface iface wlan0 inet dhcp wpa-driver wext wpa-key-mgmt WPA-PSK wpa-proto WPA wpa-ssid 001601842AEE wpa-psk MD5_hash_of_my_WPA2-AES_key
iface eth0 inet dhcp
Is there a reason to avoid Network Manager and applets? I've found it works well, but as per the README requires that that specific file be mostly blank!
Justin Dugger