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.

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

WWAN interfaces still need ifname in device model #4484

Open
eriknordmark opened this issue Dec 13, 2024 · 0 comments
Open

WWAN interfaces still need ifname in device model #4484

eriknordmark opened this issue Dec 13, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@eriknordmark
Copy link
Contributor

Please provide information requested in the template below as much as possible.

Describe the bug

The commit message and code in 65852ac intended to allow for WWAN interfaces to be indenfied by a PCI address or USB address in order to handle the dynamic and random order the wwan interfaces might be numbered by the kernel.

However, for management ports (and potentially for app-shared ports as well) we do need to determine the kernel ifname before we can interact with the kernel/dhcpcd (e.g., to configure the kernel netlink and IP addresses), and for the logic in zedcloud/send.go to send requests to the controller using a particular interface. That type of logic would need to use the PCI address, USB address, or USB prod to determine the ifname dynamically.

Without this we see errors in the logs of the form "missing interface name" from SendOnIntf()

@eriknordmark eriknordmark added the bug Something isn't working label Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants