Red Hat Bugzilla – Bug 1462410
firewallctl can't install ebtables rules
Last modified: 2017-12-12 05:36:35 EST
Description of problem:
I'm trying to make a brouter on my raspberry pi at home. Here is the "very" simplified architecture:
| br0 |------+ +--------------------+
+-------| | | | systemd-nspawn |
| +-------+ | | openvpn |
| | | |
| | | |
+---+----+ +-----+----------+ +--------+ |
| eth0 | | vb-vpngateway +---+ host0 | |
+--------+ +----------------+ +--------+ |
192.168.1.10 172.17.94.1/28 | 172.17.94.2/28 |
In order for ports belonging to the bridge to communicate between each other I need to put in place a bunch of ebtables rules...
I'm running Fedora Server edition. ebtables is installed and all modules are loaded correctly:
[lionel@raspberry ~]$ lsmod |grep ebt
ebt_arp 16384 2
ebt_ip 16384 2
ebtable_broute 16384 1
ebtable_nat 16384 1
ebtable_filter 16384 1
ebtables 24576 3 ebtable_filter,ebtable_nat,ebtable_broute
bridge 122880 1 ebtable_broute
And everything works fine when evoking ebtables command directly..
Version-Release number of selected component (if applicable):
Name : firewalld
Version : 0.4.4.4
Release : 1.fc25
Name : ebtables
Version : 2.0.10
Release : 21.fc25
Steps to Reproduce:
1. sudo firewallctl direct -p add rule eb broute BROUTING 1 '-p IPv4 -i eth0 --ip-dst 192.168.1.10 -j DROP'
2. sudo firewallctl reload
ebtables rule not installed in BROUTING on the broute table.
And in the log of firewalld I have:
raspberry firewalld: WARNING: '/usr/sbin/ebtables -t broute -I BROUTING_direct 1 -p IPv4 -i eth0 --ip-dst 192.168.1.10 -j DROP' failed:
ebtables rule is installed in BROUTING on the broute table.
If I installed the rules directly via the ebtables command, everything is working smoothly without any trouble. But once I reload the firewall, the ebtables rules I put in place manually are erased. Hope this will ring a bell to someone..
Did someone as already a hint ? This is really annoying for me..
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
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 Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
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 Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.