Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 292029 Details for
Bug 429154
bonding + arp monitoring + xen cause interface flapping
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
[patch]
Patch to network-bridge to add scope host IP back to physical bond
xen-3.0.3-network-bridge-support-arp-monitoring-bond-netdevs.patch (text/plain), 1.60 KB, created by
Vince Worthington
on 2008-01-17 16:45:32 UTC
(
hide
)
Description:
Patch to network-bridge to add scope host IP back to physical bond
Filename:
MIME Type:
Creator:
Vince Worthington
Created:
2008-01-17 16:45:32 UTC
Size:
1.60 KB
patch
obsolete
>--- network-bridge 2007-12-11 18:55:56.000000000 -0500 >+++ network-bridge.arpmon 2007-12-11 18:55:06.000000000 -0500 >@@ -266,6 +266,17 @@ op_stop () { > if link_exists "$pdev"; then > ip link set dev ${vif0} down > mac=`ip link show ${netdev} | grep 'link\/ether' | sed -e 's/.*ether \(..:..:..:..:..:..\).*/\1/'` >+ # if pdev is a bond interface and we are using arp monitoring on it, we need >+ # to delete the scope host master IP from it now: >+ if is_bonding ${pdev} ; then >+ # are we using arp monitoring? We should have at least one arp_ip_target >+ # if we are.. >+ if [ `cat /sys/class/net/${pdev}/bonding/arp_ip_target` != "" ] ; then >+ # get IP address info from pdev >+ get_ip_info ${pdev} >+ ip addr del ${addr_pfx} dev ${pdev} >+ fi >+ fi > transfer_addrs ${netdev} ${pdev} > if ! ifdown ${netdev}; then > get_ip_info ${netdev} >@@ -309,6 +320,19 @@ add_to_bridge2() { > > if [ ${i} -eq ${maxtries} ] ; then echo '(link isnt in running state)' ; fi > >+ # is the dev a bond device? If so, is bonding driver using arp monitoring >+ # to check link status? If so, we need a master address on the pdev or our >+ # arp requests will have 0.0.0.0 as tell address and link on the pdev will >+ # flap as a result. Setting scope host should be enough without disrupting >+ # anything. >+ if is_bonding ${dev} ; then >+ # are we using arp monitoring? >+ if [ `cat /sys/class/net/${dev}/bonding/arp_ip_target` != "" ] ; then >+ echo "adding address ${addr_pfx} as scope local address to ${dev}" >+ ip addr add ${addr_pfx} dev $2 scope host >+ fi >+ fi >+ > add_to_bridge ${bridge} ${dev} > } >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 429154
:
292029
|
292034
|
292542
|
293521
|
293522
|
325247
|
328011