Hi, It's been a while users, including myself, have noticed the big amount of iptables related modules always being loaded at connman's startup. In a usage that, however, did not require those at all: - no tethering usage - no session usage
So here is a quick hack: - let's not flush any connman's chain if the modules are not loaded (so it means we are on a fresh start and nothing, even connman, has been using iptables) - same for nfacct, it initiates it when necessary only. @Daniel: can you check it's not breaking you session/policy runtime logic? Tomasz Bursztyka (2): firewall: Don't do anything with iptables until really necessary nfacct: Don't setup nfacct until it's relevant to do so src/connman.h | 3 +-- src/firewall.c | 21 ++++++++++++++++++++- src/main.c | 1 - src/nfacct.c | 20 +++++++------------- src/session.c | 20 +++++++++++++------- 5 files changed, 41 insertions(+), 24 deletions(-) -- 1.8.4.3 _______________________________________________ connman mailing list [email protected] https://lists.connman.net/mailman/listinfo/connman
