From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Connman refuses to work
Date: Sun, 7 Jan 2018 18:20:42 +0200 [thread overview]
Message-ID: <1c72b42f-477c-b435-6c28-0b8f592e4e08@gmail.com> (raw)
In-Reply-To: <87shbhd66b.fsf@openmailbox.org>
On 07/01/2018 17:45, Melleus wrote:
> Melleus <melleus@openmailbox.org> writes:
>
>> Neil Bothwick <neil@digimed.co.uk> 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.
--
Alan McKinnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2018-01-07 16:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-06 12:33 [gentoo-user] Connman refuses to work Melleus
2018-01-06 13:01 ` [gentoo-user] " Melleus
2018-01-06 13:40 ` [gentoo-user] " Rich Freeman
2018-01-06 15:37 ` [gentoo-user] " Melleus
2018-01-06 15:43 ` Neil Bothwick
2018-01-06 16:46 ` Melleus
2018-01-06 18:37 ` Neil Bothwick
2018-01-06 21:44 ` Melleus
2018-01-07 15:45 ` Melleus
2018-01-07 16:20 ` Alan McKinnon [this message]
2018-01-31 22:43 ` Melleus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1c72b42f-477c-b435-6c28-0b8f592e4e08@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox