Red Hat Bugzilla – Bug 595591
[Broadcom 6.0 bug] brcm_iscsiuio may place stale packets on the wire
Last modified: 2012-06-26 12:26:40 EDT
Only put data on the wire if there is indication from the uIP stack.
Without this fix, there were reports of being flooded with ARP data from a broadcast address. This is because uIP will silently dropthis packet but didn't give any indication back. This will send thebogus packet on the wire and other Window's boxes will respond. Which would cause a loop and thus flooding the network.
1. Run uIP with broadcast traffic. Windows machines on the network will reply.
Created attachment 416279 [details]
brcm_iscsiuio uIP-0.5.15 should resolve this problem. The solution here is to check additional indications from the uIP whether to place packets on the wire or not.
If it is possible, I think this would be ok for 6.0. It was found while testing our beta code and the fix will only affect the bnx2i driver. Adding devel ack.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
This is fixed in iscsi-initiator-utils-18.104.22.1682-6. You can download it here:
There was a fix from Shyam (from https://bugzilla.redhat.com/show_bug.cgi?id=580743#c44) to the brcm code. I forgot to add this to the iscsi-initiator-utils-22.214.171.1242-6 release.
I respun it with that fix included. Same download dir:
but there is a new version initiator-utils-126.96.36.1992-7.
Benjamin @ BRCM - please test this ASAP.
I will see if I can help verify this. But, I am aAlso adding Edward Ng <firstname.lastname@example.org> who is in charge of the Broadcom Linux iSCSI testing to see if he can also help.
This was later fixed and verified with newer uIP 5.15.1.RHEL60, it is in initiator-utils-188.8.131.522-10
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.