comp.os.linux.networking

> The connection is here 50/100, actually using the same provider
> ("Wayport").

Fiddling is fine IMO. Although you have to be root or otherwise have
admin priviledges for the network settings. Definitely not ideal for most
lowly users.

> I don't think this is the result of a bad connection - looks like
> something else is broken.

The below are variables that contain pre-determined parameters based on
what I know about that access point. As for-told by the all mighty iwlist.

>> DHCP_CHANNEL=1
>> DHCP_RATE=11
>> DHCP_KEY=off
>> DHCP_MODE=Managed
>> DHCP_ESSID=Wayport_Access
>> wireless_interface=wlan0


> What does this do (iwconfig key)?

iwconfig wlan0 key off

I use wep at home, so making sure things line up with what iwlist tells me
about the connection I'm trying to make. aka Encryption: off

for that specific location without the dynamic variables:

iwconfig wlan0 essid "Wayport_Access"
iwconfig wlan0 key off
iwconfig wlan0 mode "Managed"
iwconfig wlan0 channel 1
iwconfig wlan0 rate 11
dhclient3 wlan0 -s "Wayport_Access"

Generally I need Mode, and Channel(texas rest stops). For older 802.11b I
also need rate(diamond jacks, bosier city, LA). And for some I need the
essid matched. Although dhclient3 wlan0 -s "essid" might aid that
dependancy. Or at least make it timeout quicker when in the presence of a
dozen or more essid's. (like the bank, a few blocks away from the library)

Most of the extra stuff is just to ensure I don't have to revisit any
missed parameters after dhclient3 timed out.

HTH