Hey, On Tue, Feb 3, 2015 at 2:19 PM, Sabyasachi Sengupta < sabyasachi.sengu...@alcatel-lucent.com> wrote:
> > Hi, > > I'm trying to set up BFD between two vlans created on different bridges > running on different hosts. I noticed that unless bfd:bfd_remote_dst_mac is > specified while setting up the BFD, the packet never leaves the host switch > due to "skipping output to input port". Looking at RFC 5880/5881, there is > no specification about the encapsulating packet itself, so I reckon this > should be implementation dependent. I'm wondering if it makes sense to have > a dummy (default) mac address as rmt_eth_dst so that > bfd_should_process_flow does not flag the outgoing as something to be > processed as a received packet? Thoughts? If so, I can send over a patch.. > > bfd_should_process_flow() has nothing to do with sending bfd control packets. If you do not specify 'bfd_local_src_mac' or 'bfd_local_dst_mac', the inner packet will use the OpenFlow port's mac as src mac and 00:23:20:00:00:01 as dest mac. And you should have no issue sending the bfd control packets. Could you show me you ovs configuration (ovs-vsctl show output, and on which port you enable bfd)? I suspect there could be something wrong with the configuration... Thanks, Alex Wang, > Thanks, > Sabya > _______________________________________________ > dev mailing list > dev@openvswitch.org > http://openvswitch.org/mailman/listinfo/dev > _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
