Thanks Kyriakos :)
In fact, my confusion came from the fact that the inport is got from
registering to the packet_in event. So when you register you get the
inport, however this inport is used for two different cases.
So, in the case where the inport is got from registering to the
packet_in event, would this be the port from which the controller
received the packet from the switch or the port from which the switch
received the packet from the network but did not know how to handle it.
Thanks again!
On 03/28/2011 06:39 PM, Kyriakos Zarifis wrote:
Hi Karim,
'inport' actually refers to a different thing in each case:
* send_openflow(dpid, bufid, buf, openflow.OFPP_FLOOD, inport)
send_openflow is used to inject a packet in the network, and send it
out the 'dpids's port(s) described the 4th parameter. The switch
should treat the packet as if it arrived on 'inport'. The packet
actually arrives through the openflow channel, but you use this for
things like openflow.OFPP_TABLE, where the packet will be forwarded
based on the flow_table matches, in which case it needs to have
arrived on a physical port.
* install_datapath_flow(dpid, flow, 5, 0, actions, bufid,
openflow.OFP_DEFAULT_PRIORITY, inport, packet)
Here it is indeed what you said: it is the input port to match for
this flow entry we are installing. (after installing this entry,
packets matching 'flow' arriving on 'inport' all be treated according
to 'actions')
Do they design the port of communication between the controller
and the switch, or the port from which a switch received a packet
and that has after to forward it to the controller.
In the first case it seems that the inport is the port between the
controller and the switch, however the second case seems to be the
port from which a switch received a packet.
Thanks a lot.
Regards,
Karim
_______________________________________________
nox-dev mailing list
[email protected] <mailto:[email protected]>
http://noxrepo.org/mailman/listinfo/nox-dev
_______________________________________________
nox-dev mailing list
[email protected]
http://noxrepo.org/mailman/listinfo/nox-dev
