Hi Neale, Thanks for sharing the patch.
While I debugged today with gdb I found that fib_index value in the if block always used to be 0. The I traced the code and found that though fib_index_by_sw_if_index field is set in ip4_main, the call to fib_table_get_index_for_sw_if_index() always yields a 0 that is causing the teib to get added into the wrong FIB (in the problem case, it was always added to default fib which is fib 0) On similar lines to your patch, I simply commented out the call to fib_table_get_index_for_sw_if_index() and use the outer fib_index (which is nh_fib_index in your patch). This patch would ensure teib gets added properly. I am building the change. I will update after testing. Thank you for the support. Regards, Vijay Kumar N On Sat, Mar 20, 2021 at 1:14 AM Neale Ranns <ne...@graphiant.com> wrote: > Hi Vijay, > > > > I was able to re-produce your issue. Please try with: > > https://gerrit.fd.io/r/c/vpp/+/31695 > > > > /neale > > > > *From: *Vijay Kumar Nagaraj <vijay...@microsoft.com> > *Date: *Friday, 19 March 2021 at 19:12 > *To: *Neale Ranns <ne...@graphiant.com>, Vijay Kumar < > vjkumar2...@gmail.com> > *Cc: *y...@wangsu.com <y...@wangsu.com>, vpp-dev@lists.fd.io < > vpp-dev@lists.fd.io> > *Subject: *RE: [vpp-dev] mgre interface get UNRESOLVED fib entry. > > Hi Neale, > > > > I have captured the output of “show fib entry 81” that is related to the > route of the overlay and GRE peer. > > In the output, the adjacency/FIB entry looks fine for me. I have followed > all the configurations exactly as you mentioned below but there is no luck. > All > the packets are dropped as blackholed packets (highlighted in red) > > The only difference between us is the fib-idx is 1 in my case. In your > example there is no outer fib-idx in create gre tunnel cmd or either create > teib cmd. > > > > Topology and config > > ============================== > > Strongswan VM (20.20.99.215, gre peer 2.2.2.1) > <=======================> VPP cluster (20.20.99.99, gre peer 2.2.2.2) > > > > Configuration on VPP side > > ================ > > create gre tunnel src *20.20.99.99* outer-table-id 1 instance 1 multipoint > set interface ip addr gre1 2.2.2.2/32 > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F2.2.2.2%2F32&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192691263%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=%2BsCTdeX3Z%2Bvp4smOeUAUfl6GpmXZbGRSGgbtM9hcYx0%3D&reserved=0> > set interface state gre1 up > create teib gre1 peer 2.2.2.1 nh-table-id 1 nh *20.20.99.215 * > > ip route add 7.7.7.7/32 > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F7.7.7.7%2F32&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192701256%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=kyEGUcXvxn%2FFWf2uqc%2BRRkbE2wOWVV6vmX8rZdvjvwc%3D&reserved=0> > table > 1 via 2.2.2.1 gre1 > > > > > > vpp# show adj > > [@0] ipv4-glean: loop0: mtu:9000 next:1 ffffffffffffdead000000000806 > > [@1] ipv4-glean: loop1: mtu:9000 next:2 ffffffffffffdead000000010806 > > [@2] ipv4 via 0.0.0.0 memif0/0: mtu:65535 next:3 > > [@3] ipv4 via 0.0.0.0 memif0/1: mtu:65535 next:4 > > [@4] ipv4 via 0.0.0.0 memif0/2: mtu:65535 next:5 > > [@5] ipv4 via 0.0.0.0 memif128/0: mtu:65535 next:6 > > [@6] ipv4 via 0.0.0.0 memif128/1: mtu:65535 next:7 > > [@7] ipv4 via 0.0.0.0 memif128/2: mtu:65535 next:8 > > [@8] ipv4 via 0.0.0.0 memif192/0: mtu:65535 next:9 > > [@9] ipv4 via 0.0.0.0 memif192/1: mtu:65535 next:10 > > [@10] ipv4 via 0.0.0.0 memif192/2: mtu:65535 next:11 > > [@11] ipv4-glean: VirtualFuncEthernet0/7/0.1556: mtu:9000 next:3 > fffffffffffffa163ec2b4f4810006140806 > > [@12] ipv4 via 0.0.0.0 memif210/0: mtu:65535 next:12 > > [@13] ipv4 via 0.0.0.0 memif210/1: mtu:65535 next:13 > > [@14] ipv4 via 0.0.0.0 memif210/2: mtu:65535 next:14 > > [@15] ipv4 via 2.2.2.1 gre1: mtu:9000 next:15 > 4500000000000000fe2fcd6c14146363141463d700000800 > > stacked-on entry:81: > > [@3]: ipv4 via 20.20.99.215 VirtualFuncEthernet0/7/0.1556: mtu:1500 > next:16 fa163e4b6b42fa163ec2b4f4810006140800 > > [@16] ipv4 via 20.20.99.215 VirtualFuncEthernet0/7/0.1556: mtu:1500 > next:16 fa163e4b6b42fa163ec2b4f4810006140800 > > vpp# > > vpp# > > vpp# show gre tunnel > > [0] instance 1 src 20.20.99.99 dst 0.0.0.0 fib-idx 1 sw-if-idx 18 payload > L3 multi-point > > vpp# > > vpp# > > vpp# show teib > > [0] gre1:2.2.2.1 via [1]:20.20.99.215/32 > > vpp# > > vpp# > > vpp# show ip fib > > NWU, fib_index:1, flow hash:[src dst sport dport proto ] epoch:0 > flags:none locks:[API:2, adjacency:2, ] > > 0.0.0.0/0 > > unicast-ip4-chain > > [@0]: dpo-load-balance: [proto:ip4 index:55 buckets:1 uRPF:66 to:[0:0]] > > [0] [@0]: dpo-drop ip4 > > 0.0.0.0/32 > > unicast-ip4-chain > > [@0]: dpo-load-balance: [proto:ip4 index:56 buckets:1 uRPF:78 to:[0:0]] > > [0] [@0]: dpo-drop ip4 > > 2.2.2.1/32 > > UNRESOLVED > > 7.7.7.7/32 > > unicast-ip4-chain > > [@0]: dpo-load-balance: [proto:ip4 index:83 buckets:1 uRPF:113 to:[0:0]] > > [0] [@6]: ipv4 via 2.2.2.1 gre1: mtu:9000 next:15 > 4500000000000000fe2fcd6c14146363141463d700000800 > > stacked-on entry:81: > > [@3]: ipv4 via 20.20.99.215 VirtualFuncEthernet0/7/0.1556: > mtu:1500 next:16 fa163e4b6b42fa163ec2b4f4810006140800 > > 20.20.99.0/32 > > unicast-ip4-chain > > [@0]: dpo-load-balance: [proto:ip4 index:63 buckets:1 uRPF:86 to:[0:0]] > > [0] [@0]: dpo-drop ip4 > > 20.20.99.0/24 > > unicast-ip4-chain > > [@0]: dpo-load-balance: [proto:ip4 index:62 buckets:1 uRPF:85 to:[0:0]] > > [0] [@4]: ipv4-glean: VirtualFuncEthernet0/7/0.1556: mtu:9000 next:3 > fffffffffffffa163ec2b4f4810006140806 > > 20.20.99.99/32 > > unicast-ip4-chain > > [@0]: dpo-load-balance: [proto:ip4 index:65 buckets:1 uRPF:90 to:[1:80]] > > [0] [@2]: dpo-receive: 20.20.99.99 on VirtualFuncEthernet0/7/0.1556 > > 20.20.99.215/32 > > unicast-ip4-chain > > [@0]: dpo-load-balance: [proto:ip4 index:82 buckets:1 uRPF:116 to:[0:0]] > > [0] [@5]: ipv4 via 20.20.99.215 VirtualFuncEthernet0/7/0.1556: > mtu:1500 next:16 fa163e4b6b42fa163ec2b4f4810006140800 > > 20.20.99.255/32 > > unicast-ip4-chain > > [@0]: dpo-load-balance: [proto:ip4 index:64 buckets:1 uRPF:88 to:[0:0]] > > [0] [@0]: dpo-drop ip4 > > 224.0.0.0/4 > > unicast-ip4-chain > > [@0]: dpo-load-balance: [proto:ip4 index:58 buckets:1 uRPF:80 to:[0:0]] > > [0] [@0]: dpo-drop ip4 > > 240.0.0.0/4 > > unicast-ip4-chain > > [@0]: dpo-load-balance: [proto:ip4 index:57 buckets:1 uRPF:79 to:[0:0]] > > [0] [@0]: dpo-drop ip4 > > 255.255.255.255/32 > > unicast-ip4-chain > > [@0]: dpo-load-balance: [proto:ip4 index:59 buckets:1 uRPF:81 to:[0:0]] > > [0] [@0]: dpo-drop ip4 > > vpp# > > vpp# > > vpp# show fib entry 81 > > 81@20.20.99.215/32 fib:1 index:81 locks:4 > > adjacency refs:1 entry-flags:attached, > src-flags:added,contributing,active, cover:60 > > path-list:[94] locks:2 uPRF-list:116 len:1 itfs:[14, ] > > path:[126] pl-index:94 ip4 weight=1 pref=0 attached-nexthop: > oper-flags:resolved, > > 20.20.99.215 VirtualFuncEthernet0/7/0.1556 > > [@0]: ipv4 via 20.20.99.215 VirtualFuncEthernet0/7/0.1556: mtu:1500 > next:16 fa163e4b6b42fa163ec2b4f4810006140800 > > Extensions: > > path:126 adj-flags:[refines-cover] > > recursive-resolution refs:1 src-flags:added, cover:-1 > > > > forwarding: unicast-ip4-chain > > [@0]: dpo-load-balance: [proto:ip4 index:82 buckets:1 uRPF:116 to:[0:0]] > > [0] [@5]: ipv4 via 20.20.99.215 VirtualFuncEthernet0/7/0.1556: > mtu:1500 next:16 fa163e4b6b42fa163ec2b4f4810006140800 > > Delegates: > > track: sibling:156 > > Children:{adj:15} > > Children:{fib-entry-track:16} > > vpp# > > vpp# > > vpp# ping 7.7.7.7 source gre1 > > > > Statistics: 5 sent, 0 received, 100% packet loss > > vpp# > > vpp# > > vpp# show node counters > > Count Node Reason > > 5 null-node blackholed packets > > 1 dpdk-input no error > > 2252 an_ppe_wfectrl wfectrl packets received > > 2252 an_ppe_wfectrl wfectrl replies sent > > 1799 an_ppe_wfectrl session stat request > received > > 1 an_ppe_wfectrl service construct config > request received > > 1 an_ppe_wfectrl service construct config > request success > > 1 an_ppe_wfectrl service config request > received > > 1 an_ppe_wfectrl service config request > success > > 374 an_ppe_wfectrl dpi stats request > received > > 374 an_ppe_wfectrl dpi stats request success > > 15 an_ppe_wfectrl nat stats request > received > > 15 an_ppe_wfectrl nat stats request success > > 1 arp-reply ARP replies sent > > 1 ip4-local ip4 source lookup miss > > 2 ethernet-input unknown vlan > > vpp# > > vpp# > > > > *From:* Neale Ranns [mailto:ne...@graphiant.com] > *Sent:* 18 March 2021 00:47 > *To:* Vijay Kumar <vjkumar2...@gmail.com> > *Cc:* y...@wangsu.com; Vijay Kumar Nagaraj <vijay...@microsoft.com>; > vpp-dev@lists.fd.io > *Subject:* [EXTERNAL] Re: [vpp-dev] mgre interface get UNRESOLVED fib > entry. > > > > Hi Vijay, > > > > Please ‘sh fib entry 81’ which, according to the adj on the gre tunnel, is > the FIB entry to reach the next-hop. > > > > /neale > > > > > > *From: *Vijay Kumar <vjkumar2...@gmail.com> > *Date: *Wednesday, 17 March 2021 at 18:48 > *To: *Neale Ranns <ne...@graphiant.com> > *Cc: *y...@wangsu.com <y...@wangsu.com>, Vijay Kumar Nagaraj < > vijay...@microsoft.com>, vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> > *Subject: *Re: [vpp-dev] mgre interface get UNRESOLVED fib entry. > > Hi Neale, > > > > I did the configuration exactly like you suggested above. But still the > ping from VPP to the overlay is failing as Blackholed packets. > > In my case both gre tunnel created and the teib peer created were in > fib-idx 1. My case is always non-zero fib > > > > Let me know if you tested mgre in non-zero fib? > > > > Some points FYI: - > > =============== > > 1) the fib entry for my overlay (7.7.7.7/32 > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F7.7.7.7%2F32&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192681261%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Rypof1ftX0zhFBUEKkAz2g5%2F38WvbGotdsSLN7cEya4%3D&reserved=0>) > was showing dpo-drop as pasted below. > > 2) The vpp version I am running is mentioned below. > > 3) I also applied the mGRE patch you shared yesterday. > > https://gerrit.fd.io/r/c/vpp/+/31643 > <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgerrit.fd.io%2Fr%2Fc%2Fvpp%2F%2B%2F31643&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192691263%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=7X%2BTYbgZDm%2BtOhzPNVSOcXPHCZ26voIyCuC5cM9IYpc%3D&reserved=0> > > > > Topology and config > > ============================== > > Strongswan VM (20.20.99.215, gre peer 2.2.2.1) > <=======================> VPP cluster (20.20.99.99, gre peer 2.2.2.2) > > > > Configuration on VPP side > > ================ > > create gre tunnel src *20.20.99.99* outer-table-id 1 instance 1 multipoint > set interface ip addr gre1 2.2.2.2/32 > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F2.2.2.2%2F32&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192691263%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=%2BsCTdeX3Z%2Bvp4smOeUAUfl6GpmXZbGRSGgbtM9hcYx0%3D&reserved=0> > set interface state gre1 up > create teib gre1 peer 2.2.2.1 nh-table-id 1 nh *20.20.99.215 * > > ip route add 7.7.7.7/32 > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F7.7.7.7%2F32&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192701256%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=kyEGUcXvxn%2FFWf2uqc%2BRRkbE2wOWVV6vmX8rZdvjvwc%3D&reserved=0> > table > 1 via 2.2.2.1 gre1 > > > > > > FIB entry and logs > > ======================= > > NWU, fib_index:1, flow hash:[src dst sport dport proto ] epoch:0 > flags:none locks:[API:2, ] > 7.7.7.7/32 > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F7.7.7.7%2F32&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192711252%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=qhpzsawR3umblvbcEo4l8g2uYA7MTjRve75tSl3QytI%3D&reserved=0> > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:85 buckets:1 uRPF:115 to:[0:0]] > [0] [@6]: ipv4 via 2.2.2.1 gre1: mtu:9000 next:15 > 4500000000000000fe2fcd6c14146363141463d700000800 > stacked-on entry:81: > [@1]: dpo-drop ip4 > 20.20.99.99/32 > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F20.20.99.99%2F32&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192711252%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=o4qFNOnWhQ%2FpkK1OiHq3wN5NfkvsTBlWI3ycahOkRFg%3D&reserved=0> > unicast-ip4-chain > [@0]: dpo-load-balance: [proto:ip4 index:65 buckets:1 uRPF:90 to:[0:0]] > [0] [@2]: dpo-receive: 20.20.99.99 on VirtualFuncEthernet0/6/0.1556 > > vpp# ping 7.7.7.7 source gre1 > > Statistics: 5 sent, 0 received, 100% packet loss > vpp# show node counters > Count Node Reason > 12 null-node blackholed packets > 945 an_ppe_wfectrl wfectrl packets received > 945 an_ppe_wfectrl wfectrl replies sent > 754 an_ppe_wfectrl session stat request > received > 1 an_ppe_wfectrl service construct config > request received > 1 an_ppe_wfectrl service construct config > request success > 1 an_ppe_wfectrl service config request > received > 1 an_ppe_wfectrl service config request > success > 157 an_ppe_wfectrl dpi stats request > received > 157 an_ppe_wfectrl dpi stats request success > 6 an_ppe_wfectrl nat stats request > received > 6 an_ppe_wfectrl nat stats request success > vpp# > vpp# > > vpp# show version > vpp v20.05.1-2~gca5e4556e-dirty built by an-vijay_kumar on af37e99caca7 at > 2021-03-17T14:31:40 > vpp# > vpp# > > > > > > > > On Wed, Mar 17, 2021 at 5:26 PM Neale Ranns <ne...@graphiant.com> wrote: > > > > Can I suggest a few changes. You should consider a mgre interface much > like ethernet when assigning addresses. So it should be; > > > > set interface state eh0 up > set interface ip addr eth0 1.1.1.1/24 > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F1.1.1.1%2F24&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192721243%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=OsS6svdhBiKPk7lbxKEPHjjrKJpZ9byvo3S9PPVHrNA%3D&reserved=0> > create gre tunnel src 1.1.1.1 instance 1 multipoint > set interface state gre1 up > set interface ip addr gre1 2.1.1.2/ > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F2.1.1.2%2F&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192721243%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=FcSYYLHz%2BGJbXellfqj6z3AFVx388f3T01%2FqvDp9LKg%3D&reserved=0> > 28 > > > > these are the equivalent of ARPs for hosts (the nh is the MAC address > equivalent) > create teib gre1 peer 2.1.1.3 nh 1.1.1.2 > create teib gre1 peer 2.1.1.4 nh 1.1.1.3 > > > then you can add whatever routes you have in the overlay via these GRE > peers > > ip route add 4.4.4.4/32 > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F4.4.4.4%2F32&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192731239%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=1gCxLJiHbGgtMWBB%2BXQM7n6U2otO6HdvSeelp6oC7dY%3D&reserved=0> > via 2.1.1.4 gre1 > > and you must specify the next hop, like on an ethernet. > > /neale > > > > > > *From: *vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> on behalf of 叶东岗 via > lists.fd.io > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.fd.io%2F&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192741237%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=eingSgNNeq0yBJIuB8M9OOI1L2NvQk4JIV7VzCqI9G4%3D&reserved=0> > <yedg=wangsu....@lists.fd.io> > *Date: *Wednesday, 17 March 2021 at 10:54 > *To: *Vijay Kumar Nagaraj <vijay...@microsoft.com>, vpp-dev@lists.fd.io < > vpp-dev@lists.fd.io> > *Subject: *Re: [vpp-dev] mgre interface get UNRESOLVED fib entry. > > set interface state eh0 up > set interface ip addr eth0 1.1.1.1/24 > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F1.1.1.1%2F24&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192741237%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Y%2BSBll0ke6EFDxYHE87ZoGew90ZjlOTsAyHT3VDUjKo%3D&reserved=0> > create gre tunnel src 1.1.1.1 instance 1 multipoint > set interface state gre1 up > set interface ip addr gre1 2.1.1.2/32 > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F2.1.1.2%2F32&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192751229%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=mAtZ3FXhYHdQ9P6HzQTNqj52PG%2B0XTJ0HZgKRzhzp3A%3D&reserved=0> > create teib gre1 peer 3.3.3.3 nh 1.1.1.2 > ip route add 3.3.3.3/32 > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F3.3.3.3%2F32&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192761225%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=VdTPE59m0rnNaAgkvR1pAsveXKypUihaPv%2BAUsy7pZI%3D&reserved=0> > via gre1 > create teib gre1 peer 4.4.4.4 nh 1.1.1.3 > ip route add 4.4.4.4/32 > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F4.4.4.4%2F32&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192761225%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=3CTLdjRD5VdZEkywkkXg2cEI67I6980RJq9m6Ji%2FJrQ%3D&reserved=0> > via gre1 > > this config works. > > 在 2021/3/17 下午5:28, Vijay Kumar Nagaraj 写道: > > Hi Yedg, > > > > Gentle reminder!! > > > > Hope you are doing fine. > > > > I am trying mGRE for a certain project at Microsoft and even I don’t have > much idea about exact config. I followed mGRE example in the fd.io > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Ffd.io%2F&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192771223%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=R7W0kP6xmVI44ouGynoz91D5L1rEuqBFRkYbnTJyYkU%3D&reserved=0> > wiki page but it is crashing when I configured multipoint tunnel, setup > route and tried to ping from VPP to the destination host > > > > Can you pls share me your mGRE config if it is working? > > > > > > *From:* Vijay Kumar N > *Sent:* 15 March 2021 11:09 > *To:* 'y...@wangsu.com' <y...@wangsu.com> <y...@wangsu.com> > *Cc:* vjkumar2...@gmail.com > *Subject:* RE: [vpp-dev] mgre interface get UNRESOLVED fib entry. > > > > Hi Yedg, > > > > Hope you are doing fine, I saw your recent query on vpp mailing list. > > > > Are you able to successfully test mGRE feature? > > Has the below config worked for you after Neale’s reply. > > > > I am trying mGRE for a certain project at Microsoft and even I don’t have > much idea about exact config. I followed mGRE example in the fd.io > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Ffd.io%2F&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192781215%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=y4AZjTECcMUbCZudtuOsK%2BXvx5N5zPTi0KVYPLNc0OQ%3D&reserved=0> > wiki page but it is crashing when I configured multipoint tunnel, setup > route and tried to ping from VPP to the destination host > > > > Can you pls share me your mGRE config if it is working? > > > > > > Regards. > > > > ---------- Forwarded message --------- > From: *Neale Ranns* <ne...@graphiant.com> > Date: Mon, Feb 22, 2021 at 8:47 PM > Subject: Re: [vpp-dev] mgre interface get UNRESOLVED fib entry. > To: y...@wangsu.com <y...@wangsu.com>, vpp-dev@lists.fd.io < > vpp-dev@lists.fd.io> > > > > > > > > *From: *vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> on behalf of 叶东岗 via > lists.fd.io > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.fd.io%2F&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192781215%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=iX7VxLQ8yuiKEc0ZNmda2dtHulIqTswpKD3%2BMFduUi4%3D&reserved=0> > <yedg=wangsu....@lists.fd.io> > *Date: *Monday, 22 February 2021 at 13:53 > *To: *vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> > *Subject: *[vpp-dev] mgre interface get UNRESOLVED fib entry. > > Hi: > > I try to config a mgre interface fellow those steps, then i get an > UNRESOLVED fib entry, is it right? I think it should be unicast-ip4-chain? > > any examples of mgre config? Thinks. > > > create memif socket id 1 filename /work/memif1 > create interface memif socket-id 1 master > set interface state memif1/0 up > set interface ip addr memif1/0 1.1.1.2/24 > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F1.1.1.2%2F24&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192791210%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=g2E%2BPvpFIOUAQLI%2FuWXN50iRJvspnc9HzmbijrX2mtc%3D&reserved=0> > set interface rx-mode memif1/0 interrupt > create gre tunnel src 1.1.1.2 instance 1 multipoint > set interface state gre1 up > set interface ip addr gre1 2.1.1.2/32 > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F2.1.1.2%2F32&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192801207%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=C43ii%2BIoKumQ7FSHwGfVKrM4bg7Yl5cBKYhPbz0vJeI%3D&reserved=0> > create teib gre1 peer 3.3.3.3 nh 1.1.1.1 > > 3.3.3.3 is not in the same subnet as 2.1.1.2/32 > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F2.1.1.2%2F32&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192801207%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=C43ii%2BIoKumQ7FSHwGfVKrM4bg7Yl5cBKYhPbz0vJeI%3D&reserved=0>, > so it’s not a valid neighbour, hence the UNRESOLVED. > > /neale > > > > > DBGvpp# show ip fib 3.3.3.3/32 > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F3.3.3.3%2F32&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192811203%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=%2B%2Bo2NN0CxRwwQrr4zVConU9Q1zDlYGf9%2BGrvAarZHFU%3D&reserved=0> > ipv4-VRF:0, fib_index:0, flow hash:[src dst sport dport proto flowlabel > ] epoch:0 flags:none locks:[adjacency:2, recursive-resolution:1, > default-route:1, ] > 3.3.3.3/32 > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F3.3.3.3%2F32&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192821197%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=ld%2BbtccniKiXKvZHOuJsxzBjR43tZ0Blq9Rp6JA5tvA%3D&reserved=0> > fib:0 index:16 locks:4 > adjacency refs:1 entry-flags:attached, > src-flags:added,contributing,active, cover:0 > path-list:[21] locks:2 uPRF-list:24 len:1 itfs:[2, ] > path:[25] pl-index:21 ip4 weight=1 pref=0 attached-nexthop: > oper-flags:resolved, > 3.3.3.3 gre1 > [@0]: ipv4 via 3.3.3.3 gre1: mtu:9000 next:4 > 4500000000000000fe2fb8cb010101010101010100000800 > stacked-on entry:11: > [@3]: ipv4 via 1.1.1.1 memif1/0: mtu:9000 next:3 > 02fe21058f7502fe049eea920800 > Extensions: > path:25 > recursive-resolution refs:1 src-flags:added, cover:-1 > > forwarding: UNRESOLVED > > > DBGvpp# show adj > [@0] ipv4-glean: [src:0.0.0.0/0 > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F0.0.0.0%2F0&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192821197%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=lsIpdT2gCA66qE1ktavUxp8DJepD0ZWREt1pqLABhbw%3D&reserved=0>] > memif1/0: mtu:9000 next:1 > ffffffffffff02fe049eea920806 > [@1] ipv4-glean: [src:1.1.1.0/24 > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F1.1.1.0%2F24&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192831194%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=LkA2JY1oEn9uMx9SiYXGkb5JYTjwVXM0F%2B4o7QbL6pU%3D&reserved=0>] > memif1/0: mtu:9000 next:1 > ffffffffffff02fe049eea920806 > [@2] ipv4 via 1.1.1.1 memif1/0: mtu:9000 next:3 > 02fe21058f7502fe049eea920800 > [@3] ipv4 via 3.3.3.3 gre1: mtu:9000 next:4 > 4500000000000000fe2fb8cb010101010101010100000800 > stacked-on entry:11: > [@3]: ipv4 via 1.1.1.1 memif1/0: mtu:9000 next:3 > 02fe21058f7502fe049eea920800 > > > DBGvpp# show teib > [0] gre1:3.3.3.3 via [0]:1.1.1.1/32 > <https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2F1.1.1.1%2F32&data=04%7C01%7Cvijaynag%40microsoft.com%7C017e3563375946808c3608d8e9794177%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637516055192841189%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Chnf04agJGAV%2BXPRh5SIBw2Z462NdWUZeGlLlSrlhD8%3D&reserved=0> > > > > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#18981): https://lists.fd.io/g/vpp-dev/message/18981 Mute This Topic: https://lists.fd.io/mt/80823285/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
