Ticket #309 (closed defect: invalid)
No dhcp lease with kernel 2.6.28 using WPA2
| Reported by: | Kareema | Owned by: | ainulindale |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | SHR Image | Version: | SHR-unstable |
| Keywords: | Cc: |
Description
Starting with the kernel 2.6.28 image, I no longer get a dhcp lease with WPA2 using wpa_supplicant, although it seems that I'm connected to my access point. The same works perfectly with WEP. There were no such problems with kernel 2.6.24.
ifup output:
root@neo:~# ifup eth0 WPA: Configuring Interface ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported ioctl[SIOCSIWENCODEEXT]: Operation not supported udhcpc (v1.13.2) started run-parts: /etc/udhcpc.d/00avahi-autoipd exited with code 1 Sending discover... Sending discover... Sending discover... No lease, failing
Attachments
Change History
comment:1 Changed 3 years ago by Kareema
AR6000 seems to disconnect from AP every 4 seconds for no obvious reason (see syslog-wlan.txt).
comment:2 Changed 3 years ago by Kareema
Configuration: AP is a FRITZ!Box Fon WLAN 7050, firmware version 14.04.33 and dnsmasq 2.45-1ubuntu1 as DHCP on an Ubuntu server. Connection attempts with WPA and WPA2 and the following kernels on the same base system (SHR unstable up-to-date):
2.6.24:
kernel-2.6.24_2.6.24-oe4+gitrfb42ce6724576fc173faf8abfb04aa2c36d213b7-r0_om-gta02: WORKING!!!
2.6.28-rc4 (from SHR):
uImage-2.6.28-oe1+gitr34240a1c06ae36180dee695aa25bbae869b2aa26-r3-om-gta02.bin: not working
2.6.29-rc2 and 2.6.29-GTA02_andy-tracking-mokodev:
uImage-2.6.28-stable+gitr0+f19f259d3c1afde8eae53983fd19f61831927413-r2-om-gta02.bin: not working
uImage-moredrivers-GTA02_andy-tracking-15ca3dafb2662db4.bin: not working
comment:4 Changed 3 years ago by dos
- Status changed from new to closed
- Resolution set to invalid
Happens to me the same with my home network with 2.6.28 and 2.6.29 kernel. It doesn't matter, if i'm using WPA, WEP or open network. Connecting to others (not-my-home :P) networks works well. But... I don't think it's SHR problem, please fill bug in OM tracker.

