| Summary: | Bridging not Working as Expected with 8021q and bonding | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jonathan Steffan <jonathansteffan> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 14 | CC: | drjohnson1, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, nhorman |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-08-16 13:47:22 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Jonathan Steffan
2011-03-13 00:21:16 UTC
Is the switch configured for an 802.1q connection on those two ports? (In reply to comment #1) > Is the switch configured for an 802.1q connection on those two ports? Yes. The following both work: [eth0] <=> [eth0.vlantag] <=> [br0] <=> [vnet0] [eth1] <=> [eth1.vlantag] <=> [br0] <=> [vnet0] I'm pretty sure you do not want to do ifup on eth0 and eth1, and also you should do ifdown on bond0 before bringing up the vlan interfaces on it. ifconfig dev up does not do anything but activate the interface. It does not run the ifcfg scripts. The reason I'm doing an ifconfig dev up is because an interface needs to be up to join to a bond, iirc. Seeing as how I'm not using any ifcfg scripts to configure these interfaces (for the purpose of this bug report) I had to bring the interfaces up. Any updates here? This is still an issue. check the bridge forwarding tables. I expect you'll find that the mac addresses for your tun tap devices are associated with the incorrect interface. If so, this is an artifact of the bonding driver getting frames looped back to itself from the peer switch. To fix it you'll need to use a bonding mode that prevents such behavior (802.3ad is the best method). This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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 |