| 619a511d4f5b5cc74b9a8ab853db386489e02e6f |
|
19-Jan-2017 |
Jeff Sharkey <jsharkey@android.com> |
StrictMode to detect untagged network traffic.
Network usage is tracked by the kernel at the UID level, which is
granular enough for normal apps, but large components (such as the
system server) are impossible to debug without adding additional
socket tagging to help identify subsystems within a UID.
To help ensure that system components tag all their network traffic,
this change offers a new StrictMode option to detect and report
untagged sockets.
Test: builds, boots, all common traffic tagged
Bug: 30943431, 30414041
Change-Id: I825c7941076054732264690247de2863342638e2
/frameworks/base/services/core/java/com/android/server/connectivity/NetworkDiagnostics.java
|
| a09b4d2a611a7606e8fc8c73a24bd941b6fc173f |
|
15-Apr-2016 |
Narayan Kamath <narayan@google.com> |
Remove unnecessary allocation+unboxing of objects.
Transforming String->int can be done with 0 allocations
using Integer.parseInt.
bug: 28078871
Change-Id: I8d9f322d7154728849dde61ef282046032858d60
/frameworks/base/services/core/java/com/android/server/connectivity/NetworkDiagnostics.java
|
| 106cdf6c94c455462316555b7ac59ec79c3b40fa |
|
03-Feb-2016 |
Erik Kline <ek@google.com> |
Expose measurement results to interested callers.
With this it's possible for callers to:
Network network = ...
LinkProperties lp = ...
NetworkDiagnostics netdiag = new NetworkDiagnostics(network, lp, 5000);
netdiag.startMeasurements();
netdiag.waitForMeasurements();
boolean result = true;
for (Measurement m : netdiag.getMeasurements()) {
if (!m.checkSucceeded()) {
result = false;
// Additional error handling here.
}
}
return result;
Bug: 21832299
Bug: 26780890
Change-Id: Iaf7ff029e2c6a998b574c23d0dcde8d57a467a22
/frameworks/base/services/core/java/com/android/server/connectivity/NetworkDiagnostics.java
|
| 29f666688d73dcaf3f65b8124f34841927f70186 |
|
09-Sep-2015 |
Lorenzo Colitti <lorenzo@google.com> |
NetworkDiagnostics: ping default router from all global addreses.
This will hopefully allow us to determine if the router does not
have our global addresses in its neighbour cache.
Bug: 23661687
Change-Id: I46734c3c719003939cfccf038457ec309a9ff967
/frameworks/base/services/core/java/com/android/server/connectivity/NetworkDiagnostics.java
|
| 87cfc70b732422d6927ad9fe97f1ad7ab65fd508 |
|
27-Jul-2015 |
Lorenzo Colitti <lorenzo@google.com> |
Always check off-link connectivity in NetworkDiagnostics.
Currently, NetworkDiagnostics only checks off-link connectivity if
one of the DNS servers is off-link. Make it check off-link
connectivity in all cases by sending probes to Google Public DNS
if off-link DNS servers are not specified.
Bug: 22569331
Bug: 22641669
Bug: 22748900
Change-Id: I6cb0dd8491bc0c1a488631deca56722b9c1d2b3f
/frameworks/base/services/core/java/com/android/server/connectivity/NetworkDiagnostics.java
|
| ed1b45968edb11ce8dc5c1d5a5db09d943e8d425 |
|
24-Jun-2015 |
Erik Kline <ek@google.com> |
Don't lose critical success/failure messages
Occasionally, "dumpsys connectivity --diag" will show measurement
results without success or failure messages. Properly record the
error before decrementing the countdown latch.
Bug: 20733156
Change-Id: Ic654dedb753a65a96fe870f79fb296fbfc459fcb
/frameworks/base/services/core/java/com/android/server/connectivity/NetworkDiagnostics.java
|
| 379747a4040118130ca35947aef6942b2cd1cd67 |
|
05-Jun-2015 |
Erik Kline <ek@google.com> |
initial revision of NetworkDiagnostics
Bug: 21449922
Change-Id: I6a66cfa98601d6ccfe38ff840b0dd49ed1538a41
/frameworks/base/services/core/java/com/android/server/connectivity/NetworkDiagnostics.java
|