Hi.
I am really sorry. I had not specified the port of the controller previously
in tcpdump.
Now it is dumping the control traffic.
Sorry for confusion. Hope it helps to find the problem.
Best Regards.
2011/7/25 kk yap yap...@stanford.edu
There are no OpenFlow control traffic in both. In
I mean a tcpdump of the control traffic. Not datapath. :)
On 24 July 2011 10:04, Ricardo Bennesby ricardo.benne...@gmail.com wrote:
Hi. The tcpdump .pcap file the print of a dump-flows command are attached.
The dump-flows, tcp-dump and wireshark shows the same result: I first ping
from
Hi KK. I tested as you suggested.
*ofm-match.nw_dst = htons(36677824); // I tested also ofm-match.nw_dst =
flow.nw_dst;*
and in the action I did:
*
*
*nwaction-nw_addr = htons(new_ip);*
*
*
But it continue trying to send to IP *192.168.47.2...*
The Wireshark continues showing these:
*Ethernet
