Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

KNI interfaces come up as "no carrier" when NAT creates them #4

Open
gshimansky opened this issue Feb 1, 2019 · 2 comments
Open

KNI interfaces come up as "no carrier" when NAT creates them #4

gshimansky opened this issue Feb 1, 2019 · 2 comments
Assignees
@gshimansky

Comments

@gshimansky
Copy link
Contributor

Starting with recent DPDK versions KNI interfaces are created with "no carrier" state. This is a link with discussion about introducing this change https://mails.dpdk.org/archives/dev/2018-August/110551.html. NAT should be able to do something like echo 1 > /sys/devices/virtual/net/myKNI/carrier when an interface appears in the system.
@gshimansky gshimansky self-assigned this Feb 1, 2019
gshimansky added a commit that referenced this issue Feb 1, 2019
@gshimansky
Implemented writing to carrier file to enable it when bringing up an …
27a04c6 
…interface

Fix for #4
@RajalakshmiPrabahakar
Copy link

Hi Is myKNI interface is created inside the pod. Need clarity on the same. I am also facing similar issue. Thank you

@leoluk
Copy link

leoluk commented Mar 8, 2022 •
edited
Loading

Sadly nff-go is pretty much dead - Intel stopped all support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gshimansky gshimansky

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@leoluk @gshimansky @RajalakshmiPrabahakar