Opened 3 years ago

Closed 2 weeks ago

#12482 closed bug (fixed)

Cannot connect to Wireless Network anymore...

Reported by: bruno Owned by: mmlr
Priority: normal Milestone: Unscheduled
Component: Network & Internet/Wireless Version: R1/Development
Keywords: Cc:
Blocked By: Blocking: #13472
Has a Patch: no Platform: All

Description

After booting starting the Network Settings... I see my Wireless Network BeBox-Net (WPA2)...

After choosing my Wifi-Net the Connect Wireless Network Window askes me to store my configuration or not... I choose: Store this configuration and click the OK button Haiku seems to try to find the connection ... but after some seconds (20) I will be asked again wheater to save the config or not... and so on... what to do?

Attachments (19)

syslog (127.8 KB) - added by bruno 3 years ago.
previous_syslog (117.4 KB) - added by bruno 3 years ago.
wpa_supplicant-698-debug-19-11-2015-08-35-59.report (11.1 KB) - added by bruno 3 years ago.
wpa_supplicant-638-debug-21-11-2015-16-32-25.report (11.6 KB) - added by bruno 3 years ago.
previous_syslog.2 (151.5 KB) - added by bruno 19 months ago.
syslog.2 (332.1 KB) - added by bruno 19 months ago.
wpa_supplicant-851-debug-11-01-2017-16-57-25.report (11.1 KB) - added by bruno 19 months ago.
syslog1 (321.4 KB) - added by bruno 18 months ago.
syslog2 (183.9 KB) - added by bruno 18 months ago.
previous_syslog1 (147.5 KB) - added by bruno 18 months ago.
previous_syslog2 (148.2 KB) - added by bruno 18 months ago.
syslog.3 (238.7 KB) - added by bruno 9 months ago.
106 (23.8 KB) - added by bruno 9 months ago.
101 (422.6 KB) - added by bruno 9 months ago.
DHCP
manually changed DHCP to static and back to make it work (153.9 KB) - added by bruno 9 months ago.
wireless_networks (45 bytes) - added by bruno 9 months ago.
outputfile.avi (731.1 KB) - added by bruno 9 months ago.
outputfile.2.avi (2.8 MB) - added by bruno 5 months ago.
2018-07-07 12.12.03.jpg (225.5 KB) - added by bruno 2 weeks ago.

Change History (57)

comment:1 Changed 3 years ago by diver

Please attach your syslog.

Changed 3 years ago by bruno

Attachment: syslog added

Changed 3 years ago by bruno

Attachment: previous_syslog added

comment:2 Changed 3 years ago by bruno

I deleated all my files in the system/settings/network folder.... and tried arround... now I have wireless connection again...

In my network settings folder I have now two files: resolv.conf and wireless_networks...

there shold be 4 files?! or not?

how to save my settings now? They should be saved automatically ... or not?

comment:3 Changed 3 years ago by diver

hostname and hosts are missing but this is probably harmless. What settings are you talking about? The one that lets you automatically connect to your wireless network? I don't know if it works already or not. In any case check this article https://www.haiku-os.org/guides/daily-tasks/wireless

comment:4 Changed 3 years ago by bruno

The one that let meautomatically connect to my wireless network! Yes and no...

It was not working before... since I tried... But I usualy only click on my wireless network once to get a connection. No Settings window was showing up... telling me to store the settings... which I already did...

Before I was able to start the Wifi by using the NetworkStatus in the Deskbar only... right click and choose my Wifi-Network... That was and is ok for me...

BTW.: Where is my .bash_history stored now? I get all history in Terminal but if I open my .bash_history I get only the commands I manually saved there...

After 10 attempts (clicking the save button and ok) I can still get a Wifi connection... but it is not behaving like before...

Last edited 3 years ago by bruno (previous) (diff)

comment:5 Changed 3 years ago by bruno

I did a clean new install! hrev 49857 pkgman full-sync reboot right click on the Network icon in the Deskbar and chose my WIFI connection BeBox-XXXX(WPA2) by clicking on it... After a while (30sec.) the Connect Wireless Network Window will appear... asking me weather to Store this configuration or not... All fields are automatically filled with the correct informations about my Wireless Network... I click on "Store this configuration" and then the button "OK"... then the window will appear again and again... 3 times... 4 times... trying to write or connect... I dont know... 7 times and so on... Then I choose the preferences Network... Disable and Enable the Network choose my WiFi Network there... a few times.. no work... I try to disable and disable the NetworkStatus in the Deskbar and then I will get a Debug Report... I enable the Wifi and the NetworkStatus again... and right click on the Wifi connection in the Deskbar ... sometimes it works sometime not... Strange...

