Now it comes clear, Even why other controller like pox or floodlight work
out-of-the-box.
Thanks for your reply
> Am 04.07.2014 um 18:40 schrieb Ben Pfaff :
>
>> On Fri, Jul 04, 2014 at 08:49:53AM +0200, Daniel Spiekermann wrote:
>> In my ovs-VM I ran ovs-ovctl set-controller mybridge tcp:172.23
On Fri, Jul 04, 2014 at 08:49:53AM +0200, Daniel Spiekermann wrote:
> In my ovs-VM I ran ovs-ovctl set-controller mybridge tcp:172.23.56.42:6663
>
> Now the ovs should connect to the controller, which produce this logfiles
>
> sudo ovs-controller ptcp:6663 -v
> Jul 03 05:19:42|1|poll_loop|D
Am 04.07.2014 00:02, schrieb Ben Pfaff:
On Wed, Jul 02, 2014 at 09:36:16AM +0200, Daniel Spiekermann wrote:
Hi there,
I am working with ovs and mininet just for a few days, and now I
have some difficulties to unterstand one thing.
I have the "official" mininet VM and locally it works fine. I us
On Wed, Jul 02, 2014 at 09:36:16AM +0200, Daniel Spiekermann wrote:
> Hi there,
>
> I am working with ovs and mininet just for a few days, and now I
> have some difficulties to unterstand one thing.
> I have the "official" mininet VM and locally it works fine. I use
> another VM running an OVS-ins
Hi there,
I am working with ovs and mininet just for a few days, and now I have
some difficulties to unterstand one thing.
I have the "official" mininet VM and locally it works fine. I use
another VM running an OVS-installation. I installed it according to the
INSTALL.Debian instructions. This
