You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A device selector file might contain devices that do not exist on the host when the forwarder is starting.
Devices are stored in a map, thus it's non-deterministic when InitLinks() will try to process the missing interface, but when it does it will return without considering the remaining devices. (The outcome might be different among the running vpp forwarders.)
This might result in issues when for example trying to use Remote VLAN NSE with an interface that got ignored, hence the forwarder/vpp will not know about it.
IMHO an error during InitLinks should either be considered fatal, or the code should filter out devices that does not exist on the host without skipping others.
So, basically the question is if a device selector file with unknown interfaces is considered an error or not.
The text was updated successfully, but these errors were encountered:
A device selector file might contain devices that do not exist on the host when the forwarder is starting.
Devices are stored in a map, thus it's non-deterministic when InitLinks() will try to process the missing interface, but when it does it will return without considering the remaining devices. (The outcome might be different among the running vpp forwarders.)
This might result in issues when for example trying to use Remote VLAN NSE with an interface that got ignored, hence the forwarder/vpp will not know about it.
IMHO an error during InitLinks should either be considered fatal, or the code should filter out devices that does not exist on the host without skipping others.
So, basically the question is if a device selector file with unknown interfaces is considered an error or not.
The text was updated successfully, but these errors were encountered: