Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 1
    The ID is 04f9:01ea, and isn't changing. The "Bus" (001), is which USB host device you connected it to. The "Device" is a connection specific entry of how the system internally refers to this device. It is expected to change, and can't be fixed. You might be able to put the forwarding into a udev rule, or write a script to parse the output if lsusb -d 04f9:01ea. You might be able to forward it by 04f9:01ea (though maybe not as there could be two matching devices). Commented Oct 13, 2024 at 19:39
  • @DavidG. Thanks, that's a good idea. I see this option for VMs but not for LXC containers. Do you know how forwarding by VendorID/DeviceID works for containers? Commented Oct 14, 2024 at 6:54
  • Sorry, can't specifically help you there, but: The LXC container's filesystem may be in your parent filesystem, allowing udev to write into it. Mind you, a symlink probably wouldn't work as the container couldn't see the target Instead you would need to make a device node. Commented Oct 14, 2024 at 7:00
  • @DavidG. Ok, I switched the entire system from LXC to a VM and now it all works great. Thanks for the hint Commented Oct 14, 2024 at 8:01