On Thu, Dec 07, 2017 at 02:44:36PM -0800, Kevin Lin wrote:
> Hi Ben,
>
> I’ve included the traces for an ARP request, and a ping. ovs-vswitchd also
> logs errors for the return traffic, but I didn’t include that as it seems
> redundant.
>
> root@ip-172-31-2-45:/# ovs-appctl ofproto/trace kelda-int
> 'arp,in_port=1,vlan_tci=0x0000,dl_src=02:00:0a:c5
> :34:1e,dl_dst=ff:ff:ff:ff:ff:ff,arp_spa=10.197.52.30,arp_tpa=10.203.4.66,arp_op=1,arp_sha=02:00:0a:c5:34:1e
> ,arp_tha=ff:ff:ff:ff:ff:ff'
> Flow:
> arp,in_port=1,vlan_tci=0x0000,dl_src=02:00:0a:c5:34:1e,dl_dst=ff:ff:ff:ff:ff:ff,arp_spa=10.197.52.30,arp_tpa=10.203.4.66,arp_op=1,arp_sha=02:00:0a:c5:34:1e,arp_tha=ff:ff:ff:ff:ff:ff
>
> bridge("kelda-int")
> -------------------
> 0. in_port=1,dl_src=02:00:0a:c5:34:1e, priority 32768
> load:0x2->NXM_NX_REG0[]
> resubmit(,1)
> 1. arp,dl_dst=ff:ff:ff:ff:ff:ff, priority 1000
> LOCAL
> output:NXM_NX_REG0[]
> -> output port is 2
> >>>> Cannot truncate output to patch port <<<<
Thanks for the details.
Would you mind testing this patch?
https://patchwork.ozlabs.org/patch/845908/
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
