08c7116ab9cd04ad6dd3c04aa1017237e7f409ac |
|
28-Feb-2015 |
John Spurlock <jspurlock@google.com> |
Remove unused imports in frameworks/base. Change-Id: I031443de83f93eb57a98863001826671b18f3b17
/frameworks/base/services/core/java/com/android/server/connectivity/Nat464Xlat.java
|
7f6c0d7d2d5ad9e9f316300ce06f27d8492b05cd |
|
11-Nov-2014 |
Lorenzo Colitti <lorenzo@google.com> |
Populate 464xlat LinkProperties only when the interface comes up. Currently Nat464Xlat reads the clat IPv4 address and updates the clat LinkProperties when the interface is created. This causes a race condition: because clatd only sets the IPv4 address after creating the interface, it's possible that Nat464Xlat will read the address before clatd has set it, causing the framework to think that the clat IPv4 address is 0.0.0.0/32. This seems to be happening more frequently now, perhaps because clatd takes a bit longer to configure the IPv4 address now that it needs to check that the address is free before using it. Fix this by making Nat464Xlat listen for the interface coming up instead of listening for the interface being added. Bug: 12111730 Change-Id: Ic1c59b5b6dbb851b7431d1b06885f67803373bb9
/frameworks/base/services/core/java/com/android/server/connectivity/Nat464Xlat.java
|
dc6690867bbe839bbabddd9d7d5e4ec887a2bfee |
|
28-Oct-2014 |
Lorenzo Colitti <lorenzo@google.com> |
Enable 464xlat on wifi. Bug: 12111730 Change-Id: If6d118a3c6e163262b09cc2fb3e3d3f9a81986ec
/frameworks/base/services/core/java/com/android/server/connectivity/Nat464Xlat.java
|
e21a26b3ba78b0238f4ed4a09b43319a2320fbaa |
|
28-Oct-2014 |
Lorenzo Colitti <lorenzo@google.com> |
Add support for running 464xlat on wifi as well. 1. Add a command to NetworkManagementService to enable/disable IPv6 ND offload via netd. 2. Make Nat464Xlat enable offload if clatd successfully comes up on a wifi network (which means it detected a NAT64), and correspondingly re-enable offload when the clatd interface goes down. This change does not enable clatd on wifi yet, that requires an extra 2 lines to enable it. Bug: 12111730 Change-Id: I4318611762a37487c9a84f8c4867ec5aece98be8
/frameworks/base/services/core/java/com/android/server/connectivity/Nat464Xlat.java
|
954394653dad05838235f48244a4320893e0f0cf |
|
09-Oct-2014 |
Lorenzo Colitti <lorenzo@google.com> |
Support more than one clatd at a time. 1. Make Nat464Xlat a per-network object, one for every network requiring clat, instead of a ConnectivityService singleton. 2. Make the NetworkManagementService clatd commands take an interface. 3. When we attempt to start clatd on a network, store its Nat464Xlat object in the NetworkAgentInfo, so we have an authoritative way of knowing whether clat is running on a given network. 4. Rework Nat464Xlat, hopefully simplifying it. Bug: 12111730 Change-Id: I1fa5508ef020cd1c3d1c7a1f7b06370ac5fc2ae2
/frameworks/base/services/core/java/com/android/server/connectivity/Nat464Xlat.java
|
f3cab63ef2248aebf2c931cd1e84d5739791fa50 |
|
20-Oct-2014 |
Lorenzo Colitti <lorenzo@google.com> |
Change removeStackedLink to take an interface name. This simplifies callers. Also remove all "implementations" of addStackedLink and removeStackedLink except the one in LinkProperties, because they are unused. Bug: 12111730 Change-Id: Ie294b855facba4b1436299dcb3211b72d9ba448e
/frameworks/base/services/core/java/com/android/server/connectivity/Nat464Xlat.java
|
1df5fa55c5a5c1ba054b783ea639c99d57c357cf |
|
20-Sep-2014 |
Lorenzo Colitti <lorenzo@google.com> |
Only stop/start clatd if necessary. Previously we would restart clatd on every LinkProperties change, which now happens every time we switch radio technology (e.g., LTE to HSPA). We also would not stop it if the link got an IPv4 address. Bug: 15024258 Bug: 17186694 Bug: 17569702 Change-Id: I65cfcd5e7acec8ea1a12392a59dabd668c58490f
/frameworks/base/services/core/java/com/android/server/connectivity/Nat464Xlat.java
|
43b76dfddbfe2a27a0658dbca8632a9b1dc8d6ff |
|
16-May-2014 |
Lorenzo Colitti <lorenzo@google.com> |
Stop clatd when starting the Nat464Xlat service. If a runtime restart happens while clatd was running, we try to start clatd, which causes a fatal exception because netd returns a 400 error (clatd already started. Bug: 13450716 Bug: 15012035 Change-Id: I102a06d6193fb5f4a1ebe5ad52e5647ff72ca0da
/frameworks/base/services/core/java/com/android/server/connectivity/Nat464Xlat.java
|
3b75982e39ed9370153ae7f238f1d6041b9506ed |
|
13-May-2014 |
Paul Jensen <pauljensen@google.com> |
Get clatd/Nat464Xlat working with new NetworkAgents. Change-Id: I65dfb59ce519a42bdb872940d229039b5403fd92
/frameworks/base/services/core/java/com/android/server/connectivity/Nat464Xlat.java
|
9158825f9c41869689d6b1786d7c7aa8bdd524ce |
|
22-Nov-2013 |
Amith Yamasani <yamasani@google.com> |
Move some system services to separate directories Refactored the directory structure so that services can be optionally excluded. This is step 1. Will be followed by another change that makes it possible to remove services from the build. Change-Id: Ideacedfd34b5e213217ad3ff4ebb21c4a8e73f85
/frameworks/base/services/core/java/com/android/server/connectivity/Nat464Xlat.java
|