From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Ryan King <ryank@staff.globaldial.com>
Cc: "bridge@lists.linux-foundation.org" <bridge@lists.linux-foundation.org>
Subject: Re: [Bridge] MAC intermittently being learnt on wrong port
Date: Mon, 11 Jan 2010 10:18:48 -0800 [thread overview]
Message-ID: <20100111101848.38fad04f@nehalam> (raw)
In-Reply-To: <0B4BAD7651DDBF4CB463FDBCA36C673F108C64BE@EXCHANGE.claremont.globaldial.com>
On Fri, 8 Jan 2010 03:25:10 +0000
Ryan King <ryank@staff.globaldial.com> wrote:
> Hi,
>
> I am seeing a strange issue with a fairly simple bridge I have setup (for openvpn in bridge mode).
>
> eth0 --- [ openvpn machine (tap0) ] --- eth1
>
> The bridge is between tap0 and eth1 on a debian machine running on ESX 4. (tap0 being the openvpn tunnel interface). Intermittently, I see openvpn client MAC addresses on port 2 (eth1). When this happens, their vpn link stops working, since arp replies are being sent back via the wrong interface. But after a random amount of time, it will change back to port 1 (tap0) and start working again. Sometimes this is quick, sometimes it doesn't happen for hours.
>
> Anyone else had these issues? I've searched the archives, and come across several people who seem to have had similar problems - but haven't found one that has a solution yet.
>
> I'd appreciate any suggestions on where I should start looking to find out why/how these MAC's are being learnt on the wrong interface...
>
By default the address of the bridge interface is the minimum of all the interfaces,
and the tap one is generated randomly; that might be your problem.
So either:
1. force a specific MAC address on the tap interface
or 2. force the the MAC address of the bridge interface to be that of eth
next prev parent reply other threads:[~2010-01-11 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-08 3:25 [Bridge] MAC intermittently being learnt on wrong port Ryan King
2010-01-11 17:16 ` Robert LeBlanc
2010-01-11 18:18 ` Stephen Hemminger [this message]
2010-01-11 18:42 ` Robert LeBlanc
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=20100111101848.38fad04f@nehalam \
--to=shemminger@linux-foundation.org \
--cc=bridge@lists.linux-foundation.org \
--cc=ryank@staff.globaldial.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.