Ethernet Bridge development
 help / color / mirror / Atom feed
From: "Joubert Berger" <joubert@berger-family.org>
To: Elias Chatzigeorgiou <echatzigeorgiou@youtravel.com>
Cc: bridge@osdl.org
Subject: Re: [Bridge] Bridging under vmware esx 3.0
Date: Sat, 16 Aug 2008 23:33:58 -0400	[thread overview]
Message-ID: <82b0add70808162033x67c43630wd6a1a656fb57f2cb@mail.gmail.com> (raw)
In-Reply-To: <30CDFF93154A1B47814BD152CC5F9201089E4C73@YTMAIL.youtravel.local>

Remember that you need to put the ports on the vmware switch into
promiscuous mode.

--joubert

On Thu, Aug 14, 2008 at 5:50 PM, Elias Chatzigeorgiou
<echatzigeorgiou@youtravel.com> wrote:
> Hello,
>     I tried to setup a bridge in a (debian-based) virtual machine using esx
> server. I added two nics on my vm connected then in two different networks
> and used the bridge utility (brctl) to bridge them. I gave the bridge an ip
> address so that it would be visible from the network.
>
> I can access both networks from that vm, and machines on both networks can
> access the vm.
>
> BUT PACKETS from net1 do not reach net2 and vise-versa.
>
> I have no ip/ebtable rules and /proc/sys/net/bridge/* files are set to zero.
>
> As a last check, I used tcpdump to dump packets comming from e.g. the net1
> to the attached nic (eth0) and they seem to reach only if eth0 is not part
> of the bridge.
>
> PLEASE ADVISE.
>
> Thanks
> Elias Chatzigeorgiou
>
> _______________________________________________
> Bridge mailing list
> Bridge@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/bridge
>

      parent reply	other threads:[~2008-08-17  3:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-14 21:50 [Bridge] Bridging under vmware esx 3.0 Elias Chatzigeorgiou
2008-08-15 22:03 ` Stephen Hemminger
2008-08-17  3:33 ` Joubert Berger [this message]

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=82b0add70808162033x67c43630wd6a1a656fb57f2cb@mail.gmail.com \
    --to=joubert@berger-family.org \
    --cc=bridge@osdl.org \
    --cc=echatzigeorgiou@youtravel.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