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 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)
inst.register_for_datapath_join(datapath_join_callback)
inst.post_callback(1, tim
When a flow removed event is thrown, it can be either due to a flow removal
or flow expired. If it is flow expired, I wanted to know which flow it is,
that is flow attributes like destination IP and source IP. In the
flow_removed header, I cannot see this information being passed to the
controller.
All the packet objects (ethernet, ipv4, tcp, etc.) have a number of fields
(generally set in their __init__()). For example, tcp packets have .srcport
and .dstport among others. ipv4 objects have .srcip, .dstip, etc. Packet
objects also have a .next field which contains their payload. This m
Hi,
I am trying to parse the packets which arrive at NOX controller for
following parameters:
1. Source/Destination IP address
2. Source/Destination Port number
All this information will be obtained from TCP/UDP packet along with IP
header. I found in "packet" folder ethernet.py, ipv4.py, tcp.py
Hi Murphy,
You were right!!
I registered the port_status_event function in my coreapi and now all the
values
are printed correctly.
Thank You!
regards,
Sachin Sharma
From: Murphy McCauley
To: sachin sharma
Cc: nox-dev@noxrepo.org
Sent: Thu, 25 November,
Hi Matt,
Take a look at OpenFlowVMS
(http://www.openflowswitch.org/wk/index.php/OpenFlowVMS), which have
support for OpenFlow 1.0. (Caveat: I maintain that). Unfortunately,
note that I am not actively developing this anymore.
Regards
KK
On 24 November 2010 20:32, Matt Strum wrote:
> Hello, I'
Hi Derek,
In C/C++, you can make use of datapathmem in netapps/networkstate. I
would personally discourage you from maintaining your own list and
extend datapathmem for use in Python. Unfortunately, I do not use
Python in NOX enough for me to swigify the component. I am happy to
push your patch
