[solved] Problems with wireless / dhcp

Question

I've been happily using Arch for the past two years but only recently I hit a problem I can't seem to solve on my own.
I have a wireless network at home, with WPA encryption and suddenly one day (probably after an update) I cannot get the IP address from my router over DHCP any more. The other PC at home (with Windows) works as it used to.
Details:
[fijam@hp510 ~]$ cat /etc/network.d/wlan
CONNECTION="wireless"
INTERFACE=eth1
SECURITY="wpa"
ESSID="wlan"
KEY="xxxxxxxxxxxx"
IP="dhcp"
TIMEOUT="30"
DHCP_OPTIONS="-d"
[fijam@hp510 ~]$ cat /etc/dhcpcd.conf
# Inform the DHCP server of our hostname for DDNS.
hostname
# A list of options to request from the DHCP server.
option domain_name_servers, domain_name, domain_search, host_name
# Most distributions have NTP support.
#option ntp_servers
# Respect the network MTU.
option interface_mtu
# A ServerID is required by RFC2131.
# Some broken DHCP servers do not send one and dhcpcd can work without it.
# Some broken DHCP servers NAK incorrectly and do not include a ServerID
# either so the default is to require a ServerID.
#require dhcp_server_identifier
# A hook script is provided to lookup the hostname if not set by the DHCP
# server, but it should not be run by default.
nohook lookup-hostname
noipv4ll
[fijam@hp510 ~]$ sudo netcfg -c wlan
:: wlan up [BUSY]
dhcpcd: version 5.0.6 starting
dhcpcd: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT
dhcpcd: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
dhcpcd: eth1: rebinding lease of 192.168.1.12
dhcpcd: eth1: sending DHCP_REQUEST (xid 0x55befbc9), next in 3.13 seconds
dhcpcd: eth1: sending DHCP_REQUEST (xid 0x55befbc9), next in 7.96 seconds
dhcpcd: timed out
- DHCP IP lease attempt failed. [FAIL]
[fijam@hp510 ~]$ iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
eth1 IEEE 802.11g ESSID:"wlan"
Mode:Managed Frequency:2.417 GHz Access Point: 00:1E:37:EF:67:60
Bit Rate:54 Mb/s Tx-Power=20 dBm Sensitivity=8/0
Retry limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=68/100 Signal level=-59 dBm Noise level=-89 dBm
Rx invalid nwid:0 Rx invalid crypt:41 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:218 Missed beacon:0
Help would be appreciated, I am really out of ideas here.
Last edited by fijam (2009-08-06 15:35:32)

Answer 1

EDIT: Actaully, dhcpcd still would not work while dhclient obtained IP without problems. I fixed the problem by adding -r <ip> to DHCP_OPTIONS in network.d file but I am still not sure why is it necessary.
EDIT2: Today -- not working again. I increased DHCP_TIMEOUT to 60 and it eventually gets the IP. I am surprised since the link quality is 77 and it had not been necessary before.
Last edited by fijam (2009-08-05 09:11:04)