[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openvswitch-discuss
Subject:    [ovs-discuss] Unable to get traffic through to internal interfaces inside a VM
From:       blp () nicira ! com (Ben Pfaff)
Date:       2013-01-30 17:34:03
Message-ID: 20130130173403.GG4748 () nicira ! com
[Download RAW message or body]

That doesn't really make sense.

I would try using tcpdump to figure out where packets are going.

On Wed, Jan 30, 2013 at 06:31:16PM +0100, Endre Karlson wrote:
> I also tested setting a IP address directly which SHOULD work in my mind,
> but I can't get any connectivity. Seems to be like when the traffic reaches
> the OVS it doesn't reach the internal port?
> 
> 2013/1/30 Ben Pfaff <blp at nicira.com>
> 
> > On Tue, Jan 29, 2013 at 12:43:40PM +0100, Endre Karlson wrote:
> > > Now I see traffic working fine and I get a address, now the odd bit comes
> > > when I try to add this interface to a OVS bridge after "nulling" it out
> > > with 0.0.0.0 and trying to get an address on another so called "internal"
> > > port in the OVS bridge.
> > > ovs-vsctl add-br br-ex
> > > ovs-vsctl add-port br-ex eth2
> > > ovs-vsctl add-port br-ex wan -- set Interface wan type=internal
> > > dhclient wan
> > >
> > > Now the above yields nada results, but even more odd I think is that
> > when I
> > > do
> > > dhclient br-ex
> > >
> > > I actually get a IP as when I do it just for eth2 when eth2 is not a
> > member
> > > of a OVS bridge.
> >
> > br-ex will have the same MAC address as eth2, but wan is going to have a
> > different one.  This may affect your DHCP server's behavior.
> >

[prev in list] [next in list] [prev in thread] [next in thread]