comment:6 Changed 3 years ago by pulkomandy

It seems this was working for you before, so, what did change? If you install an older version of Haiku, does it work there? (and which version is that?)

I'm wondering if this is a new problem in Haiku, or an existing problem that became visible because of an update of your WiFi access point or some other change.

comment:7 Changed 3 years ago by bruno

I depend on a WIFI connection since my local network is not supported... It works ... sometimes... sometimes not!

Some time ago it was reconnecting automatically when the connection got lost.

I am so happy to see Webpositive working fast enough now... unfortunately my WIFI makes me a headache.

Last edited 18 months ago by bruno (previous) (diff)

comment:8 Changed 3 years ago by bruno

After deleating all files in boot/system/settings/network Haiku will create a resolve.config file in this folder...

Seems to work now... this way... maybe wrong.. but works for me right now...

comment:9 Changed 3 years ago by bruno

unable to "Store this configuration" in wpa_supplicant

If I try 30 times sometimes it will connect to the WIFI Network...

comment:10 Changed 3 years ago by bruno

This version hrev. 49921 works well... if i restart i can connect... hope it will be solved soon this crazy bug...

comment:11 Changed 2 years ago by bruno

maybe solved can be closed this ticket... thx...

comment:12 Changed 2 years ago by diver

wpa_supplicant package hasn't been updated yet so this issue should be still there.

comment:13 Changed 2 years ago by diver

Owner: changed from axeld to mmlr
Status: newassigned

comment:14 Changed 2 years ago by bruno

yes true... it works somehow but is not right at the moment...

comment:15 Changed 19 months ago by bruno

I can connect but have always problems to store the configuration file of wpa_supplicant its popup-window... has to clich ok 3 or 5 times to make it connect to the WIFI...

comment:16 Changed 19 months ago by bruno

I still have have problems storing the wifi-connection. Have to click a few times /ok/ ...usually 5 times until I get connected.

Last edited 19 months ago by bruno (previous) (diff)

comment:17 Changed 19 months ago by bruno

I just found out... If i boot Haiku and wait some Minutes and then try to connect... everything works like expected... All ok... if I just wait just after starting Haiku...

Changed 19 months ago by bruno

Attachment: previous_syslog.2 added

Changed 19 months ago by bruno

Attachment: syslog.2 added

comment:18 Changed 19 months ago by bruno

Haiku hrev 50849

I just added the previous_syslog with no problems connecting... and the one one minute after booting into Haiku with the problems...

I added a wpa_supplicant-851-debug-11-01-2017-16-57-25.report

Last edited 19 months ago by bruno (previous) (diff)

comment:19 Changed 18 months ago by bruno

If I start Haiku from CD and choose to connect to WIFI (by right-clicking the network icon in the Deskbar and choosing my network) the Connect Wireless Network window pops up.

I fill in my WPA2 Password and it works! Each time I start Haiku from CD. Check box "store this configuration" checked or not!

Booting Haiku from locally HD, and trying to connect still makes the "Connect Wireless Network" window poping up several times until accepting to connect. Sometimes it will refuse to connect and I have to restart Haiku.

I will attach my syslogs: syslog1 before trying to storeing the networks configuration and key. and the syslog2 after triying to store the key and the preferences.

Get keys from the keyring... Maybe there is the problem? Because in CD mount there is no keyring pop up window!?

Last edited 18 months ago by bruno (previous) (diff)

Changed 18 months ago by bruno

Attachment: syslog1 added

Changed 18 months ago by bruno

Attachment: syslog2 added

Changed 18 months ago by bruno

Attachment: previous_syslog1 added

Changed 18 months ago by bruno

Attachment: previous_syslog2 added

comment:20 Changed 9 months ago by bruno

If I use static it works well now... but still DHCP won't

Changed 9 months ago by bruno

Attachment: syslog.3 added

Changed 9 months ago by bruno

Attachment: 106 added

