[nox-dev] Handling corrupted TCP header

2011-01-13 Thread Srini Seetharaman
When someone sends the attached packet to a switch, it generates an infinite loop of packet_ins in our production network. This is because this incoming tcp packet has nw_proto=6 and tcp port numbers of 0, but outgoing flow_mod has nw_proto of 0 and tcp port numbers of 0. So, the packet_out

Re: [nox-dev] Handling corrupted TCP header

2011-01-13 Thread kk yap
Hi Srini, What is this packet? The length of TCP is zero?!?! I wish to understand the circumstance for which we are getting the packet before commenting on the right way to handle this. Regards KK On 13 January 2011 10:38, Srini Seetharaman seeth...@stanford.edu wrote: When someone sends

Re: [nox-dev] Handling corrupted TCP header

2011-01-13 Thread Srini Seetharaman
We don't know who sent it, but it came from outside our network. If it is easy to take down a network by just sending 1 invalid packet, I'd be worried! On Thu, Jan 13, 2011 at 10:59 AM, kk yap yap...@stanford.edu wrote: Hi Srini, What is this packet?  The length of TCP is zero?!?!  I wish to

Re: [nox-dev] Handling corrupted TCP header

2011-01-13 Thread kk yap
Hi Srini, I think you are fixing this in the wrong place. Putting nw_proto=0 does not cause an infinite loop. Where is the loop happening? Can you provide more detailed NOX output so that we can even start looking at this. Regards KK On 13 January 2011 11:02, Srini Seetharaman

[nox-dev] C++ Posting Timer Error

2011-01-13 Thread Ricardo Bennesby
Hi, I am writing a component in C++ that uses a timer. In the .hh file I put: *Timer post(const Timer_Callback, const timeval duration) const; Disposition handle_datapath_join(const Event e);* And in the .cc file there is a post that calls a timer method: *#include timeval.hh

Re: [nox-dev] Handling corrupted TCP header

2011-01-13 Thread Masayoshi Kobayashi
KK, I think the implementer will read the spec the other way around. Spec requires nothing special about OFPP_TABLE action (it does not say don't generate pkt_in, if there is no match). So the switch just follows the default behavior, i.e., pkt_in will be generated. I would expect the reference

[nox-dev] pytopology patch

2011-01-13 Thread Nikhil Handigol
Hi, I have added 2 new functions to pytopology that makes it more useful/usable: * get_datapaths() : returns a list of all datapathids in the network * get_neighbors(dpid) : returns a list of neighbors of a given datapathid. I've attached a patch for the destiny branch (commit no.

Re: [nox-dev] pytopology patch

2011-01-13 Thread Martin Casado
Awesome, thanks Nikhil. Hi, I have added 2 new functions to pytopology that makes it more useful/usable: * get_datapaths() : returns a list of all datapathids in the network * get_neighbors(dpid) : returns a list of neighbors of a given datapathid. I've attached a patch for the destiny