I'm experiencing something unusual.
A device of mine, running Armbian, cannot communicate with an Android device in my LAN. Otherwise everything else works.
My Orange Pi Zero 2w running Armbian can ping all of my LAN IPs (and access theyre net services also) , but fails at pinging an Android device (which is connected through WiFi): "Destination Host Unreachable".
Same goes the other way around where Termux runs on the above mentioned Android 15 device but cannot ping ("Destination Host Unreachable") the host running Armbian or access it via ssh (it simply stalls).
Everything else works just fine, all of my devices connect with each other without a glitch; they can all access every other running ssh instance inside the lan (which is a mix of Windows, Linux and Android devices).
The very same Orange Pi Zero 2w running Armbian is perfectly accessible via ssh from all other hosts and vice versa.
The Android device running Termux is capable of pinging and accessing all other ssh hosts.
And there's more; I'm running Wireguard on the Orange Pi and it works fine. it works so good that once I access the lan with the Android Device through Wireguard, I can suddenly ping the Armbian host and ssh login into it.
Always using the very same IP address (no dns involved).
I wonder where I should look. I cannot imagine what's causing it.
Any suggestions? Is this a known scenario?
ArmBian Community running on Orange Pi Zero 2w
v26.2 rolling for Orange Pi Zero2W running Armbian Linux 6.12.71-current-sunxi64
Packages: Debian stable (trixie)
Android 15 running Termux
Android REL 15 aarch64
Linux 5.10.236-android12-9-00020
Termux googleplay.2026.02.11
There's no WiFi separation on the router side.
I'm experiencing something unusual. A device of mine, running Armbian, cannot communicate with an Android device in my LAN. Otherwise everything else works. My Orange Pi Zero 2w running Armbian can ping all of my LAN IPs (and access theyre net services also) , but fails at pinging an Android device (which is connected through WiFi): "Destination Host Unreachable". Same goes the other way around where Termux runs on the above mentioned Android 15 device but cannot ping ("Destination Host Unreachable") the host running Armbian or access it via ssh (it simply stalls). Everything else works just fine, all of my devices connect with each other without a glitch; they can all access every other running ssh instance inside the lan (which is a mix of Windows, Linux and Android devices). The very same Orange Pi Zero 2w running Armbian is perfectly accessible via ssh from all other hosts and vice versa. The Android device running Termux is capable of pinging and accessing all other ssh hosts. And there's more; I'm running Wireguard on the Orange Pi and it works fine. it works so good that once I access the lan with the Android Device through Wireguard, I can suddenly ping the Armbian host and ssh login into it. Always using the very same IP address (no dns involved). I wonder where I should look. I cannot imagine what's causing it. Any suggestions? Is this a known scenario? ArmBian Community running on Orange Pi Zero 2w v26.2 rolling for Orange Pi Zero2W running Armbian Linux 6.12.71-current-sunxi64 Packages: Debian stable (trixie) Android 15 running Termux Android REL 15 aarch64 Linux 5.10.236-android12-9-00020 Termux googleplay.2026.02.11 There's no WiFi separation on the router side.