comment:21 Changed 9 months ago by pulkomandy

A description of the setup for each test would help (which are with a static IP, for example?)

Anyway, in "106" I notice the following pattern, which seems strange:

383	DAEMON 'DHCP': /dev/net/iprowifi3945/0: Send DHCP_DISCOVER to 255.255.255.255:67
384	DAEMON 'DHCP': /dev/net/iprowifi3945/0: Send DHCP_REQUEST to 255.255.255.255:67
385	DAEMON 'DHCP': /dev/net/iprowifi3945/0: Send DHCP_DISCOVER to 255.255.255.255:67
386	DAEMON 'DHCP': /dev/net/iprowifi3945/0: Send DHCP_REQUEST to 255.255.255.255:67
387	DAEMON 'DHCP': /dev/net/iprowifi3945/0: Send DHCP_DISCOVER to 255.255.255.255:67
388	DAEMON 'DHCP': /dev/net/iprowifi3945/0: Send DHCP_REQUEST to 255.255.255.255:67
389	DAEMON 'DHCP': /dev/net/iprowifi3945/0: Send DHCP_DISCOVER to 255.255.255.255:67
390	KERN: wlan_control: 9235, 15
391	KERN: wlan_control: 9235, 76
392	DAEMON 'DHCP': /dev/net/iprowifi3945/0: Send DHCP_REQUEST to 255.255.255.255:67
393	DAEMON 'DHCP': /dev/net/iprowifi3945/0: Send DHCP_DISCOVER to 255.255.255.255:67
394	DAEMON 'DHCP': /dev/net/iprowifi3945/0: Send DHCP_REQUEST to 255.255.255.255:67
395	DAEMON 'DHCP': /dev/net/iprowifi3945/0: Send DHCP_DISCOVER to 255.255.255.255:67
396	DAEMON 'DHCP': /dev/net/iprowifi3945/0: Send DHCP_REQUEST to 255.255.255.255:67
397	KERN: wlan_control: 9235, 76
398	DAEMON 'DHCP': /dev/net/iprowifi3945/0: Send DHCP_DISCOVER to 255.255.255.255:67
399	DAEMON 'DHCP': /dev/net/iprowifi3945/0: Send DHCP_REQUEST to 255.255.255.255:67
400	DAEMON 'DHCP': /dev/net/iprowifi3945/0: Send DHCP_DISCOVER to 255.255.255.255:67
401	DAEMON 'DHCP': /dev/net/iprowifi3945/0: Send DHCP_REQUEST to 255.255.255.255:67
402	KERN: wlan_control: 9235, 1
403	KERN: wlan_control: 9235, 15
404	DAEMON 'DHCP': /dev/net/iprowifi3945/0: Send DHCP_DISCOVER to 255.255.255.255:67
405	KERN: wlan_control: 9234, 19
406	Last message repeated 1 time
407	KERN: wlan_control: 9235, 15
408	KERN: wlan_control: 9235, 76
409	DAEMON 'DHCP': /dev/net/iprowifi3945/0: Send DHCP_REQUEST to 255.255.255.255:67
410	DAEMON 'DHCP': /dev/net/iprowifi3945/0: Received DHCP_ACK from 192.168.2.1
411	DAEMON 'DHCP':   server: 192.168.2.1
412	DAEMON 'DHCP':   lease time: 4294967295 seconds
413	DAEMON 'DHCP':   subnet: 255.255.255.0
414	DAEMON 'DHCP':   gateway: 192.168.2.1
415	DAEMON 'DHCP':   nameserver[0]: 192.168.2.1
416	DAEMON 'DHCP': /dev/net/iprowifi3945/0: DHCP status = No error

No DHCP_OFFER was received (or it was not understood), but still we eventually get a DHCP_ACK and seem happy with that. Where does the IP come from in this case?

comment:22 Changed 9 months ago by pulkomandy

Blocking: 13472 added

comment:23 Changed 9 months ago by bruno

In this case the IP comes from my static IP i gave. Because DHCP wont work and gives a wrong IP here: 117! not the correct 106! I don't get a connection with DHCP enabled... I have to use static IP 192.168.2.106 to make WIFI work! 192.168.2.117 wont work!

Last edited 9 months ago by bruno (previous) (diff)

comment:24 Changed 9 months ago by bruno

