Bug#813580: [Pkg-netfilter-devel] Bug#813580: Bug#813580: No Internet Connection with iptables-1.6.0-2

2016-02-04 Thread Tsu Jan
On Thu, 4 Feb 2016 08:51:57 +0100 Arturo Borrero Gonzalez 
 wrote:

> Hi Tsu,
>
> I would need you to provide additional info about this bug:
> * connman config
> * connman service systemd detailed log
> * connman own log? (if exists)
> * kernel log (the dmesg one)
> * iptables service systemd detailed log (if exists)
> * iptables ruleset (from iptables-save)
>
> thanks
> --
> Arturo Borrero González
>
>
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)?


I haven't changed connman config -- it's the default Debian one.

I saved journalctl output before downgrading connman and iptables and 
there was no iptable line in it but its connman lines were so:


Feb 03 14:20:51 debian systemd[1]: connman.service: Main process exited, 
code=exited, status=1/FAILURE


Feb 03 14:20:51 debian systemd[1]: connman.service: Unit entered failed 
state.


Feb 03 14:20:51 debian systemd[1]: connman.service: Failed with result 
'exit-code'.


Feb 03 14:20:51 debian systemd[1]: connman.service: Service hold-off 
time over, scheduling restart.






Feb 03 14:20:57 debian systemd[1]: connman.service: Failed with result 
'start-limit'.


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.


Thanks, Tsu


-- Logs begin at Thu 2016-02-04 13:43:28 IRST, end at Thu 2016-02-04 14:25:05 
IRST. --
Feb 04 13:43:28 debian kernel: Initializing cgroup subsys cpuset
Feb 04 13:43:28 debian kernel: Initializing cgroup subsys cpu
Feb 04 13:43:28 debian kernel: Initializing cgroup subsys cpuacct
Feb 04 13:43:28 debian kernel: Linux version 4.3.0-1-amd64 
(debian-ker...@lists.debian.org) (gcc version 5.3.1 20160114 (Debian 5.3.1-6) ) 
#1 SMP Debian 4.3.3-7 (2016-01-19)
Feb 04 13:43:28 debian kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-4.3.0-1-amd64 root=/dev/sda5
Feb 04 13:43:28 debian kernel: x86/fpu: xstate_offset[2]: 0240, 
xstate_sizes[2]: 0100
Feb 04 13:43:28 debian kernel: x86/fpu: Supporting XSAVE feature 0x01: 'x87 
floating point registers'
Feb 04 13:43:28 debian kernel: x86/fpu: Supporting XSAVE feature 0x02: 'SSE 
registers'
Feb 04 13:43:28 debian kernel: x86/fpu: Supporting XSAVE feature 0x04: 'AVX 
registers'
Feb 04 13:43:28 debian kernel: x86/fpu: Enabled xstate features 0x7, context 
size is 0x340 bytes, using 'standard' format.
Feb 04 13:43:28 debian kernel: x86/fpu: Using 'eager' FPU context switches.
Feb 04 13:43:28 debian kernel: e820: BIOS-provided physical RAM map:
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0x-0x0009c7ff] usable
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0x0009c800-0x0009] reserved
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0x000e-0x000f] reserved
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0x0010-0xb9862fff] usable
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xb9863000-0xb9869fff] ACPI NVS
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xb986a000-0xba0e3fff] usable
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xba0e4000-0xba383fff] reserved
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xba384000-0xc98c7fff] usable
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xc98c8000-0xc9ad0fff] reserved
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xc9ad1000-0xc9e02fff] usable
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xc9e03000-0xcab07fff] ACPI NVS
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xcab08000-0xcaffefff] reserved
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xcafff000-0xcaff] usable
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xcbc0-0xcfdf] reserved
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xf800-0xfbff] reserved
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xfec0-0xfec00fff] reserved
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xfed0-0xfed03fff] reserved
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xfed1c000-0xfed1] reserved
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xfee0-0xfee00fff] reserved
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0xff00-0x] reserved
Feb 04 13:43:28 debian kernel: BIOS-e820: [mem 
0x0001-0x00032f1f] usable
Feb 04 13:43:28 debian kernel: NX (Execute Disable) protection: active
Feb 04 

Bug#813580: [Pkg-netfilter-devel] Bug#813580: Bug#813580: No Internet Connection with iptables-1.6.0-2

2016-02-03 Thread Arturo Borrero Gonzalez
Control: tags -1 moreinfo

On 3 February 2016 at 14:09, Tsu Jan  wrote:
> On Wed, 3 Feb 2016 13:00:24 +0100 Arturo Borrero Gonzalez
>  wrote:
>> On 3 February 2016 at 12:13, Tsu Jan  wrote:
>> You were using connman? Or are you using iptables rules directly?
>> Which version of connman are you running?
>> --
>> Arturo Borrero González
>>
>
> Yes, I use connman, which was upgraded alongside iptables from v1.21-1.2+b1
> to v1.21-1.2+b2 (rebuild against libxtables11).
>
> Downgrading connman alone didn't fix the issue, although I had libxtables10
> too.
>


Hi Tsu,

I would need you to provide additional info about this bug:
* connman config
* connman service systemd detailed log
* connman own log? (if exists)
* kernel log (the dmesg one)
* iptables service systemd detailed log (if exists)
* iptables ruleset (from iptables-save)

thanks
-- 
Arturo Borrero González