I'd suggest that the first thing you do is examine the traffic from the
controller to the switch. Wireshark with the OpenFlow dissector is the easiest
way to do this. Take a look at the flow_mod on the wire and see if it looks
like you think it should (whether tp_src and tp_dst are set right,
I think in this case, the other program is another instance of NOX being run
simultaneously. :) So the last suggestion applies. The commandline to start
the second instance should be something like:
./nox_core -v -i ptcp:6635 jsonmessenger=tcpport=2704 spanning_tree routing
-- Murphy
On Sep
Hi,
Which match-fields are you setting in the Flow? For setting Source and
Destination Port Addresses (tp_dst or tp_src), OpenFlow protocol requires
you to set the Network Protocol (nw_proto) match-field as well. This field
tells the datapath what header to expect next after the IP header. A
nw_pr
It looks like either the socket was left open from an ungraceful shutdown
last time you ran NOX, or another application happens to be using the port
that jsonmessenger is trying to use. If I recall, that would be port 2703.
If you run "lsof -i | grep 2703" you should be able to see which applicat
When i try to run two nox with the spanning_tree i get this error below.
First: Ok
openflow@openflowvm:~/nox/build/src$ ./nox_core -v -i ptcp:6634 switch
spanning_tree routing
1|nox|INFO:Starting nox_core
(/home/openflow/nox/build/src/.libs/lt-nox_core)
2|nox|INFO:nox bootstrap complete
S
Hi,
I'm trying to install a flow that matches on IP as well as port numbers. I'm
using the flow provided by calling extract_flow() on a packet as the
argument to install_datapath_flow() but if I use 'dpctl dump-flows' on a
switch the flow displayed does not have entries for tp_dst or tp_src. Is
the