OSDN Git Service

Manage NAT64 prefix discovery lifecycle in the framework.
authorLorenzo Colitti <lorenzo@google.com>
Tue, 19 Feb 2019 04:21:56 +0000 (13:21 +0900)
committerLorenzo Colitti <lorenzo@google.com>
Tue, 26 Feb 2019 15:18:13 +0000 (00:18 +0900)
commitd593e298c66d1138240f8e97e92b8a5b8f9eb130
tree0e9e4094184f75c450d6a81fd527c338a74a3b62
parent6998fa8a17756b36d925446bb5e1f3ec4993200f
Manage NAT64 prefix discovery lifecycle in the framework.

Currently NAT64 prefix discovery, which runs in netd, is started
by netd itself when a network is programmed with all-IPv6 DNS
servers. Unfortunately this is not correct because in many cases
we program DNS servers before the network is connected and it's
actually possible to send packets to them.

In general netd does not have enough visibility into network
lifecycle management to decide when to start and stop prefix
discovery. So move it into the framework with the rest of the
464xlat control plane.

Bug: 65674744
Test: atest FrameworksNetTests
Change-Id: I8fa051a9c216d9c05082bf7d0bbb0cbd56000162
services/core/java/com/android/server/ConnectivityService.java
services/core/java/com/android/server/connectivity/Nat464Xlat.java
services/core/java/com/android/server/connectivity/NetworkAgentInfo.java
tests/net/java/com/android/server/ConnectivityServiceTest.java
tests/net/java/com/android/server/connectivity/Nat464XlatTest.java