Fix networking on aarch64
Due to limitations in the Android build system, we currently build all
of the host tools as x86_64, and then use qemu-user to translate them to
aarch64 on the target device. However, qemu-user can't translate TUN
ioctls, so the tap devices are not correctly configured for crosvm and
networking is broken. This works around the problem by pushing the
critical configuration out of process.
The correct longer term fix for this problem is to modify crosvm to
accept tap devices by name; as we provide crosvm natively for aarch64,
no translation occurs, and crosvm can freely use the TUN ioctls.
Bug: 156322936
Change-Id: I9fba825324b037e907394064724e6adfab93c3ed
Merged-In: I9fba825324b037e907394064724e6adfab93c3ed
diff --git a/host_package.mk b/host_package.mk
index 24a5210..9a1d807 100644
--- a/host_package.mk
+++ b/host_package.mk
@@ -51,6 +51,7 @@
fsck.f2fs \
resize.f2fs \
make_f2fs \
+ tapsetiff
cvd_host_tests := \
monotonic_time_test \