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
icmp responder nse throws the following error cannot support any of the requested mechanism when sriov forwarder sends service request with {"mechanism_preferences":{"+0":{"cls":"REMOTE","type":"NOOP"}}} (is the cls parameter valid when nsc and nse are in the same worker node ?)
Logs at the NSE side (when service request arrived at NSE request handler, it looks mechanism preference is already suppressed by NSMgr, may be because of cls set with Remote ?) :
SR-IOV forwarder works only for remote cases. For the local cases there should be some other more efficient solutions like using VPP forwarder with tup interfaces.
I guess that we can discuss this with @edwarnicke.
icmp responder nse throws the following error
cannot support any of the requested mechanism
when sriov forwarder sends service request with{"mechanism_preferences":{"+0":{"cls":"REMOTE","type":"NOOP"}}}
(is the cls parameter valid when nsc and nse are in the same worker node ?)Logs at the forwarder side:
Logs at the NSE side (when service request arrived at NSE request handler, it looks mechanism preference is already suppressed by NSMgr, may be because of cls set with Remote ?) :
Steps to reproduce:
Running this example on a single node k8s cluster.
The text was updated successfully, but these errors were encountered: