Opened 11 years ago
Last modified 4 months ago
#10162 assigned bug
WIFI doesn't automatically connect
Reported by: | Giova84 | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Servers/net_server | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | #17064 | |
Platform: | All |
Description (last modified by )
I have an atheros wifi card, WPA2 auth method. Every time that I boot Haiku, also if i choose to store the details, i have to manually select my SSID.
syslog attached.
Attachments (1)
Change History (24)
by , 11 years ago
comment:1 by , 11 years ago
Component: | Servers → Servers/keystore_server |
---|---|
Description: | modified (diff) |
Owner: | changed from | to
Platform: | x86 → All |
comment:2 by , 11 years ago
comment:3 by , 11 years ago
No, i don't need to enter again my password. So the keystore_server shouldn't be the culprit.
comment:4 by , 11 years ago
I have momentarily solved with the following workaround: Inside UserBootScript i have added
ifconfig /dev/net/atheroswifi/0 join MYSSID
But is only a temporary workaround :-)
comment:5 by , 11 years ago
Component: | Servers/keystore_server → Servers/net_server |
---|---|
Owner: | changed from | to
comment:6 by , 9 years ago
I have the same problem with my Atheros WLAN adapter, the network also WPA2.
Haiku (recent nightly gcc2h) does not ask for password, it just does not connect automatically, so i need to go to the right click menu of NetworkStatus replicant, and select my SSID, then it connectin without problem.
I will try the UserBootScript workaround, but it would be better to locate and eliminate this bug for the new users.
comment:7 by , 9 years ago
I does work for my iprowifi4695 after setting the WLAN in the Network preferences. Have you tried that?
comment:8 by , 8 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:10 by , 4 years ago
device Network controller [2|80|0]
vendor 168c: Qualcomm Atheros device 0036: QCA9565 / AR9565 Wireless Network Adapter
Problem still exists (hrev55022)
comment:11 by , 3 years ago
On a hunch... does the SSID that is problematic contain a space? I have noticied that common SSID names with spaces like "FritzBox NNNN" seem to not work for reconnecting, but I have other single name SSID's that do work.
Yesterday I renamed a SSID from the FritzBox NNNN style to a single word name and afterwards the new SSID managed to autoconnect, thus my hunch that this might be related to spaces. (could also explain https://dev.haiku-os.org/ticket/14043)
comment:13 by , 3 years ago
Blocking: | 17064 added |
---|
comment:14 by , 2 years ago
Still present in hrev56391. With Haiku starting to look like it's ready for prime time, this should probably be addressed.
comment:15 by , 2 years ago
Yeah, probably. It's only two clicks to do it manually if you have the password saved, but that's two clicks less than every other OS :)
Likely the entire autoconnect logic needs to be totally scrapped and rewritten. It's never worked for me, anyway.
comment:16 by , 2 years ago
It works fine for me most of the time, maybe somebody should check how it works first before scrapping it :P
comment:18 by , 11 months ago
I added the following to my UserBootScript:
sleep 10; ifconfig /dev/net/realtekwifi/0 join [SSID name] [Passphrase] &
Hopefully this also works for Atheros wifi hardware?
comment:19 by , 9 months ago
FWIW,
This problem is still present in hrev57521.
Wifi device is a USB dongle (RTL8188CUS) at /dev/net/realtekwifi/0.
comment:20 by , 6 months ago
still happens in latest nightly hrev57709 with my iaxwifi200 integrated wireless device, and the password is not persisted even when storing it and enabling keychain access, so I have to enter the password everytime.
This has another unpleasant side-effect in that the clock is not synced and I have to go to Time preferences to manually sync with network time after my network is up again.
comment:21 by , 4 months ago
May be worth trying again. There's been quite the update in network drivers and my wifi dongle has been automatically starting a successful connection immediately after boot every time for a few days. Before updating it would usually take some minutes and some days I would have to ifconfig down/up to force it to connect.
comment:22 by , 4 months ago
tried with build from July 4th, sadly still not working. It also takes a really long time (approx 20) before the prompt even comes up. Here's some relevant output from Linux 6.9.7-1 (Manjaro testing):
[ 4.307275] iwlwifi 0000:00:14.3: Detected crf-id 0x3617, cnv-id 0x20000302 wfpm id 0x80000000 [ 4.307295] iwlwifi 0000:00:14.3: PCI dev a0f0/0074, rev=0x351, rfid=0x10a100 [ 4.319466] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37 [ 4.319747] iwlwifi 0000:00:14.3: loaded firmware version 77.a20fb07d.0 QuZ-a0-hr-b0-77.ucode op_mode iwlmvm [ 4.518287] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x351 [ 4.640122] iwlwifi 0000:00:14.3: Detected RF HR B5, rfid=0x10a100 [ 4.705856] iwlwifi 0000:00:14.3: base HW address: f0:9e:4a:61:39:15 [ 4.724456] iwlwifi 0000:00:14.3 wlp0s20f3: renamed from wlan0 [ 5.539867] iwlwifi 0000:00:14.3: Registered PHC clock: iwlwifi-PTP, with index: 0
comment:23 by , 4 months ago
Ok since the latest nightlies where the updated BSD drivers and related fixes have been integrated this works much better now, but not fully.
I don't need to enter my password again and the authentication method is also remembered directly, that was an intermittent glitch where it always defaulted to open.
However, still no automatic connection on boot. I always have to manually select my wireless network from the list, then it works.
Do you need to enter your password after connecting to your SSID?