WiFi stack seems to be killed & other strange network behavior
Beantwortet
Hope someone can help with a proper way to keep the WiFi stack running or a trick to only restart the Powernode WiFi stack or is there maybe an OS-update that fixes this? Does anyone know which requirements must be met to get this functioning (details below)?
Got a Powernode today. After some time the Powernode WiFi stack is killed and does not work anymore. Only way to get it working again is a reset and re-initialize of the Powernode. Naturally the app is working in the beginning but after the Powernode WiFi is malfunctioning the app is empty and nothing can be configured. The Powernode itself is functioning. I can play music via Bluetooth and watch/listen Apple TV/Blu-Ray via aARC. It's a pity, such an expensive, beautiful device and so much troubles.
When I say the WiFi stack is killed it's because no IP-traffic is coming from Powernode anymore. No ntp, no http 80/443, no trying to connect to link local addresses, nothing.
The WiFi stack shows itself as a 'Arcadyan Technology Corporation' component. The software tries to contact some odd IP-addresses, which I didn't allow at first:
Korean Republic, 103.243.201.15
Netherlands Antilles or Naaldwijk NL, 190.2.153.21, 190-2-153-21.hosted-by-worldstream.net
Reserved IP, Link local address 169.254.73.131
And also it tries to contact upgrade.nadelectronics.com (3.98.159.36) that uses a certificate from ca2.upgrade.bluos.net which I didn't allow at first because of the invalid certificate
ca2.upgrade.bluos.net (3.98.159.36) itself gets rating A on ssllabs (higher should be better, but it is ok-ish)
And this redirects to ec2-3-98-159-36.ca-central-1.compute.amazonaws.com
-
Offizieller Kommentar
When I bought a new Node2i at a local dealer a few years ago, it contained links to some services. So it was obviously a used device, showroom or so.
I don't know if this is your case but maybe the procedure to restore to factory settings can help.
https://support1.bluesound.com/hc/en-us/articles/200272046
-
Thanks Alain DW! I started with the reset after the first issues. It didn't help or showed other traffic patterns.
I'm sure the Wifi stack is the culprit here. I connected with a cable (looks nice over the living room floor!) and that helps. I learned that there are more people suffering from this. I already ordered a WiFi-bridge to get rid of the physical cable and see how that goes.
What I see now I have a proper connection the Arcadyan component is likely to be the 'hotspot' for initial configuration. What makes matters worse I also saw some CVEs for that specific 'hotspot' linux kernel that look serious (high & critical): CVE-2023-38432
CVE-2023-39191
CVE-2023-5345
CVE-2023-44466
CVE-2023-38431
CVE-2023-38426
CVE-2023-38428
CVE-2023-38429
CVE-2023-38430
CVE-2023-384270 -
Being a Linux user I wouldn't worry too much about these "vulnerabilities". There is an infinitesimally small risk since your are using the device in your home network and exposure to the internet is behind the firewall of your router.
Anyhow these things get solved with kernel updates when needed.
0 -
Don't know why something above is mentioned as an 'official comment' or why my initial post is marked 'answered' because nothing is answered yet.
@Alian, vulnerabilities wouldn't be that serious to me on their own but using an EOL linux version, communicating with Korea, not having proper certificate management in place, and having a wobly WiFi stack does not establish trust on my side.
The one thing that helps the original query is not using the WiFi stack at all. I connected a TP-Link AC750 TL-WR902AC in client mode to the Powernode rj45 connector and using the same SSID I had no problems anymore. As I do not have a direct cable in the vicinity of the set-up this is a mediocre solution. As this device is on an audition I'm going to look for other devices that serve my needs. It's a pitty because the sound is great. But a streamer must be able to stream!
1
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
4 Kommentare