Opened 12 years ago

Closed 12 years ago

Last modified 11 years ago

#6455 closed bug (fixed)

Wireless connection DHCP does not work as expected.

Reported by: bbjimmy Owned by: axeld
Priority: normal Milestone: R1
Component: Network & Internet/Wireless Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: x86



device Network controller (Ethernet controller) [2|0|0]

vendor 168c: Atheros Communications Inc. device 001c: AR5001 Wireless Network Adapter

and Hailku 36822

With one wireless connection detected using wlanconfig scan:

DHCP finds an ip and gaterwaw, but may change to a new ip at any time... re-assigning the ip from the router. To use wireless I set the ip to static then re-boot to keep the ip ... just seting the ip to static will not keep the ip, the reboot is required.

With more than one wireless connecction:

Wlanconfig join to connect to the proper connection, DHCP finds the ip, but will re-negociate with any detected connection at any time. To use the connection I need to use wlanconfig to set the proper connection and dhcp to get the ip, then set the ip to static and reboot as before, or the ip will change again.

Change History (6)

comment:1 by bbjimmy, 12 years ago

using hrev38094

DHCP no longer finds an ip. I must already know the router gateway and ip range and dns to connect.

Before at least DHCP would find the info for me even if it would not keep the ip.

comment:2 by andrewbachmann, 12 years ago

If you have a chance you may want to try again with hrev38838 which fixed DHCP issues for me.

comment:3 by bbjimmy, 12 years ago

Indeed DHCP seems to be working again on my wifi again. Sorry for the delay testing, my build system was not working for a while.

comment:4 by axeld, 12 years ago

Resolution: fixed
Status: newclosed

Thanks for the update!

comment:5 by bbjimmy, 12 years ago

Now DHCP is back to where it was when I opened the ticket.

in reply to:  5 comment:6 by deejam, 11 years ago

Replying to bbjimmy:

Now DHCP is back to where it was when I opened the ticket.

The description of this ticket sounds like the same problem as what's now tracked in #7346.

Note: See TracTickets for help on using tickets.