-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
TCP connections fail on TUN only (Tun doesn't start properly half the time) #3010
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
i compared outputs of "iptables -S -t nat/mangle/filter", "ip route show table 0", "ip rule" between good and bad starts and there is no difference.
|
You may need a reboot |
this is happening for multiple months, reboot doesn't help, what information do i need to give? but the randomness changes over time: sometimes it doesn't start for multiple times, sometimes it works perfectly 5 times in a row |
it is very inconsistent, so i tested this way: deleted current version, rebooted, installed older apk, reboot, tried to use it, and im 90% sure that version 1.10.6 introduced this issue, but there is a weird thing: if i install the same version twice (just open the apk and agree to updating, works even with latest beta), it works fine until i reboot or force close the app from android settings |
I'm sorry but it looks like you lied about being a sponsor so I'll close this. |
sorry, i asked my friend to send crypto but he's delaying it for a week already, how much do you want for this? |
Uh oh!
There was an error while loading. Please reload this page.
Operating system
Android
System version
android 11 LOS on mi a3, android 10 miui on redmi 9a
Installation type
sing-box for Android Graphical Client
If you are using a graphical client, please provide the version of the client.
No response
Version
Description
sing-box TUN is inconsistent, sometimes it starts properly, sometimes it starts and all TCP connections fail (connection refused on curl), i have to stop/start sing-box to fix it (waiting doesn't help).
UDP over TUN works all the time.
TCP over SOCKS works all the time.
logcat: (log just before i press the start button, i don't see any difference between them)
bad.log.txt
good.log.txt
redundant logcats:
bad-1.log.txt
good-1.log.txt
bad-2.log.txt
good-2.log.txt
bad-3.log.txt
good-3.log.txt
good-4.log.txt
screenshots of bad start:
good start is the same but tcp connections are visible in the log
Reproduction
config: https://pastebin.com/QrZgaq26 (mtu 1500 or 9000, stack system or gvisor, ip 172.19.0.1/30 - same result)
start the config multiple times, 50% of the time internet will not be accessible.
only mobile data and only wifi give the same result.
Logs
Supporter
Integrity requirements
The text was updated successfully, but these errors were encountered: