One thing that I never got to doing is to change all the parsing to go
through the openflow-pack library which will fix the byte order issue.
If someone would do that, it would be a great service to people using
NOX.
Regards
KK
On 2 May 2011 10:48, Murphy McCauley wrote:
> So I'm not sure if th
Thanks a lot, that worked perfectly :)
On 05/02/2011 07:48 PM, Murphy McCauley wrote:
So I'm not sure if this is a bug or a feature. If NOX has a really coherent
strategy towards byte order, I've never really figured it out. :) But the
problem is just that your bytes are getting swapped. I'd s
So I'm not sure if this is a bug or a feature. If NOX has a really coherent
strategy towards byte order, I've never really figured it out. :) But the
problem is just that your bytes are getting swapped. I'd say just call
ntohs() on event.flow_dl_type. (Equivalently, call htons() on whatever
Hi,
I am using the authenticator module.
I registered to the flow in event :
self.register_handler(Flow_in_event.static_get_name(),self.flow_in_call_back)
When I try to get the EtherType of a flow through calling this
parameter: type = event.flow.dl_type
I get EtherType equal to "25480" which i
I wouldn't call myself an expert on the routing component, but...
If you're not using nat_enforcer/pass False for check_nat, I think setup_flow()
is basically just a flow_mod, possibly followed by a packet_out if you supply a
buffer and no buffer ID. You can specify extra actions, but it append
You just want to check the TOS field value of a packet you got from a Python
packet_in handler? In that case, all that matters is ipv4.py (from the Python
packet parsing library), and I'm pretty sure the TOS field works fine in it.
So if you're seeing packet.next.tos is 0, then... I suspect it
Hi Marwen
I believe this is a problem with your NOX code. Could you please mail
to the nox-dev list relevant pieces of your code and folks can help
you figure out what is going wrong?
Please drop openflow-discuss list from the future replies.
Thanks
Srini.
On Mon, May 2, 2011 at 3:24 AM, marwen
Hi,
My NOX controller version is zaku.
I recently wanted to know the tos field value, so I print openflow.OFPFW_NW_TOS
and packet.next.tos, but these results were so strange like the following:
openflow.OFPFW_NW_TOS = 2097152
packet.next.tos=0
Not only ping, but also ftp service, they were alwa
Hi,
I need to know what does the following functions do, unfortuanately no
documnetation is provided for them:
- setup_flow(self, flow, dp, outport, bid, buf, timeout,actions, check_nat)
- send_packet(self, dp, inport, outport, bid, buf,
actions, check_nat, flow)
Can an
