Re: [nox-dev] order of processing packets

[maybe less of a nox question and more of an openflow question, but...] The switch opens a raw socket to listen on each interface, so it's effectively a read-only copy like tcpdump uses (exactly like tcpdump), so it doesn't interfere with any other processing that happens. You could imagine the

Re: [nox-dev] Matching on NW_TOS doesn't seem to work?

Hmm, It seems like if I'm having trouble getting this to match as well? flow[core.NW_DST] = ipstr_to_int(192.168.2.99) The flow entry still becomes cookie=0, duration_sec=15s, duration_nsec=23900s, table_id=1, priority=32768, n_packets=15, n_bytes=1470,

Re: [nox-dev] order of processing packets

Thanks Rob, Thats what I was thinking was going on. Just wanted to make sure. Aaron On Sun, Nov 21, 2010 at 2:04 PM, Rob Sherwood rob.sherw...@stanford.eduwrote: [maybe less of a nox question and more of an openflow question, but...] The switch opens a raw socket to listen on each

Re: [nox-dev] Xterm

I assume you're using OpenFlowVMS or the old VM scripts. If you want to use a single xterm, use screen or tmux. Discussion of their use is really off-topic for this list. Both have man pages that you can reference as well as many websites that describe their use. But here's a short

Re: [nox-dev] Matching on NW_TOS doesn't seem to work?

Do you have the OpenFlow wireshark plugin? I'd suggest monitoring the OpenFlow traffic from the controller to the switch and seeing if the match data in the flow mod looked right. -- Murphy On Nov 21, 2010, at 11:12 AM, Aaron Rosen wrote: Hmm, It seems like if I'm having trouble

[nox-dev] order of processing packets

Hello, I have a question about what happens when you are sending packets to a host that is also running the openflow switch. For example, I'm running openflow on a pc-engine with the following command. ofprotocol unix:/var/run/dp0 tcp:130.127.39.173:6639 --fail=closed ofdatapath

Re: [nox-dev] Matching on NW_TOS doesn't seem to work?

Hi Aaron If you are using Open vSwitch, you should use ovs-ofctl instead of ovs-dpctl to lookup your flow table. Also, since nw_tos and nw_dst are valid only for IP flows, you should add: flow[core.DL_TYPE] = 0x0800 to match only IP flows. I think that if you don't do that OVS may just ignore

Re: [nox-dev] Matching on NW_TOS doesn't seem to work?

Thanks Romain, That did the trick. Aaron On Sun, Nov 21, 2010 at 5:48 PM, Romain Lenglet rom...@midokura.jp wrote: Hi Aaron If you are using Open vSwitch, you should use ovs-ofctl instead of ovs-dpctl to lookup your flow table. Also, since nw_tos and nw_dst are valid only for IP flows,

[nox-dev] Adding flows using python code.

Hi, How do you add flows in the python controller. One way to achieve this is to add using dpctl tool. I want to know if there are some inbuilt functions to call such command in python code? Also, can someone verify my understanding: After starting mininet and NOX controller, I would add

Re: [nox-dev] Adding flows using python code.

Yes, NOX can manipulate the flow table of a switch, for example by using the install_datapath_flow() method of components. A good example of this is in pyswitch.py, and you can find some additional information here: http://openflow.org/wk/index.php/GEC8Tutorial#Sending_OpenFlow_messages Your