On 06/18/2015 10:35 AM, Patrik Flykt wrote: > On Thu, 2015-06-18 at 13:48 +0530, Sukanya Ch wrote: >> With these changes I am not able to run connman daemon..Here I am >> providing >> the logs. >> >> connmand[4691]: src/ipconfig.c:__connman_ipconfig_init() >> connmand[4691]: src/rtnl.c:__connman_rtnl_init() >> connmand[4691]: src/task.c:__connman_task_init() >> connmand[4691]: src/proxy.c:__connman_proxy_init() >> connmand[4691]: src/detect.c:__connman_detect_init() >> connmand[4691]: src/rtnl.c:connman_rtnl_register() rtnl 0xa2448 name >> detect >> connmand[4691]: src/session.c:__connman_session_init() >> connmand[4691]: src/notifier.c:connman_notifier_register() notifier >> 0xa2510 >> name session >> connmand[4691]: src/firewall.c:__connman_firewall_enable() mangle >> INPUT -j >> CONNMARK --restore-mark >> connmand[4691]: src/firewall.c:insert_managed_rule() table mangle add >> managed chain for INPUT >> connmand[4691]: src/iptables.c:__connman_iptables_new_chain() -t >> mangle -N >> connman-INPUT >> connmand[4691]: src/iptables.c:iptables_init() mangle >> connmand[4691]: src/iptables.c:iptables_add_chain() table mangle chain >> connman-INPUT >> connmand[4691]: src/iptables.c:__connman_iptables_insert() -t mangle >> -I >> INPUT -j connman-INPUT >> (null) v(null): Couldn't load target `standard':No such file or >> directory > > The above lines state only that connman logs errors, not that ConnMan is > unable to run. __connman_iptables_init() and __connman_firewall_init() > always return success, so if ConnMan stops running it happens later in > some other part of the code which is not visible above.
Something I had on my TODO list was to dynamically detect if iptables is available or not. Google indicates testing for /proc/net/ip_tables* should do the trick. _______________________________________________ connman mailing list connman@connman.net https://lists.connman.net/mailman/listinfo/connman
