Bug 17404 - The kernel module "ipt_netflow" doesn't compile
Summary: The kernel module "ipt_netflow" doesn't compile
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA6-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2015-12-27 18:27 CET by rexy
Modified: 2018-09-21 18:27 CEST (History)
7 users (show)

See Also:
Source RPM: ipt_NETFLOW-1.8-9.mga6
CVE:
Status comment:


Attachments

Description rexy 2015-12-27 18:27:41 CET
Description of problem:
The version of "ipt_netflow" which is in the Mageia repositories (V5 & cauldron) doesn't compile.

With the last 'GIT' version of "ipt-netflow" the compilation is ok and the kernel module works fine on Mageia5 (https://github.com/aabc/ipt-netflow).

It would be very interesting to update this package to the last version :
 - IPFIX V5, 9 & 10
 - DKMS compatibility
 - Kernel 4.X compatibility

Rexy

Reproducible: 

Steps to Reproduce:
David Walser 2015-12-28 16:14:01 CET

Assignee: bugsquad => pterjan

Pascal Terjan 2016-01-07 20:09:15 CET

Status: NEW => ASSIGNED

Comment 2 Marja Van Waes 2018-04-24 18:59:38 CEST
Hi rexy,

Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

CC: (none) => marja11

Comment 3 rexy 2018-04-25 23:19:41 CEST
Need to be update to 2.3

Version: 5 => Cauldron

Comment 4 Marja Van Waes 2018-04-26 09:29:19 CEST
(In reply to rexy from comment #3)
> Need to be update to 2.3

CC'ing the kernel & driver maintainer group.

CC: (none) => kernel
Source RPM: ipt_NETFLOW-1.8-8.mga5.src.rpm => ipt_NETFLOW-1.8-9.mga6

Marja Van Waes 2018-04-26 09:29:25 CEST

Summary: The kernel module "ipt_netflow" doesn't compil => The kernel module "ipt_netflow" doesn't compile

Comment 5 Thomas Backlund 2018-09-08 02:10:59 CEST
Cauldron and Mga6 updated to 2.3 for new kernel support...


SRPM:
ipt_NETFLOW-2.3-1.mga6.src.rpm

i586:
dkms-ipt_NETFLOW-2.3-1.mga6.noarch.rpm
iptables-NETFLOW-2.3-1.mga6.i586.rpm

x86_64:
dkms-ipt_NETFLOW-2.3-1.mga6.noarch.rpm
iptables-NETFLOW-2.3-1.mga6.x86_64.rpm

Version: Cauldron => 6
CC: (none) => tmb
Assignee: pterjan => qa-bugs

Comment 6 Len Lawrence 2018-09-08 10:16:06 CEST
Tried installing earlier version from Release.
dkms kicked in but failed to compile and install iptables-NETFLOW.

Instructed to compile against the running kernel so rebooted and watched it build during the boot process.

Updated from Updates Testing.
The DKMS build succeeded.

$ rpm -qa | grep NETFLOW
dkms-ipt_NETFLOW-2.3-1.mga6
iptables-NETFLOW-2.3-1.mga6

CC: (none) => tarazed25
Whiteboard: (none) => MGA6-64-OK

Comment 7 Thomas Andrews 2018-09-21 03:48:47 CEST
That should be enough. Validating.

Keywords: (none) => validated_update
CC: (none) => andrewsfarm, sysadmin-bugs

Dave Hodgins 2018-09-21 17:29:25 CEST

Keywords: (none) => advisory
CC: (none) => davidwhodgins

Comment 8 Mageia Robot 2018-09-21 18:27:30 CEST
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2018-0153.html

Resolution: (none) => FIXED
Status: ASSIGNED => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.