diff options
| author | Hugo Benichi <hugobenichi@google.com> | 2018-02-28 10:00:14 +0900 |
|---|---|---|
| committer | Hugo Benichi <hugobenichi@google.com> | 2018-03-01 09:32:21 +0900 |
| commit | 77660392eb3e9aa287cc02307c443ee64b5fc570 (patch) | |
| tree | 6ac2c38732b72efc07adad1a907b5f5f48982dfc /server/TetherControllerTest.cpp | |
| parent | 3ce916d29e06b93d1d0cbb9e87f7efd16e0dfb34 (diff) | |
WakeupController: remove --nflog-range
Trying to use the --nflog-range option for truncating packets received
with NFLOG does actually nothing and causes warnings to be printed by
IptablesRestoreController in netd.
The warning was added in https://patchwork.kernel.org/patch/9191269/
to iptables which also introduces a new XT_NFLOG_F_COPY_LEN
constant for passing down the packet copy len argument to the kernel
via a new --nflog-size option in iptables.
This patch removes the --nflog-range which is not necessary.
In reality WakeupController already specify a range argument when
subcribing to NFLOG using the NFLogListener interface in netd.
This sets the NFULNL_COPY_PACKET argument when doing the initial
Netlink request to NFLOG.
Bug: 73918721
Test: built, flashed, checked wakeup events are still correctly logged,
checked that warnings are not printed anymore.
Change-Id: I742aaecf8563d5e476805301e0435a412bb37e6a
Diffstat (limited to 'server/TetherControllerTest.cpp')
0 files changed, 0 insertions, 0 deletions