This morning I tried DHCP again and it looks like that it works now! I get the correct IP: xxx.xxx.x.101 I will leave this settings now untouched and will test it for a while. I will attach the actual syslog 101... whith the correct looking IP address! Maybe there is still some problem? I will have to try for a while first... Btw.: How to autostart the DHCP connection, so I dont have to start it manually every start/boot?

comment:25 Changed 9 months ago by bruno

This morning I tried DHCP again and it looks like that it works now! I get the correct IP: xxx.xxx.x.101 I will leave this settings now untouched and will test it for a while. I will attach the actual syslog 101... whith the correct looking IP address! Maybe there is still some problem? I will have to try for a while first... Btw.: How to autostart the DHCP connection, so I dont have to start it manually every start/boot?

Changed 9 months ago by bruno

Attachment: 101 added

DHCP

comment:26 Changed 9 months ago by bruno

Has a Patch: set

comment:27 Changed 9 months ago by pulkomandy

Has a Patch: unset

It should be automatic already. You just select your wifi network, enter the password and check "store this configuration". Then you allow wpa_supplicant to store the password in the keystore. This should be all there is needed. If that doesn't work, then it's a bug.

comment:28 Changed 9 months ago by bruno

Ok then the bug is still there! After start/boot I have to: 1.: Choose the WLAN manually. (then it will stuck in configuring!) 2.: I have to change manualy from DHCP to static and back to DHCP to make DHCP work.

As I noticed today: Network settings asks for the password but does'nt store it in the wireless_networks file (boot/system/settings/network/wireless_network) it writes only:network mynetwork and does not store the password! It schould store: network mynetwork {password mypassword} Am I wrong?

Last edited 9 months ago by bruno (previous) (diff)

comment:29 Changed 9 months ago by bruno

Has a Patch: set

Changed 9 months ago by bruno

Attachment: wireless_networks added

Changed 9 months ago by bruno

Attachment: outputfile.avi added

comment:30 Changed 6 months ago by pulkomandy

Has a Patch: unset

comment:31 Changed 5 months ago by bruno

Still the same... to connect I have to click the wireless network icon in the Deskbar and choose my WIFI... As soon as the notification shows up... showing: configuring... I have to click the icon again and choose network settings... In the network preflet I choose IPV4... change the DHCP to STATIC and back to DHCP to make the connection work. Notification is showing up: READY! That I have to do every time I start Haiku! I close the Network Preflet and network is ready...

comment:32 Changed 5 months ago by bruno

Still the same... to connect I have to click the wireless network icon in the Deskbar and choose my WIFI... As soon as the notification shows up... showing: configuring... I have to click the icon again and choose network settings... In the network preflet I choose IPV4... change the DHCP to STATIC and back to DHCP to make the connection work. Notification is showing up: READY! That I have to do every time I start Haiku! I close the Network Preflet and network is ready...

btw.: anyone watched my BeScreenCapture Video? Thx...

Last edited 5 months ago by bruno (previous) (diff)

Changed 5 months ago by bruno

Attachment: outputfile.2.avi added

comment:33 Changed 3 weeks ago by bruno

Still same problem start network... ...configure... then I change in Network Preflet to static IP and back to DHCP to make the connection "ready"

comment:34 Changed 2 weeks ago by bruno

I use a 32Bit built.. With the updated WIFI driver Haiku Rev.52077 will go into KDL if WIFI is on... will attach the kdl pic Haiku will crash immediately if I switch WIFI on...

Last edited 2 weeks ago by bruno (previous) (diff)

Changed 2 weeks ago by bruno

Attachment: 2018-07-07 12.12.03.jpg added

comment:35 Changed 2 weeks ago by diver

Try with newer revision, this should be fixed now.

comment:36 Changed 2 weeks ago by diver

Actually, it looks like it crashes there even with the newer revision as well. See #14246.

comment:37 Changed 2 weeks ago by bruno

with hrev 52080-1.....[master] WIFI is working quiet nicely... no need to go to static IP and then back to DHCP anymore! choosing my WIFI connection is enough to make it "ready"-- hoping it will persist!

comment:38 Changed 2 weeks ago by diver

Resolution: fixed
Status: assignedclosed

Closing as fixed then.

Note: See TracTickets for help on using tickets.