Since 2.6.26. I use ath5k instead of madwifi-ng. For several reasons I disabled the dhcp-server of my wlan-router and configured the wlan-devices static. /etc/conf.d/net: modules="wpa_supplicant" wpa_supplicant_ath0="-Dwext" config_ath0="192.168.100.100/24" routes_ath0="default via 192.168.100.1" dns_servers_ath0="192.168.100.100" But instead of assigning this configuration to the network-device, ath0 tries to get an ip by dhclient: /var/log/messages: Oct 7 15:41:26 Blechkasten ath0: Initial auth_alg=0 Oct 7 15:41:26 Blechkasten ath0: authenticate with AP 00:1d:19:ba:1e:72 Oct 7 15:41:26 Blechkasten ath0: RX authentication from 00:1d:19:ba:1e:72 (alg=0 transaction=2 status=0) Oct 7 15:41:26 Blechkasten ath0: authenticated Oct 7 15:41:26 Blechkasten ath0: associate with AP 00:1d:19:ba:1e:72 Oct 7 15:41:26 Blechkasten ath0: RX AssocResp from 00:1d:19:ba:1e:72 (capab=0x431 status=0 aid=1) Oct 7 15:41:26 Blechkasten ath0: associated Oct 7 15:41:26 Blechkasten ath0: switched to short barker preamble (BSSID=00:1d:19:ba:1e:72) Oct 7 15:41:26 Blechkasten Adding 1461904k swap on /dev/sda2. Priority:-1 extents:1 across:1461904k Oct 7 15:41:26 Blechkasten rc[3125]: segfault at 960 ip b80e50d4 sp bfff4708 error 4 in ld-2.8.so[b80dc000+1a000] Oct 7 15:41:26 Blechkasten rc[2430]: segfault at 2f00 ip b80d6ac6 sp bfff5ce0 error 4 in libutil-2.8.so[b80d6000+2000] Oct 7 15:41:27 Blechkasten dhclient: wmaster0: unknown hardware address type 801 Oct 7 15:41:30 Blechkasten dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6 Oct 7 15:41:36 Blechkasten dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 9 Oct 7 15:41:45 Blechkasten dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 15 Oct 7 15:42:00 Blechkasten dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 11 Oct 7 15:42:11 Blechkasten dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 15 Oct 7 15:42:26 Blechkasten dhclient: DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5 Oct 7 15:42:31 Blechkasten dhclient: No DHCPOFFERS received. During the boot process I recognize this behaviour in that way, that the system hangs for about one minute while booting. After completing the boot-process I have to restart the net.ath0-service, then the static configuration will assign to the device and the card works quite unproblematic. Reproducible: Always Steps to Reproduce: 1. Boot the system with static net configuration (no dhcp) connected to the red by a wlan-device Actual Results: There's no ip assigned to the wlan network card. Expected Results: The wlan-configuration should be able to work without dhclient. I simply want to have a static configured working wlan-device. Additional comments: 1. This behaviour is independet of the kind of the ath5k-module. I tried it as module and also as compiled in into the kernel. No difference. 2. If there's an entry in /var/lib/dhcp/dhclient.leases, that is vaild for this network, then dhclient tries to assign this entry and the red works afterwards. But this "workaround" isn't an acceptable behaviour.
*** This bug has been marked as a duplicate of bug 240383 ***
