Hi Michael, It is present in 17.04 also.
/neale From: Michael Borokhovich <michael...@gmail.com> Date: Wednesday, 11 October 2017 at 19:09 To: "Neale Ranns (nranns)" <nra...@cisco.com> Cc: "Shaw, Jeffrey B" <jeffrey.b.s...@intel.com>, "vppsb-...@lists.fd.io" <vppsb-...@lists.fd.io>, vpp-dev <vpp-dev@lists.fd.io> Subject: Re: [vpp-dev] [vppsb-dev] Router plugin with VPP 1707 - incoming OSPF Hello packets are dropped by VPP Hi Neale, Was the mfib present in 1704? If not, maybe I can try router plugin with the recent fixes on 1704? Thanks, Michael. On Wed, Oct 11, 2017 at 4:59 AM, Neale Ranns (nranns) <nra...@cisco.com<mailto:nra...@cisco.com>> wrote: Hi Michael, It doesn’t work in 17.07 because we introduced the IP-multicast FIB (mfib). Your 224.0.0.0/24<http://224.0.0.0/24> route now needs to be in the mfib not the unicast FIB. Please try the mfib APIs I mentioned in my previous mail. Thanks, Neale From: Michael Borokhovich <michael...@gmail.com<mailto:michael...@gmail.com>> Date: Wednesday, 11 October 2017 at 05:34 To: "Neale Ranns (nranns)" <nra...@cisco.com<mailto:nra...@cisco.com>> Cc: "Shaw, Jeffrey B" <jeffrey.b.s...@intel.com<mailto:jeffrey.b.s...@intel.com>>, "vppsb-...@lists.fd.io<mailto:vppsb-...@lists.fd.io>" <vppsb-...@lists.fd.io<mailto:vppsb-...@lists.fd.io>>, vpp-dev <vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>> Subject: Re: [vpp-dev] [vppsb-dev] Router plugin with VPP 1707 - incoming OSPF Hello packets are dropped by VPP Hi Neale, In the router plugin, the code below ("vppsb/router/router/tap_inject.c") should make sure that incoming multicast packets are forwarded from VPP to Linux. However, it does not work if "FIN_VERSION" is not 1 (i.e., it works for 1609 but not for 1707). Do you have any idea why? Thanks! Michael. Hi Michael, Both of; vppctl ip mroute 224.0.0.0/8<http://224.0.0.0/8> via GigabitEthernet0/4/0 Accept vppctl ip mroute 224.0.0.0/8<http://224.0.0.0/8> via local Forward the first says you are accepting (i.e RPF checks on) GigE0/4/0 the second says you are ‘forwarding/replicating’ to VPP’s local IP stack. The mfib equivalent of the fib API you were using is; extern fib_node_index_t mfib_table_entry_special_add(u32 fib_index, const mfib_prefix_t *prefix, mfib_source_t source, mfib_entry_flags_t flags, index_t rep_dpo); if you include the flag MFIB_ENTRY_ACCEPT_ALL_ITF then mfib will accept from any incoming interface, hence you won’t need an explicit ‘Accept’ rule. But this API is strict about the last argument ‘dpo’ being a replicate DPO type. See the mfib_test.c examples on how to construct one for use with the API.
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
