Failing to connect to a wifi ap results in the need for a reboot.

[kallisti5]

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.

[mmlr]

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?

[cocobean]

See #12281. I had an kernel panic issue with iprowifi3945 driver stability. I know there was some recent updates to wpa_supplement 2.6. May be worth a look.

[cocobean]

syslog of iprowifi3945 driver/wpa_supplement 2.4 using hrev_51880

[scottmc]

can you recheck this with a recent Haiku build?

[waddlesplash]

Probably fixed with new wpa_supplicant; at least it works here. Closing as fixed.

[nielx]

Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone