On Wed, Nov 09, 2016 at 10:59:59PM -0500, Lax Clarke wrote: > Thank you for your advice! > > Sadly, I managed to run into a problem: packets do not forward after the > vlans are modified (even though I do see evidence of packets ingressing > into the bridges and matching the modify vlan rules). > I've looked at docs and tried many commands and tried to do my best.... > > 1) Here is how I added the openflow entries: > > # ovs-vsctl show > 7fd1e9d9-0a50-4dfa-bf3d-bedceb9600a6 > Bridge SUB > Port SUB > Interface SUB > type: internal > Port "ens1f0" > Interface "ens1f0" > Port "vnet2" > Interface "vnet2" > Bridge INT > Port "vnet3" > Interface "vnet3" > Port "ens1f1" > Interface "ens1f1" > Port INT > Interface INT > type: internal > ovs_version: "2.5.0" > > # ovs-ofctl add-flow SUB "in_port=1, actions=mod_vlan_vid:2600" > # ovs-ofctl add-flow INT "in_port=1, actions=mod_vlan_vid:2500"
The actions you specified modify the VLAN but then don't do anything with the packet. _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
