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
Currently USBPcapCMD allows filtering by device address. The address gets saved between subsequent extcap starts. This is ok if the user does not reconnect the device and the device address stays intact.
It might be worthwhile to allow specifying filtered devices using port numbers. When filtered device is connected via hub, the full "path" should be used (e.g. 1:2:3 is when device is connected via two hubs in following way [Root Hub port 1] <- [USB Hub port 2] <- [USB Hub port 3] <- [device]).
The text was updated successfully, but these errors were encountered:
I haven't done any windows kernel work, and I'm not too familiar with this code base, but if there is enough information (files/functions in this codebase you think are in scope for modification) to make a shot at this that is reasonably likely to work and you be on board with, I could give it a go.
Currently USBPcapCMD allows filtering by device address. The address gets saved between subsequent extcap starts. This is ok if the user does not reconnect the device and the device address stays intact.
It might be worthwhile to allow specifying filtered devices using port numbers. When filtered device is connected via hub, the full "path" should be used (e.g. 1:2:3 is when device is connected via two hubs in following way [Root Hub port 1] <- [USB Hub port 2] <- [USB Hub port 3] <- [device]).
The text was updated successfully, but these errors were encountered: