[ovs-discuss] When a controller is plugged in vlans stop working: normal?

[Pasquale Dir]

Problem is that for my project I need openvswitches which can be used to
make communicate internal hosts with external ones, if specific events
occur.

So my idea was the following: a generic openvswitch would have been like
-br0
---eth0
---gre0 tag2

If I would have needed to share some resource to the external world I'd
just put an openflow rule on the specific openvswitch telling it to output
specific packets from gre0 port (internal) to the eth0 port (external).

Hosts who attach to an openvswitch throught tagged ports are indeed part of
an internal network so it is just right that they can communicate JUST
between each other by gre tunnels...but if eth0 is connected to the
openvswitch too, these hosts stop communicating.

I though that, as openvswitch is executed as a software process, it would
have used linux network stack anyway to allow gre tunnel
communication...but it seems it doesn't.

It will do it with this configuration:
-bro
---gre0 tag2
-eth0

but it is not ok to me, as I would miss a way to output some internal gre
traffic to eth0, as it isn't connected to the switch and thus I could not
make any openflow rule.




2014-05-05 23:00 GMT+02:00 Ben Pfaff <blp at nicira.com>:

> On Mon, May 05, 2014 at 10:56:01PM +0200, Pasquale Dir wrote:
> > Yes, that way it works fine, I already tried it...so you confirm me that
> > for openvswitch to work I need at least a working external network
> > interface?
>
> I don't understand the question.
>
> If you want a computer to interface to an external network, you need a
> working external network interface.  This has nothing to do with Open
> vSwitch.
>
> If you don't want your computer to interface to an external network,
> you don't need a working external network interface.  This also has
> nothing to do with Open vSwitch.
>
> Open vSwitch works OK in either situation.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/discuss/attachments/20140505/07b16238/attachment.html>