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

Introduce new network interface type vcan #301

Open
2 tasks
mirenz1 opened this issue Aug 29, 2024 · 0 comments
Open
2 tasks

Introduce new network interface type vcan #301

mirenz1 opened this issue Aug 29, 2024 · 0 comments
Labels
component: carl Mostly related to CARL. component: carl-api Mostly related to the opendut-carl-api component: edgar Mostly related to EDGAR. component: lea Mostly related to LEA. type: enhancement Fulfills a need or requirement by improving an existing functionality.

Comments

@mirenz1
Copy link
Contributor

mirenz1 commented Aug 29, 2024

Derived from #276 there are different configuration options for a physical and virtual CAN interface, hence they should be treated as different interface types.

  • network interface type for vcan is supported
  • only supported configuration options can be configured for type vcan
@mirenz1 mirenz1 added this to openDuT Aug 29, 2024
@mirenz1 mirenz1 converted this from a draft issue Aug 29, 2024
@mirenz1 mirenz1 added component: carl Mostly related to CARL. component: edgar Mostly related to EDGAR. component: lea Mostly related to LEA. type: enhancement Fulfills a need or requirement by improving an existing functionality. component: carl-api Mostly related to the opendut-carl-api labels Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: carl Mostly related to CARL. component: carl-api Mostly related to the opendut-carl-api component: edgar Mostly related to EDGAR. component: lea Mostly related to LEA. type: enhancement Fulfills a need or requirement by improving an existing functionality.
Projects
Status: Backlog
Development

No branches or pull requests

1 participant