[nox-dev] Flow removed message's match has extra 0-fields

2011-02-15 Thread Derek Cormier
Hello, I think I may have found a bug. First, I add a flow where the dl_type set and everything else is wildcarded. Then I delete it using delete_strict_datapath_flow(). When I receive a flow removed event, I print out the match dictionary and see: {'dl_type': 5, 'nw_dst_n_wild': 0L,

Re: [nox-dev] Flow removed message's match has extra 0-fields

2011-02-15 Thread James Murphy McCauley
So the to_python for ofp_match shows that there's at least an attempt to do the right thing. Given that, the next thing I'd do is check the ofp_flow_removed message on the wire (using Wireshark) to make sure I think the wildcards field is set right there, which would indicate that this is indeed

Re: [nox-dev] Flow removed callback function input parameters.

2010-11-27 Thread K Singh
Thanks Murphy, I was able to get all the required information from .flow parameter mentioned by you. I am trying to accomplish below mentioned statement, would like your or other developers inputs on the approach chosen. I am prioritizing the flows between end hosts on the basis of port

Re: [nox-dev] Flow removed callback function input parameters.

2010-11-26 Thread Murphy McCauley
Responses inline. On Nov 25, 2010, at 9:29 PM, K Singh wrote: I was adding flow removed event in the pyswitch.py file. def install(self): inst.register_for_packet_in(packet_in_callback) inst.register_for_datapath_leave(datapath_leave_callback)

Re: [nox-dev] Flow Removed

2010-11-25 Thread kk yap
Hi Rohit, There is get_flow() in the flow removed event that allows you to get these match information. There is also a reason field which will tell you why the flow was removed. Regards KK PS Happy thanksgiving (and black Friday shopping). On 25 November 2010 17:17, Rohit Manohar