Regression with latest iaxwifi200 merge? Cannot connect to github, HaikuDepot

Development OS
1

I’m having troubles connecting to certain sites, Wifi drops connection sometimes and lookups tend to take a long time.
All that worked quite fine before, and my network is stable under Linux (600Mbit connection).
No proxy, standard DNS from my provider / using local 192.168.0.1 as usual.

Now I read in the March update that upstream changes to the iaxwifi driver have been merged, so I suspect it might have caused regressions.

Here’s a syslog from a successful initialization which allows me to go online with WebPositive, but not connect to github:

KERN: iwx: SCAN -> INIT
Last message repeated 1 time
KERN: iwx: SCAN -> AUTH
KERN: iwx: AUTH -> ASSOC
KERN: iwx: ASSOC -> RUN
KERN: /dev/net/iaxwifi200/0: link up, media 0x870080 quality 1000 speed 0
DAEMON 'DHCP': /dev/net/iaxwifi200/0: Send DHCP_REQUEST for 192.168.0.150 to 255.255.255.255:67
DAEMON 'DHCP': /dev/net/iaxwifi200/0: Send DHCP_REQUEST to 255.255.255.255:67
DAEMON 'DHCP': /dev/net/iaxwifi200/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON 'DHCP': /dev/net/iaxwifi200/0: Received DHCP_OFFER from 192.168.0.1
DAEMON 'DHCP':   your_address: 192.168.0.150
DAEMON 'DHCP':   server: 192.168.0.1
DAEMON 'DHCP':   lease time: 86400 seconds
DAEMON 'DHCP':   renewal time: 43200 seconds
DAEMON 'DHCP':   rebinding time: 75600 seconds
DAEMON 'DHCP':   subnet: 255.255.255.0
DAEMON 'DHCP':   broadcast: 192.168.0.255
DAEMON 'DHCP':   gateway: 192.168.0.1
DAEMON 'DHCP':   nameserver[0]: 192.168.0.1
DAEMON 'DHCP':   domain name: "telekom.ip"
DAEMON 'DHCP': /dev/net/iaxwifi200/0: Send DHCP_REQUEST for 192.168.0.150 to 255.255.255.255:67
DAEMON 'DHCP': /dev/net/iaxwifi200/0: Received DHCP_ACK from 192.168.0.1
DAEMON 'DHCP':   server: 192.168.0.1
DAEMON 'DHCP':   lease time: 86400 seconds
DAEMON 'DHCP':   renewal time: 43200 seconds
DAEMON 'DHCP':   rebinding time: 75600 seconds
DAEMON 'DHCP':   subnet: 255.255.255.0
DAEMON 'DHCP':   broadcast: 192.168.0.255
DAEMON 'DHCP':   gateway: 192.168.0.1
DAEMON 'DHCP':   nameserver[0]: 192.168.0.1
DAEMON 'DHCP':   domain name: "telekom.ip"
DAEMON 'DHCP': /dev/net/iaxwifi200/0: DHCP status = No error

And here is a problematic session where i had to manually disable/enable wifi via Network prefs (note the “not supported” opcodes in the log):

KERN: openbsd wlan_control: 9235, 78 (not supported)
KERN: [net/iaxwifi200/0] compat_close()
KERN: wlan_close(0xffffffffc4d92008)
KERN: iwx: RUN -> INIT
KERN: [net/iaxwifi200/0] compat_free()
KERN: [net/iaxwifi200/0] compat_open(0x2)
KERN: /dev/net/iaxwifi200/0: link down, media 0x80 quality 1000 speed 0
KERN: iwx: SCAN -> AUTH
KERN: iwx: AUTH -> ASSOC
KERN: iwx: ASSOC -> RUN
KERN: /dev/net/iaxwifi200/0: link up, media 0x870080 quality 1000 speed 0
KERN: openbsd wlan_control: 9235, 78 (not supported)
KERN: openbsd wlan_control: 9235, 16 (not supported)
KERN: iwx: RUN -> INIT
KERN: /dev/net/iaxwifi200/0: link down, media 0x80 quality 1000 speed 0
DAEMON 'DHCP': /dev/net/iaxwifi200/0: Send DHCP_RELEASE to 192.168.0.1:67

Using Haiku/Dev hrev58805 (stuck to that one since I cannot update, Haiku repo is not reachable for me).

1 Like
2

What’s the last working hrev for you?

3

should be the one from 09.04.2025 which was my last successful push.

4

ok, tried a Github site with curl and the -L option - both “git” and “curl” give me this error:
TLS connect error: error:00000000:lib(0)::reason(0)

cURL verbose output is:

> curl -v -L https://github.com/Genio-The-Haiku-IDE/Genio.git
* Host github.com:443 was resolved.
* IPv6: (none)
* IPv4: 140.82.121.4
*   Trying 140.82.121.4:443...
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /packages/curl-8.13.0-2/ca_root_certificates/data/ssl/CARootCertificates.pem
*  CApath: none
* TLS connect error: error:00000000:lib(0)::reason(0)
* OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to github.com:443 
* closing connection #0
curl: (35) TLS connect error: error:00000000:lib(0)::reason(0)

syslog contains no error during this time and shows the network connection is just fine:

DAEMON 'DHCP':   server: 192.168.0.1
DAEMON 'DHCP':   lease time: 86400 seconds
DAEMON 'DHCP':   renewal time: 43200 seconds
DAEMON 'DHCP':   rebinding time: 75600 seconds
DAEMON 'DHCP':   subnet: 255.255.255.0
DAEMON 'DHCP':   broadcast: 192.168.0.255
DAEMON 'DHCP':   gateway: 192.168.0.1
DAEMON 'DHCP':   nameserver[0]: 192.168.0.1
DAEMON 'DHCP':   domain name: "telekom.ip"
DAEMON 'DHCP': /dev/net/iaxwifi200/0: DHCP status = No error

So my root cert seems to be the issue - how to fix this on Haiku?

5

also getting this when trying to wget a working web resource:

OpenSSL: error:0A000126:SSL routines::unexpected eof while reading
Unable to establish SSL connection
6

Is your system date set correctly?

7

yes it is. Good point though, that had bitten me in the past sometimes;-)

8

Ok so I reinstalled Haiku (just installed the latest nightly from last night, hrev58829 over my current installation) and everyhing works perfectly again, using my old settings - same DNS, same Haiku repo URL etc.

Guess something was off with the nightly I had, or something went wrong when upgrading my system then, or my SSH key / root cert was updated to a sane current one with the manual upgrade.

2 Likes
9

haha the story continues but I’ve nailed it down now I think.

So after successfully updating my nightly from yesterday with SoftwareUpdater today, I was back to the same old connectivity issues again.

There were 2 suspects:

  1. iaxwifi200 driver got a firmware update
  2. new root certificates (well, at least from last November) were installed

I could rule out #1 with booting back into the old working state (thanks to packagefs:-) and checking that the log is the same and the dirver is binary equivalent.

So this leaves me with option 2 - seems the new root certs don’t work here as well as the older ones from July 2024…

The old working package is:
ca_root_certificates-2024_07_02-1-any.hpkg

vs the new one is:
ca_root_certificates-2024_11_26-1-any.hpkg

Since basic network connectivity works and shows the same log, including DHCP, for both installation states, it must be the certificates.

1 Like