Android client trying to connect all over the place?!

My android client (v1.29.0 64-arm, build 2024-12-30) is set to connect using two relays on a specific port (e.g. relay://example.com?2200?id=relay1...) But when I look at one peer info, it has dozens of

tcp://<ip of example.com>:11081 i/o timeout
tcp://<ip of example.com>:14595 i/o timeout
tcp://<ip of example.com>:12545 i/o timeout
tcp://<ip of example.com>:45124 i/o timeout
tcp://<ip of example.com>:12341 i/o timeout

Why is it trying all those ports?

If I click on “Listeners”, quic://0 and tcp:/0 are up. One relay is up. One of the relays is up, but the one owning the dns for that IP keeps changing from UP and "timedout no context.

The two relays are exactly the same (running on openWRT but on different places)

It will often try lots of ports for a given device because it has reported a lot of ports, due to NAT, port mappings, etc.

it has never seen the device before…

is there any option to disable this? I think i turned off all the NAT options already.

More info that might be relevant. I restarted it via the GUI, and it shows a yellow notice

(!) Notice

Aborted scan due to an unexpected error: context canceled

…I actually think my &$^@&^$ ISP edge modem is blocking the mobile device from reaching the relay because it is hammering on too many ports too fast. Because it connects to the relay on the correct port, then starts to hammer the same IP to reach the devices, and gets disconnected from the relay too.

This doesn’t happen on the other site, where the only difference is the ISP and it’s edge router/modem.

This is so strange. Even after I move back from 5G to wifi and back into the lan, the GUI shows that the lan ip is unreachable (it still shows the same list of IPs and status from 5G, no matter if I restart)

edit: 3rd restart did the trick :slight_smile: now it only shows the lan IP and connected. But still would like to have this working on 5G/outside. I don’t think just hitting random ports makes any sense