From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 011771382C5 for ; Wed, 31 Jan 2018 22:44:10 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id ABAFCE0C15; Wed, 31 Jan 2018 22:44:02 +0000 (UTC) Received: from blaine.gmane.org (unknown [195.159.176.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 3B4E7E0AD5 for ; Wed, 31 Jan 2018 22:44:02 +0000 (UTC) Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1eh14G-0002kY-22 for gentoo-user@lists.gentoo.org; Wed, 31 Jan 2018 23:41:24 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Melleus Subject: [gentoo-user] Re: Connman refuses to work Date: Thu, 01 Feb 2018 00:43:04 +0200 Message-ID: <87tvv1sl8n.fsf@openmailbox.org> References: <87k1wvyxmx.fsf@openmailbox.org> <87bmi7yp4u.fsf@openmailbox.org> <20180106154314.5c4d3860@digimed.co.uk> <877esvyly6.fsf@openmailbox.org> <20180106183750.3a62a64d@digimed.co.uk> <87vageslwa.fsf@openmailbox.org> <87shbhd66b.fsf@openmailbox.org> <1c72b42f-477c-b435-6c28-0b8f592e4e08@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain X-Complaints-To: usenet@blaine.gmane.org User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) Cancel-Lock: sha1:sRBGLhICm61Nkgcb2sWl78isOc0= X-Archives-Salt: f5895956-1ed0-4a4d-be0f-09bbf63895b0 X-Archives-Hash: 64dfc423efabbbd84657b9ac737ce0dc Alan McKinnon writes: > On 07/01/2018 17:45, Melleus wrote: >> Melleus writes: >> >>> Neil Bothwick writes: >>> >>>> On Sat, 06 Jan 2018 18:46:25 +0200, Melleus wrote: >>>> >>>>>> What do the logs say? >>>>> That's all I could find in syslog: >>>>> >>>>> connmand[6709]: Aborting (signal 11) [/usr/sbin/connmand] >>>>> >>>>>> Can you start it manually? >>>>> >>>>> No, it pretends to start but fails silently. >>>> >>>> Looking at the man page, try adding --debug=DEBUG and --nodaemon >>> >>> Thank you for helping me. >>> >>> --debug=DEBUG is almost silent, but just --debug is more verbose. >>> >>> All I see is that something wrong is happening here: >>> >>> connmand[2434]: src/iptables.c:__connman_iptables_append() -t mangle -A connman-INPUT -j CONNMARK --restore-mark >>> connmand[2434]: Aborting (signal 11) [connmand] >> >> Thanks again for pointing me to logs. Those iptables was a >> problem. There are the closed bug #573174. Iptables higher than 1.6 >> breaks connman. The solution is to use iptables lower than 1.6 or >> connman higher than 1.32. So the combination of connman v1.29 and >> iptables v1.6.1-r2 just cannot work. But unfortunately for me they both >> have stable keyword. I beleive that this is a some kind of bug. >> After I masked iptables higher than 1.6, reemerged the packages and >> reboot, everything works like it should. >> >> I don't know whether developers are reading this thread, but it would be >> very nice to keyword only v1.4.21-r1 of iptables with stable keyword >> (like they have done with kernel recently) or promote to stable some >> version of connman higher than 1.32 upstream. This would completely >> have this bug eliminated even before someone other than me hits it. > > > Post your finding to b.g.o. > > It's a simple matter to limit which versions of iptables can be used > with each version of connman. Tracking that, and making changes when > they become known, is what being a package maintainer is all about. connman-1.35-r1 arrives to stable. So no need to tinker with iptables version anymore. The issue dissolved completely.