Hi, Thanks for your answer!
On 26 February 2015 at 07:21, Yusuke Iwase <[email protected]> wrote: > Hi Clément, > > I don't think the above command is wrong. > > $ curl -X GET http://localhost:8080/stats/groupdesc/1 > { > "1": [ > { > "type": "SELECT", > "group_id": 1, > "buckets": [ > { > "watch_port": 2, > "weight": 1000, > "watch_group": 4294967295, > "actions": [ > "OUTPUT:2" > ] > }, > { > "watch_port": 3, > "weight": 1, > "watch_group": 4294967295, > "actions": [ > "PUSH_VLAN:33024", > "SET_FIELD: {vlan_vid:4097}", > "OUTPUT:3" > ] > } > ] > } > ] > } > > How about capturing the output packets at port 3? > I captured packets at port 3, VLAN-tagged packets were output. > (Please see attached png file.) > I tried to do that but didn't manage to only capture these packets (I don't see s1-eth3 in the list of the interfaces where I can capture packets in Wireshark). What filter do you apply to do that in Wireshark? > By the way, did you assign VLAN ID to Host 3 (which is connected to port 3 > of switch)? > If not, I think Host 3 cannot reply for VLAN-tagged packets. > I'm not sure to understand what you mean by "assign VLAN ID to Host 3". Can you please elaborate? To port 3 I have a switch connected (and a rule which forwards the packet depending on the IP destination address and not on the VLAN id so it should always work). I attached a file with my rules. Best, Clément
mixed
Description: Binary data
------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________ Ryu-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ryu-devel
