From: Andrew Morton <akpm@osdl.org>
To: netdev@oss.sgi.com
Subject: Fw: [Bugme-new] [Bug 3992] New: Bondig. Not correct work function ARP Monitoring. Broken link.
Date: Wed, 5 Jan 2005 13:35:25 -0800 [thread overview]
Message-ID: <20050105133525.2bab2e09.akpm@osdl.org> (raw)
Begin forwarded message:
Date: Wed, 5 Jan 2005 07:59:17 -0800
From: bugme-daemon@osdl.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 3992] New: Bondig. Not correct work function ARP Monitoring. Broken link.
http://bugme.osdl.org/show_bug.cgi?id=3992
Summary: Bondig. Not correct work function ARP Monitoring. Broken
link.
Kernel Version: 2.6.10
Status: NEW
Severity: normal
Owner: jgarzik@pobox.com
Submitter: stanislav@muhachev.petro.ru
Distribution:
Hardware Environment:
Vmware GSX machine
Software Environment:
Gentoo
Problem Description:
bonding interface going down and down slave link
Steps to reproduce:
2 virtual pc
identical gentoo linux (copy)
1 nic for both virtual pc
up 2 openvpn link trouch nic to another virtual pc (tap0 and tap1)[ethernet
bridge]
link both vpn1 and vpn2 - ok!(independing link like:192.168.1.1-192.168.1.2
and 192.168.2.1-192.168.2.2)
bonding vpn1 & vpn2 òî bond0 (bonding default setup -> nothing failover
setings)
link îê!(192.168.100.1-192.168.100.2)
setting arp monitor in bonding (TUN/TAP driver not support Mii status)
link down!
arp request go from bond0(machine1)[from tap0 & tap1] to bond0(machine2) - ok.
arp answer bond0(machine2) interface - ok!
!!! bond0(machine2) -> tap0(tap1)(machine2) - noting!!!(arp answer broken)
resultat arp request not complite
situation analog both side
for monitoring use TCPDUMP
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2005-01-05 21:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 21:35 Andrew Morton [this message]
2005-01-11 22:17 ` Fw: [Bugme-new] [Bug 3992] New: Bondig. Not correct work function ARP Monitoring. Broken link Tommy Christensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050105133525.2bab2e09.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).