summaryrefslogtreecommitdiffstats
path: root/server/TetherController.cpp
diff options
context:
space:
mode:
authorHungming Chen <nuccachen@google.com>2020-02-07 17:47:23 +0800
committerMaciej Żenczykowski <maze@google.com>2020-02-17 20:31:54 +0000
commit7f72543f4570259818d709fabc78c1b28296f783 (patch)
tree1754ab019d7519c547a07a8d8cda33c8df7865c4 /server/TetherController.cpp
parent52db3916eee87be7aae1038f5eaac13b03576d0b (diff)
downloadplatform_system_netd-7f72543f4570259818d709fabc78c1b28296f783.tar.gz
platform_system_netd-7f72543f4570259818d709fabc78c1b28296f783.tar.bz2
platform_system_netd-7f72543f4570259818d709fabc78c1b28296f783.zip
Move attaching and detaching clsact from ClatdController to RouteController
The clsact attaching and detaching control plane is moved to: RouteController::addInterfaceToPhysicalNetwork - add clsact RouteController::removeInterfaceFromPhysicalNetwork - del clsact The above change implies that the clsact lifetime for each interface has been extended from clat enabled time to interface lifetime. The only exception is that attaching clsact to v4- tun interface still lives in ClatdController. The reason is that clat is started before the v4- tun interface is added to the network and clat has already needed to add the bpf filters. After all, keep attaching and detaching clat {in, e}gress bpf filters in ClatdController. Test: manual clatd test 1. Connect to IPv6-Only WiFi hotspot 2. Browse 172.217.0.46 (google.com) successfully 3. Disconnect from WiFi Repeat the above steps three times. Change-Id: I971e105484c7678ac304788e5ffff7cc709c400d
Diffstat (limited to 'server/TetherController.cpp')
0 files changed, 0 insertions, 0 deletions