I guess that I would probably implement a new ofproto provider that
includes the features that you can support. You can register your new
ofproto provider by inserting a call to ofproto_class_register() into
ofproto_initialize(), in ofproto/ofproto.c.
On Sat, Jan 28, 2012 at 07:10:45PM +0100, Gio
Hello Ben,
Yes, you're definitely right! But this is not about implementing OpenFlow:
I just want to realize a management interface translation for the features
that is possible to translate (e.g. port statistics retrieval).
Is up to the legacy network device to provide switching, routing, VLAN
ta
On Sat, Jan 28, 2012 at 06:49:36PM +0100, Giorgio Buffa wrote:
> Two pictures with the scenario and the role of OVS in this scenario are
> attached. Following a brief explanation.
>
> I would like to have a legacy network device (i.e. with no support to
> OpenFlow) to be monitored and controlled b
On Sat, Jan 28, 2012 at 04:38:19PM +0100, Giorgio Buffa wrote:
> I would like to use Open vSwitch for the monitoring/control of a legacy
> data plane (i.e. with no support to OpenFlow). The idea is to extend OVS to
> make it an adapter between the OpenFlow protocol (used by the control
> plane) and
Dear all,
I would like to use Open vSwitch for the monitoring/control of a legacy
data plane (i.e. with no support to OpenFlow). The idea is to extend OVS to
make it an adapter between the OpenFlow protocol (used by the control
plane) and SNMP (exposed by the underlying network devices). I'm evalua
