You understood it correctly. That learning functionality is what I need
to support the desired behavior.
So, if I intend to support this functionality, allowing it to be
configured by the OpenFlow Controller (i.e., the OpenFlow Controller may
configure the OpenFlow Swtich defining how it should "learn"), I'm
thinking in extending the set of actions.
Do you think this is the most feasible approach?
Best regards,
Carlos Guimarães
On 09/06/2013 06:14 PM, Wes Felter wrote:
On 9/6/13 9:14 AM, Carlos Guimarães wrote:
Hi,
Using the 1.3.2 OpenFlow specification, is it possible to define an
action that whenever the OpenFlow switch receives a packet to a specific
DST to add the INGRESS_PORT to a group table? The objective is to send
the response from the DST towards all ports that received the request
message to the DST (like a multicast response).
From my understanding of OpenFlow specification, I can send the
incoming packets destined to a specific DST to the OpenFlow Controller,
and then the OpenFlow Controller is responsible for updating the group
table. But I would like to avoid doing this using the OpenFlow
Controller everytime I received a packet from a different port.
It sounds like you're talking about some kind of learning. OpenFlow
doesn't have learning (yet). OVS has a learning extension, but I think
it can only create normal flow mods, not group table entries.
_______________________________________________
openflow-discuss mailing list
openflow-discuss@lists.stanford.edu
https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
