Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 54155

Summary: Not all multicast addresses being registered w/ Broadcom NIC (bcm5700)
Product: [Retired] Red Hat Linux Reporter: Michael Brock <michael_brock>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED ERRATA QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-12-06 12:10:33 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
Test Scripts for multicast addresses problems with bcm5700 none

Description Michael Brock 2001-09-28 16:30:05 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)

Description of problem:
Server has 4 broadcom cards (bcm5700.o) and doesn't register all of the 
multicast addresses on the attached networks.  Some multicast addresses do 
get reserved, but others do not.  No consistancy as far as which addresses 
do or do not get reserved.

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

How reproducible:

Steps to Reproduce:
1. Run the listen script on the server (that would be the machine w/ the 
bcm5700) to listen for the multicast registration (attached)
2. Run the register script on a client to generate the mutlicast 

Actual Results:  Not all of the multicast addresses show up as registered.

Expected Results:  All of the multicast addresses should be registered.

Additional info:

For these scripts to run properly, you'll need IBM's Java VM installled.
Comment 1 Michael Brock 2001-09-28 16:31:31 EDT
Created attachment 32938 [details]
Test Scripts for multicast addresses problems with bcm5700
Comment 2 Michael K. Johnson 2001-12-06 12:08:22 EST
Has this been reported to broadcom?
Comment 3 Arjan van de Ven 2001-12-06 12:10:28 EST
iirc Broadcom already sent us a fix included in 2.4.9-13