Bug 22014

Summary:	Couldn't write '0' to 'net/bridge/bridge-nf-call-arptables' message at boot time
Product:	Mageia	Reporter:	Christian C <bugzzzz>
Component:	RPM Packages	Assignee:	Base system maintainers <basesystem>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, ouaurelien
Version:	6
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Christian C 2017-11-12 17:54:46 CET

Description of problem:
When booting my laptop, the first messages displayed in /var/log/messages are :

rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="855" x-info="http://www.rsyslog.com"] start
mtp-probe: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-6"
systemd-sysctl[509]: Couldn't write '0' to 'net/bridge/bridge-nf-call-arptables', ignoring: No such file or directory
mtp-probe: checking bus 3, device 3: "/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.1"
systemd-sysctl[509]: Couldn't write '0' to 'net/bridge/bridge-nf-call-iptables', ignoring: No such file or directory
mtp-probe: checking bus 3, device 4: "/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.2"
systemd-sysctl[509]: Couldn't write '0' to 'net/bridge/bridge-nf-call-ip6tables', ignoring: No such file or directory

So it seems that there are problems with arptables, iptables and ip6tables !
How could I fix them ?

# uname -r
4.9.56-desktop-1.mga6


Version-Release number of selected component (if applicable):


How reproducible:
At each boot

Steps to Reproduce:
1. boot the PC
2.
3.

Comment 1 Marja Van Waes 2017-11-12 18:22:00 CET

This report is beyond my understanding, assigning to the base system maintainers, who'll understand better what's going on and which application is the culprit.

Assignee: bugsquad => basesystem
CC: (none) => marja11

Comment 2 Christian C 2017-11-13 00:41:05 CET

I looked into the internet before posting and it seems that this bug have been known for several years :
https://bugzilla.redhat.com/show_bug.cgi?id=1264588
but no solution have been proposed for the moment.

Comment 3 Aurelien Oudelet 2020-08-02 22:27:12 CEST

In mentioned Redhat bugzilla, bug is closed as "default filtering of bridge packets has been deprecated in the kernel".

See also: https://bugzilla.redhat.com/show_bug.cgi?id=634736

Also, This message is a reminder that Mageia 6 is end of life.

Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL).

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 6's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot 
be able to fix it before Mageia 6 was end of life.
If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

CC: (none) => ouaurelien
Status: NEW => RESOLVED
Resolution: (none) => OLD