As I have experimented, the problem commonly appears with the DHCP client-to-server communication (http://en.wikipedia.org/wiki/DHCP). The DHCP automates the private address assignation and makes easy the client configuration in order to access the Internet.
First, begin removing network-manager, cause it gives problems sometimes
- Code: Select all
apt-get remove network-manager network-manager-gnome
There's the configuration of the interfaces file (/etc/network/interfaces), only the section that refers to the wireless interface. I have used this configuration in Debian GNU/Linux Etch, and it seems to work the majority of the times (The key should be specified in hexagesimal, with no spaces or dots, and I assume that the interface is called wlan0):
- Code: Select all
auto wlan0
iface wlan0 inet dhcp
wireless-channel <the_channel>
wireless-essid <the_essid>
wireless-key open <the_key>
After configuring this, and doing no more changes on the system, if we reconfigure the interfaces (necessary after making any change in the configuration of any interface)
- Code: Select all
sudo /etc/init.d/networking force-reload
the system responds with a sort of DHCP requests to which the AP doesn't respond:
- Code: Select all
Reconfiguring network interfaces...Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/wlan0/00:80:5a:4d:4b:89
Sending on LPF/wlan0/00:80:5a:4d:4b:89
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
The solution to this concern can be reached through the configuration of the DHCP client, concretely the timeout parameter of the /etc/dhcp3/dhclient.conf, uncomment it and set it to 100 milliseconds:
- Code: Select all
...
timeout 100;
...
Save and re-echo the reloading of the configuration:
- Code: Select all
sudo /etc/init.d/networking force-reload
Now, the response of the system should be something like that:
- Code: Select all
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/wlan0/00:80:5a:4d:4b:89
Sending on LPF/wlan0/00:80:5a:4d:4b:89
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPOFFER from 192.168.1.1
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from 192.168.1.1
bound to 192.168.1.130 -- renewal in 124957 seconds.
done.
The AP has given the .130 private IP adress. If there isn't any response yet, you can try to decrease the rate of the link before reconfiguring, supposing you have wireless-tools installed:
- Code: Select all
iwconfig <interface> rate 1M
This solution has worked the majority of the times in my case. Having a low level signal is a problem, if you are too far from the AP, get closer and/or use an antenna (I use a homemade cantenna).