On 10/27/17 8:43 PM, Jeff Barnhill wrote: > ping v4 loopback... > > jeff@VM2:~$ ip route list vrf myvrf > 127.0.0.0/8 dev myvrf proto kernel scope link src 127.0.0.1 > 192.168.200.0/24 via 192.168.210.3 dev enp0s8 > 192.168.210.0/24 dev enp0s8 proto kernel scope link src 192.168.210.2 > > Lookups shown in perf script were for table 255. Is it necessary to > put the l3mdev table first? If I re-order the tables, it starts > working:
Yes, we advise moving the local table down to avoid false hits (e.g., duplicate addresses like this between the default VRF and another VRF). I covered that and a few other things at OSS 2017. Latest VRF slides for users: http://schd.ws/hosted_files/ossna2017/fe/vrf-tutorial-oss.pdf
