299a81157c257a6b6bc9d41aef094fdfe8aadde7
Needed because a payload data packet may have gone through non-offload path, before we added offload rules, and that this may result in in-kernel conntrack state being in ESTABLISHED but pending ACK (ie. UNACKED) state. But the in-kernel conntrack might never see the ACK because we just added offload rules. As such after adding the rules we need to force the timeout back to the normal ESTABLISHED timeout of 5 days. Issue: the timeout is set to unacknowledged 300s (countdwon to 298s) $ adb shell cat /proc/net/nf_conntrack ipv4 2 tcp 6 298 ESTABLISHED src=192.168.244.128 dst=140.112.8.116 sport=45694 dport=443 .. Test: atest TetheringCoverageTests Manual check: $ adb shell cat /proc/net/nf_conntrack ipv4 2 tcp 6 431988 ESTABLISHED src=192.168.40.162 dst=140.112.8.116 sport=40774 dport=443 .. Bug: 190783768 Bug: 192804833 Change-Id: I8c34e85e26c9d976e5e2b85473db75ff46d8abd4
Description
android_packages_modules_Connectivity
Languages
Java
81.4%
Kotlin
7.7%
AIDL
4.5%
C++
4.5%
C
1.7%
Other
0.1%