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
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/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 via 2.1.1.4 gre1
and you must specify the next hop, like on an ethernet.
/neale
From: [email protected] <[email protected]> on behalf of 叶东岗 via
lists.fd.io <[email protected]>
Date: Wednesday, 17 March 2021 at 10:54
To: Vijay Kumar Nagaraj <[email protected]>, [email protected]
<[email protected]>
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
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
create teib gre1 peer 3.3.3.3 nh 1.1.1.2
ip route add 3.3.3.3/32 via gre1
create teib gre1 peer 4.4.4.4 nh 1.1.1.3
ip route add 4.4.4.4/32 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 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: '[email protected]<mailto:[email protected]>'
<[email protected]><mailto:[email protected]>
Cc: [email protected]<mailto:[email protected]>
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 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 <[email protected]<mailto:[email protected]>>
Date: Mon, Feb 22, 2021 at 8:47 PM
Subject: Re: [vpp-dev] mgre interface get UNRESOLVED fib entry.
To: [email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>>,
[email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>>
From: [email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>> on behalf of 叶东岗 via
lists.fd.io<http://lists.fd.io>
<[email protected]<mailto:[email protected]>>
Date: Monday, 22 February 2021 at 13:53
To: [email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>>
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<http://1.1.1.2/24>
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<http://2.1.1.2/32>
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<http://2.1.1.2/32>, so it’s not
a valid neighbour, hence the UNRESOLVED.
/neale
DBGvpp# show ip fib 3.3.3.3/32<http://3.3.3.3/32>
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<http://3.3.3.3/32> 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<http://0.0.0.0/0>] memif1/0: mtu:9000 next:1
ffffffffffff02fe049eea920806
[@1] ipv4-glean: [src:1.1.1.0/24<http://1.1.1.0/24>] 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<http://1.1.1.1/32>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#18951): https://lists.fd.io/g/vpp-dev/message/18951
Mute This Topic: https://lists.fd.io/mt/80823285/21656
Group Owner: [email protected]
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-