Orbot keeps changing identity

[Pinkolik]

Hello! I'm working on a feature for an app where all other apps' traffic is redirected through Orbot proxy. But Orbot keeps changing exit node (identity) for some reason. Is it normal behavior? Can I prevent Orbot from doing that? Here's some logs

[n8fr8]

Tor is meant to create new circuits (which includes exits) after a certain amount of time... maybe 10 minutes. That shouldn't really matter to your app though... it would just look like a fresh IP address to the remote server. Do you need to keep a stable IP address for your app?

Otherwise, the log output you are showing above seems like a different problem. Is there some issue with your server blocking connections from Tor?

[n8fr8]

Okay, so first you capture traffic in the OpenVPN client. If it is NOT Tor, then you proxy that into the Tor SOCKS port. If it IS Tor, then you route that over the VPN?

Hmm, I have to think about this some more. Interesting idea though!

[n8fr8]

Could you instead detect the UID of the packets as the come in, and match that to Orbot? I think there are too many potential remote servers that tor connects to for you to figure it out based on destination.

[Pinkolik]

Could you instead detect the UID of the packets as the come in, and match that to Orbot? I think there are too many potential remote servers that tor connects to for you to figure it out based on destination.

That was my first implementation of this idea, I used getConnectionOwnerUid but it turned out to be a rather expensive operation to do on every packet, so I decided to use public nodes as a workaround to increase connection speed. By the way, even when I used to detect all Orbot traffic with getConnectionOwnerUid, I still had the same problem and same logs. Also, getConnectionOwnerUid only supports detecting TCP or UDP packets as well as my current implementation, could Orbot possibly use any other protocols which are not passed through?

[Pinkolik]

Okay, so first you capture traffic in the OpenVPN client. If it is NOT Tor, then you proxy that into the Tor SOCKS port. If it IS Tor, then you route that over the VPN?

Yep, that's right

[Pinkolik]

@n8fr8, @bitmold, any ideas?

[Pinkolik]

Just bumping this thread :)