Item #1:
flowtracer and monitoring both do per flow statistics. You might want to
examine how they do it (they use pylibopenflow to craft an OpenFlow message).
Item #2:
As I mentioned in response to your previous message, you must be using the
destiny branch of NOX (not zaku) to use OFPAT_ENQUE
Hi Murphy,
Thanks for the reply.
I am using the Zaku beta version. I guess it is the same library that you sent.
But one question I have is, I got some working example of send() function from
nox-send-cmd.py but for recv() function, I can't find example. How can I use
recv() functionof messenger.
Hi,
I am currently using NOX 0.9.0(zaku)~full~beta contrlooer for my
openvswitch 1.2.2 on openflow 1.0
I have developed certain api's using /lib/core.py file .
I am able to get table statictics and port statistics of switch on nox.
ISSUE:
1. I want to extract per flow statistics
Thanks Murphy.
That was extremely helpful.
Theo
On 01/09/2012 04:09 PM, Murphy McCauley wrote:
I am assuming that by 10.10.23.40/2, you don't intend the CIDR meaning, and in
fact mean that you want two bits to be wildcarded.
Try this:
wildcard = (wildcard& ~OFPFW_NW_DST_MASK) | (wild_bits<<
I am assuming that by 10.10.23.40/2, you don't intend the CIDR meaning, and in
fact mean that you want two bits to be wildcarded.
Try this:
wildcard = (wildcard & ~OFPFW_NW_DST_MASK) | (wild_bits << OFPFW_NW_DST_SHIFT);
.. where wild_bits is between 0 and 32 inclusive (in your case, it should be
Good Morning,
I am trying to install rules into switches to match ip prefixes. For
example 10.10.23.40/2. However, the rules i install endup looking like
this: 0.0.0.0/2. I'm sure that I'm installing these rules incorrectly.
Here is a fragment of the code that sets the matching criteria.
Thanks for the report.
Since matching on IP addresses in ARPs is an optional switch feature, I don't
think it's 100% clear what the function should do, but I don't object to the
idea that it should probably just extract the addresses. I'll add it to my
queue.
-- Murphy
On Jan 9, 2012, at 6:2
Hi,
it seems that util.py extract_flow in destiny branch is not
consistent with install_datapath_flow. I tried to install a flow
extracted from a packet and the resulting match failed to capture the
same packet stream.
More precisely, if a packet is an ARP packet, extract_flow returns
following a
Thank you for favor.
I solve the problem from your advice.
"you'll also need to rewrite the SRC when sending from B back to A"
And OFPAT_SET_NW_DST update*automatically *the IP checksum.
I didn't notice it. Thanks a lot!
- Hyogi
2012/1/9 Murphy McCauley
> OFPAT_SET_NW_DST should update the IP
OFPAT_SET_NW_DST should update the IP checksum. Are you sure that a bad
checksum is the problem?
Remember that if you rewrite the DST when sending from A to B, you'll also need
to rewrite the SRC when sending from B back to A. Host A doesn't know that
you've rewritten the address and will hav
Hi,
I want to change the destination address.
So I use these actions. And add output action.
OFPAT_SET_DL_DST, /* Ethernet destination address. */
OFPAT_SET_NW_DST, /* IP destination address. */
Finally destination node could receive the changed packet.
But there is a problem.
I snoop the packe
Right; I was unclear earlier. This bug should only appear on 32 bit Pythons.
On Pythons with 64 bit integers, these are not long integers and have no L
suffix.
This is basically a bad behavior for the hex() function, and I believe this was
*intended* to be fixed in Python 2.x, but was acciden
12 matches
Mail list logo
