01-12-2025, 04:52 PM
@TheOldPresbyope
Thank you very much for your comments and the Airplay streaming test with your Pi 3A+.
I my setup the Pi 3 B+ is installed in the original HiFiBerry steel case. Basically, a steel housing shields the WLAN signal and creates a suboptimal environment for good signal strength, but in my case, this configuration has worked well for years
However, I suspect that my Airplay problem is related to the WLAN signal processing or hardware. In the meantime I also installed the moOde 9.2.2 image on a brand new SD card, but without any positive effect.
Some month ago I changed the 5 Ghz WLAN from Wi-Fi 4 (802.11 n, up to 800 Mbit/s) to Wi-Fi 5 (802.11 ac, up to 1733 Mbit/s). Because I don't really need the higher datarates of the Wi-Fi 5 network i changed it back to Wi-Fi 4. Maybe this is the root couse and will fix the problem. I also changed the location the Pi 3B+ a little bit and get a slightly better signal qualitiy. I will report if the symptoms had disappear after this change.
iwconfig returns:
ifconfig returns:
Best regards,
Stephan
Thank you very much for your comments and the Airplay streaming test with your Pi 3A+.
I my setup the Pi 3 B+ is installed in the original HiFiBerry steel case. Basically, a steel housing shields the WLAN signal and creates a suboptimal environment for good signal strength, but in my case, this configuration has worked well for years
However, I suspect that my Airplay problem is related to the WLAN signal processing or hardware. In the meantime I also installed the moOde 9.2.2 image on a brand new SD card, but without any positive effect.
Some month ago I changed the 5 Ghz WLAN from Wi-Fi 4 (802.11 n, up to 800 Mbit/s) to Wi-Fi 5 (802.11 ac, up to 1733 Mbit/s). Because I don't really need the higher datarates of the Wi-Fi 5 network i changed it back to Wi-Fi 4. Maybe this is the root couse and will fix the problem. I also changed the location the Pi 3B+ a little bit and get a slightly better signal qualitiy. I will report if the symptoms had disappear after this change.
iwconfig returns:
Code:
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11 ESSID:"DarknetB"
Mode:Managed Frequency:5.5 GHz Access Point: 98:9B:CB:12:74:DB
Bit Rate=150 Mb/s Tx-Power=31 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=51/70 Signal level=-59 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0ifconfig returns:
Code:
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether b8:27:eb:52:41:fe txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 3222 bytes 335329 (327.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3222 bytes 335329 (327.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.29 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fdbb:c7c4:4c6f:0:d91b:ad70:e453:e84e prefixlen 64 scopeid 0x0<global>
inet6 fe80::dbee:133:6524:81b3 prefixlen 64 scopeid 0x20<link>
inet6 2003:cb:4f01:f100:c8dc:2b37:a9e4:7b05 prefixlen 64 scopeid 0x0<global>
ether b8:27:eb:07:14:ab txqueuelen 1000 (Ethernet)
RX packets 8677 bytes 5853866 (5.5 MiB)
RX errors 0 dropped 914 overruns 0 frame 0
TX packets 11858 bytes 10200508 (9.7 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0Best regards,
Stephan
