Network regression on 2026062301

anegry

I updated to 2026062301 on my Pixel 8 Pro, a terminal app (Termux) can no longer reach a private address that's only routable over my WireGuard tunnel, ping returns sendmsg: Operation not permitted instantly and SSH to the same host times out, whereas this worked reliably before the update. The tunnel is up and carrying traffic for everything except terminal-originated connections. Is this a known regression in VPN-interface networking changes? Happy to capture logs during a failed attempt if that helps.

Thanks!

Kamika242

anegry a terminal app (Termux) can no longer reach a private address

Does this app have the new "Nearby devices" permission? If not, it might be the cause.

anegry

Kamika242 I don't see anything like that, but did review permissions and everything looks right.

psqueak1

anegry I second Kamika242 's advice.
Grant nearby permission to termux and see how this changes.

Also, when you have a vpn, the local traffic is managed by the vpn itself, so you might have another layer to check on your wireguard app (permissions and/or settings)

anegry

Hi, just wanted to share some more on this issue. I've tried two ssh clients (termux and termius) and neither works, while connectbot does. Looking at the release notes, I see that android 17 made changes to networking, and it's that particular update which broke my ssh. Is it possible support will be brought back for these other ssh clients? Thanks!

RideNFly_FPV

I have the same issue, but not just on vpn. Since the last update I cannot access anything on my lan from termux.

Johnnyloans

anegry

RideNFly_FPV

On termux and wireguard, deny nearby devices and network then allow both.
To get to this menu, hold down your finger on the app's icon for 2 seconds > app info > permissions

For issues connecting to a remote device over wireguard, review your wireguard config or even uninstall/reinstall wireguard.

Here is a picture of termux working on my LAN -- no wireguard
Then a 2nd test using wireguard and a remote device

https://imgur.com/a/1nJm4uk

I haven't had an issue with any A17 version. I'm on 2026062801 currently

anegry

Johnnyloans On my build (2026070501), Termux's Permissions screen has no Nearby devices entry at all, so there's nothing to grant, whereas ConnectBot shows it

Termux:https://imgur.com/a/Wnek4ZH
Connectbot: https://imgur.com/a/HuiiKkv

GrapheneOS

anegry Termux has a compatibility issue with Android 17 caused by prematurely updating the target API level without handling the new local network permission. It needs to be resolved by them.

Johnnyloans

anegry

Yours looks different than mine and not just nearby devices. You could try uninstalling then reinstalling termux. Backup files off of termux first.

My termux permissions
https://imgur.com/a/ngopH3x

I installed A17 first then I installed all of my apps, could be the reason why.