Red Hat Bugzilla – Bug 607608
bnx/8021q does not separate vlans correctly
Last modified: 2011-06-27 14:52:16 EDT
Description of problem: I've got a 4-port network card, which is supposed to work with 802.1Q-tagged network traffic. When I use an eth0 interface, everything works as expected. Appropriate frames are delivered to proper vlan interfaces (that is eth0.vlan-id and the like). However whenever I try to use the other three interfaces nothing appears on eth[123].vlan-id. I thought disabling an asf interpreter on firmware could solve the problem. Two of the all four ports are capable of grabbing management traffic (but since there is another dedicated management port, DRAC was configured to listen on the latter anyway). The uxdiag utility with mfw option was used, but nothing has changed. Version-Release number of selected component (if applicable): 2.6.33.5-112.fc13.x86_64 How reproducible: always Steps to Reproduce: 1. ip l s eth[123] up 2. vconfig add eth[123] vlan-id 3. ip l s eth[123].vlan-id up 4. tcpdump -i eth[123] (and watch frames flowing happily) 5. tcpdump -i eth[123].vlan-id (and enjoy utter silence) Actual results: on the eth[123].vlan-id interfaces traffic is filtered out Expected results: on the eth[123].vlan-id interfaces traffic is present Additional info:
Created attachment 426568 [details] lscpi output
Has anybody been able to reproduce that erroneous behaviour?
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 WONTFIX if it remains open with a Fedora 'version' of '13'. 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 prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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. Thank you for reporting this bug and we are sorry it could not be fixed.