#12280 closed bug (fixed)
Failing to connect to a wifi ap results in the need for a reboot.
Reported by: | kallisti5 | Owned by: | nobody |
---|---|---|---|
Priority: | blocker | Milestone: | R1/beta2 |
Component: | Network & Internet/Wireless | Version: | R1/Development |
Keywords: | WIFI key prop | Cc: | |
Blocked By: | Blocking: | ||
Platform: | All |
Description
if you enter the wrong key and fail connecting to a wifi network, you have to reboot and start over
This is a break-apart of the issues listed in #7660.
Attachments (1)
Change History (8)
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Blocking: | 7660 removed |
---|
comment:3 by , 8 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
by , 7 years ago
syslog of iprowifi3945 driver/wpa_supplement 2.4 using hrev_51880
comment:6 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Probably fixed with new wpa_supplicant; at least it works here. Closing as fixed.
comment:7 by , 5 years ago
Milestone: | R1 → R1/beta2 |
---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
Note:
See TracTickets
for help on using tickets.
Are you able to reproduce this issue? The implemented workflow is as follows:
1) Try finding a stored key for the selected network and try to connect using it 2) If the connection fails (timeout with no success notification) or there were no stored credentials, bring up the dialog 3) Try to connect using the supplied credentials 4) When a connection is established successfully, store the credentials, otherwise go back to 2
The wpa_supplicant is told to shut down the association attempt when the timeout occurs, which probably is the root cause of this issue. It is probably related to disabling/reenabling the interface in the FreeBSD compatibility layer and might therefore also be driver specific. What setup did you test on?