I created the messages vendor of the new type that we want to define and
sent them to the switches in openvswitch mininet, who answer "correctly"
Error OFPET_BAD_REQUEST OFPBRC_BAD_VENDOR
'cause they do not know the vendor code that I entered
in the error message perfectly copying the message cont
Foget that, I have resolved it, but another question happened: when I use
ovs-vsctl create ovsbr0,
[root@Mic ovs]# ovs-vsctl show
0a6f41ed-415a-4868-a41a-592145adb1c7
Bridge "ovsbr0"
Port "ovsbr0"
Interface "ovsbr0"
type: internal
and then I want to use this
Hello Ed,
I don't have an answer to your question, but was wondering if it is possible
to actually implement the Authenticator via an Openflow controller using
standard OpenFlow rules? I'd be very interested to know if this is
possible or if anyone has tried this.
Regards,
Paul
_
Hi ovs members, I got this issue below, may you give me some tips to
resolve this ?
Thanks a lot.
[root@Mic ~]# ovs-vswitchd --pidfile --detach
2013-09-06T06:51:55Z|1|reconnect|INFO|unix:/usr/local/var/run/openvswitch/db.sock:
connecting...
2013-09-06T06:51:55Z|2|reconnect|INFO|unix:/usr/l
On Sat, Sep 07, 2013 at 10:13:57PM -0400, Jing Su wrote:
> I'm getting a problem with ovs-vswitchd segfaulting when I delete virtual
> machines on KVM.
>
>
> Linux 3.2.0-29-generic #46-Ubuntu SMP
> openvswitch-1.9.0 - compiled from source
We just released 1.9.3, can you try that?
__
