Control: reassing -1 connman Control: severity -1 important On 4 February 2016 at 12:29, Tsu Jan <tsujan2...@gmail.com> wrote: >> > Hi, > > My bad! I had another Debian with network-manager instead of connman. Last > night I had time to upgrade it and no problem occurred. So, this is about > connman and not iptables. Apparently, building connman-1.21 against > libxtables11 wasn't enough for it to work with iptables-1.6.0. > > Should I write another bug report or you could reassign this one to connman > (with high severity)?
Yeah, doing so now. > > I've attached my current iptables-save and dmesg logs. Sorry, I couldn't > find the logs related to that specific boot and I can't upgrade now to > reproduce the issue because this is my work system. > For the record, the ruleset you shared was generated with a previous version of iptables? the file contains: Generated by iptables-save v1.4.21 on Thu Feb 4 14:14:09 2016 Your dmesg contains logs from iptables, which indicates that the ruleset was loaded to the kernel, and it is seing traffic. Anyway, this bug is now in the connman side. I'm open to whatever help is required on my side. best regards. -- Arturo Borrero González
