Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionAntoni Segura Puimedon
2014-04-11 19:09:32 UTC
Description of problem:
When a bridge does not exist and the ifcfg file contains bridging_opts,
ifup-eth first creates the bridge doing:
brctl addbr <bridge_name>
Just after that it iterates through the bridging_opts echoing the values to
/sys/class/net/<bridge_name>/bridge/<key_name>
The problem is that when echoing the value to the bridge sysfs entries, those
entries will not yet exist, as some, like multicast_router are created after
the link is put up.
Version-Release number of selected component (if applicable):
initscripts-9.03.40-2.el6.x86_64
How reproducible: 100%
Steps to Reproduce:
1. Create a bridge named 'tar' with the following ifcfg-tar:
DEVICE=tar
ONBOOT=yes
TYPE=Bridge
DELAY=0
DEFROUTE=no
NM_CONTROLLED=no
BRIDGING_OPTS='multicast_router=0 multicast_snooping=0'
2. Do 'ifup tar'
3. cat /sys/class/net/tar/bridge/multicast_router
Actual results:
1
Expected results:
0
Additional info:
Adding an 'ip link set dev ${DEVICE} up' solves it for me.
***************
*** 62,67 ****
--- 62,68 ----
[ -n "${DELAY}" ] && /usr/sbin/brctl setfd ${DEVICE} ${DELAY}
[ -n "${STP}" ] && /usr/sbin/brctl stp ${DEVICE} ${STP}
# add the bits to setup driver parameters here
+ ip link set dev ${DEVICE} up
for arg in $BRIDGING_OPTS ; do
key=${arg%%=*};
value=${arg##*=};
Comment 1Antoni Segura Puimedon
2014-04-11 19:10:54 UTC
The code looks the same in fedora, so it happens the same.
Is it completely safe to take the bridge up (with its default options set) and only later tweak them? (I have flawed STP values in mind)
I'm not sure about the consequence, but please consider re-applying the options after the bridge is up, so that both pre-up and post-up options take effect.
By the way bridge-utils have the same problem
[root@localhost ~]# brctl setmcrouter tar 0; echo $?
0
[root@localhost ~]# cat /sys/class/net/tar/bridge/multicast_router
1
Comment 6Antoni Segura Puimedon
2014-04-14 17:16:04 UTC
It is because certain opts you can only set when the bridge is up, isn't it?
Since the fixup patch is tiny, and the bug's resolution is anticipated by a RHEV-3.5 customer, can supporting multicast_snooping be granted exception+?
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2014-1448.html
Comment 18Charles R. Anderson
2015-01-16 22:57:44 UTC
(In reply to Lukáš Nykrýn from comment #10)
> https://git.fedorahosted.org/cgit/initscripts.git/commit/?h=rhel6-
> branch&id=32a67116ad1b2f058d9724b5205a859f01dca7a3
This problem still happens for me, even with the initscripts patch included. Upon initial bootup BRIDGING_OPTS="multicast_snooping=0" doesn't get applied. Doing another "ifup br0" manually afterwards works.
The patch should be modified to also apply "multicast_snooping", not just "multicast_router" and "hash_max".
Description of problem: When a bridge does not exist and the ifcfg file contains bridging_opts, ifup-eth first creates the bridge doing: brctl addbr <bridge_name> Just after that it iterates through the bridging_opts echoing the values to /sys/class/net/<bridge_name>/bridge/<key_name> The problem is that when echoing the value to the bridge sysfs entries, those entries will not yet exist, as some, like multicast_router are created after the link is put up. Version-Release number of selected component (if applicable): initscripts-9.03.40-2.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. Create a bridge named 'tar' with the following ifcfg-tar: DEVICE=tar ONBOOT=yes TYPE=Bridge DELAY=0 DEFROUTE=no NM_CONTROLLED=no BRIDGING_OPTS='multicast_router=0 multicast_snooping=0' 2. Do 'ifup tar' 3. cat /sys/class/net/tar/bridge/multicast_router Actual results: 1 Expected results: 0 Additional info: Adding an 'ip link set dev ${DEVICE} up' solves it for me. *************** *** 62,67 **** --- 62,68 ---- [ -n "${DELAY}" ] && /usr/sbin/brctl setfd ${DEVICE} ${DELAY} [ -n "${STP}" ] && /usr/sbin/brctl stp ${DEVICE} ${STP} # add the bits to setup driver parameters here + ip link set dev ${DEVICE} up for arg in $BRIDGING_OPTS ; do key=${arg%%=*}; value=${arg##*=};