I have been looking into some weird behavior, and I am not sure whether it is a bug or a feature.
When a VIF with index v gets deleted, the MFC routes does not get updated, which means that there can be routes pointing to that VIF. On datapath, when packet hits that route, the VIF validity will be checked and will not be sent to that device (but still, the route does not get updated). Now, if the user creates another VIF with the same index v but different underlay device, the same route will forward the traffic to that device. It is relevant to mention that when user adds a MFC route, only the active VIFs are used, so the flow of adding a route with dummy VIF indices and then connecting those VIF indices to real device is not supported. The only way to create a MFC route that has non existing VIFs is to create one with existing VIFs and then delete them. Do we really want to support that? To me, it looks like a buggy flow and I suggest that upon VIF deletion, the MFC routes will be updated to not point to any non existing VIF indices.
