[nox-dev] Sending Entire packet to NOX contoller
Hi all, I have a query that how we can instruct the switch to send the entire packet rather i found solution to this as in To instruct the switch to send the entire packet to NOX, we have to make some changes to src/lib/openflow.cc. The following statement osc.miss_send_len = htons(OFP_DEFAULT_MISS_SEND_LEN); has to be changed to osc.miss_send_len = htons(0);(1) But when i changed the parameter in the openflow.cc file and recompiled the NOX it has started dropping the packet giving the error packet to short. My question is that by sending entire packet do we mean sending application level data.. Regards, Ali Ahmad ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
Re: [nox-dev] Sending Entire packet to NOX contoller
The problem is that this isn't true anymore. Since OpenFlow 0.9 or 1.0, you should set it to 0x instead of 0. 0 does exactly what it seems like it should -- send 0 bytes of data. -- Murphy On Oct 17, 2011, at 4:39 AM, ali ahmad wrote: Hi all, I have a query that how we can instruct the switch to send the entire packet rather i found solution to this as in To instruct the switch to send the entire packet to NOX, we have to make some changes to src/lib/openflow.cc. The following statement osc.miss_send_len = htons(OFP_DEFAULT_MISS_SEND_LEN); has to be changed to osc.miss_send_len = htons(0);(1) But when i changed the parameter in the openflow.cc file and recompiled the NOX it has started dropping the packet giving the error packet to short. My question is that by sending entire packet do we mean sending application level data.. Regards, Ali Ahmad ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
Re: [nox-dev] Bugs in the send_openflow_command(..) and send_openflow_packet(..)
Assuming you're installing a route along multiple switches, all of them except maybe one should probably have an empty (0x) buffer_id. This doesn't seem like it should be the problem. I can't even hazard a guess without knowing more about the situation. What version of NOX are you running? What kind of switch? What does the NOX log show? Can you provide a capture of the OpenFlow traffic between a switch that sends an error and the controller? -- Murphy On Oct 17, 2011, at 6:33 AM, andrea simeoni wrote: Hi guys, I'm trying to run the simplerouting component, and found that when installing the route it receives Malformed packet error messages back from the switches. The same happens when calling send_openflow_packet(..). If i go in wireshark to analyse the controller-switches openflow packets, I find that the field buffer-id has None value in both cases. Any suggestions? How can I make things working properly? -- Andrea Simeoni ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
Re: [nox-dev] How use send_openflow_packet(indpid, pie.buffer_id, const ofp_action_header actions[] ...)
On first glance, yes, that looks correct. Then just cast arrbuff.data() to the appropriate type and pass it as the actions parameter. -- Murphy On Oct 17, 2011, at 5:28 AM, andrea simeoni wrote: Hi guys, I'm trying to instruct a switch to send a buffered packet out of a port. Then I'm trying to use the function send_openflow_packet(indpid, pie.buffer_id, const ofp_action_header actions[] ...). If I start from an ofp_action_list how can I get the correct ofp_action_header []? I tried the following code: ofp_action_list* act_list=new ofp_action_list(); ofp_action* act = new ofp_action(); act-set_action_output(2, 0); // output on port 2 act_list-action_list.push_back(*act); Array_buffer arrbuff(act_list-mem_size()); act_list-pack(arrbuff.data()); It's correct? What is the correct ofp_action_header [] parameter to pass to the function? Thank you -- Andrea Simeoni ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
Re: [nox-dev] Bugs in the send_openflow_command(..) and send_openflow_packet(..)
You are right Murphy, in the case of simplerouting, I receive error messages by all switches along the path except for the first (as it is the only having a non empty buffer-id for that packet). I didn't know that those OF errors could be ignored. I solved also the question for the send_openflow_packet() instruction. Since the reason of my packet-in events is explicitely send to controller, then packets are never buffered in switches. However I've a little question more: When I configure the action OFPP_CONTROLLER using ofp_action, is there a way to tell the switch to send the whole packet to the controller, using the ofp_action::set_action_output()? Thank you very much 2011/10/17 Murphy McCauley jam...@nau.edu Assuming you're installing a route along multiple switches, all of them except maybe one should probably have an empty (0x) buffer_id. This doesn't seem like it should be the problem. I can't even hazard a guess without knowing more about the situation. What version of NOX are you running? What kind of switch? What does the NOX log show? Can you provide a capture of the OpenFlow traffic between a switch that sends an error and the controller? -- Murphy On Oct 17, 2011, at 6:33 AM, andrea simeoni wrote: Hi guys, I'm trying to run the simplerouting component, and found that when installing the route it receives Malformed packet error messages back from the switches. The same happens when calling send_openflow_packet(..). If i go in wireshark to analyse the controller-switches openflow packets, I find that the field buffer-id has None value in both cases. Any suggestions? How can I make things working properly? -- Andrea Simeoni ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev -- Andrea Simeoni ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
Re: [nox-dev] problem -- nox|ERR:Application 'python' description not found.
I beg your pardon i don't know if it's the roght way to answer. First I've found only the 0.5 inthis url http://noxrepo.org/wp/?page_id=15 http://noxrepo.org/wp/?page_id=15 and I've followed what's in this url http://noxrepo.org/noxwiki/index.php/NOX_Installation http://noxrepo.org/noxwiki/index.php/NOX_Installation And the release when i launch nox_core -V is the 0.9 compiled with OpenFlow 0x01 Thanks in advance for your ideas ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
Re: [nox-dev] Bugs in the send_openflow_command(..) and send_openflow_packet(..)
Yes. Use 0x as the second parameter to set_action_output(). -- Murphy On Oct 17, 2011, at 7:14 AM, andrea simeoni wrote: You are right Murphy, in the case of simplerouting, I receive error messages by all switches along the path except for the first (as it is the only having a non empty buffer-id for that packet). I didn't know that those OF errors could be ignored. I solved also the question for the send_openflow_packet() instruction. Since the reason of my packet-in events is explicitely send to controller, then packets are never buffered in switches. However I've a little question more: When I configure the action OFPP_CONTROLLER using ofp_action, is there a way to tell the switch to send the whole packet to the controller, using the ofp_action::set_action_output()? Thank you very much 2011/10/17 Murphy McCauley jam...@nau.edu Assuming you're installing a route along multiple switches, all of them except maybe one should probably have an empty (0x) buffer_id. This doesn't seem like it should be the problem. I can't even hazard a guess without knowing more about the situation. What version of NOX are you running? What kind of switch? What does the NOX log show? Can you provide a capture of the OpenFlow traffic between a switch that sends an error and the controller? -- Murphy On Oct 17, 2011, at 6:33 AM, andrea simeoni wrote: Hi guys, I'm trying to run the simplerouting component, and found that when installing the route it receives Malformed packet error messages back from the switches. The same happens when calling send_openflow_packet(..). If i go in wireshark to analyse the controller-switches openflow packets, I find that the field buffer-id has None value in both cases. Any suggestions? How can I make things working properly? -- Andrea Simeoni ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev -- Andrea Simeoni ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
[nox-dev] Cannot see the flow table
I have the following configuration NOX - eth0 - 192.168.10.1/24 Switch 1 - eth0- 192.168.10.2/24 Switch 2 - eth0 - 192.168.10.3/24 Host 1 - eth0 - 192.168.10.4/24 Host2 - eth0 - 192.168.10.5/24 NOX | |--| switch1 switch2 | | host1host2 All of them are connected to VLAN(including host1 and host2). I ran the pyswitch module on NOX and secchan on switches. Switches are connected to NOX. When I ping from host1 to host2 the ping works but I cannot see any flow tables on switches. I used dumpflow command to see flow tables. Where did I go wrong? Is my configuration right? Regards, Candy ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
