hi, perhaps you've already resolved your problem, but if not, I think there is a typo in your rules below. I'll also put some debugging tips at the end.
On Nov 14, 2013, at 12:51 AM, Perhaps Lee <07xl...@gmail.com> wrote: > 1. Without the the enqueue actions. > ... > ip,in_port=1,nw_dst=192.168.0.2,idle_timeout=0,actions=output:3 > ip,in_port=2,nw_dst=192.168.0.2,idle_timeout=0,actions=output:3 ... > then add the flows as: > ip,in_port=1,nw_dst=192.168.0.12,idle_timeout=0,actions=enqueue:3:1 > ip,in_port=2,nw_dst=192.168.0.35,idle_timeout=0,actions=enqueue:3:2 did you mean to use "nw_dst=192.168.0.2" at this point, as you had in the rules above? it looks to me like these two rules wouldn't actually match any traffic, based on your setup. > Has anyone tested this function in the openwrt equipment? yes, I can confirm that it works as described on the Slicing wiki page you described. hopefully it is working for you too now! if not, here are some tips: 1) confirm that the rules you have installed are actually matching traffic by examining the n_packets= and n_bytes= lines in 'dpctl dump-flows' 2) check that the queues are actually receiving traffic and are configured as you expect: switch$ sudo /sbin/tc -s -d -p qdisc show switch$ sudo /sbin/tc -s -d -p class show dev eth0.3 (or whatever the appropriate ethernet device is) the queues created by 'dpctl add-queue' are Linux TC (traffic control) queues in the kernel (btw, Open vSwitch uses the same underlying mechanism for its queues). you can read about them with 'man tc' or at these websites: http://linux-ip.net/articles/Traffic-Control-HOWTO/ and http://lartc.org/howto/lartc.qdisc.html good luck! Andrew _______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
