Hi Wenxian, All interfaces require some IP configuration to become ‘IP enabled’ before they will accept IP traffic. There are 2 ways to IP enable an interface:
1) Add an IP address 2) Make the interface IP unnumbered to another interface that does have an IP address; ‘set int ip unnum gre0 <OTHER-INT>’ Hth, neale From: <[email protected]> on behalf of wenxian li <[email protected]> Date: Monday, 5 June 2017 at 04:48 To: "[email protected]" <[email protected]> Subject: [vpp-dev] Why ip address is mandatory for gre interface? Hi All, I got this question while trying VPP. I added a route pointing to gre interface: ip route add 1.1.1.1/32<http://1.1.1.1/32> via gre0 Before configuring ip address for gre0, the route does not work and packets are dropped with "ip4 adjacency drop". By showing the features of gre0, only ip4-drop is enabled. DBGvpp# sh int feat gre0 ip4-unicast: ip4-drop Then I configured an IP address on gre0, and it works now. DBGvpp# set int ip add gre 9.9.9.100/32<http://9.9.9.100/32> DBGvpp# sh int feat gre0 ip4-unicast: <--------------ip4_drop node is gone. My question is: why the ip address is mandatory for a point-to-point interface? Is there any special designed reason? From user's perspective, we don't need an ip for gre interface. GRE is served as an encap string only (Like the implementation of linux). Thanks, Wenxian
_______________________________________________ vpp-dev mailing list [email protected] https://lists.fd.io/mailman/listinfo/vpp-dev
