@b0rk I worked on a small utility in Swift to send active application context to a keyboard.
Needing to probe that context made the high level approach desirable and from there I also had easy access to a higher level than straight USB interaction: Custom HID device interaction.
If I were to attack a problem like the one you describe, this background would drive me to see if engaging at a similar higher level again would be doable.
@b0rk USB Ethernet devices are an entire subclass of USB, and ought to have common packets. They are mostly all handled by the kernel, so what do you want to do exactly? If you are trying to send/receive packets, the kernels will do that for you. Libpcap has routines that can help if you want to send packets at layer 2. What is your goal?
@mcr314 i want to send packets at layer 2 on Mac OS. In the past i’ve had a lot of problems with the OS intercepting the packets and closing my connections which is why I’m thinking of bypassing the OS as much as possible
@b0rk@mcr314 you’ll find a lot of usb nics don’t actually implement usb-cdc, instead they present old rndis style interface. Some try to do a composite mode thing to offer both, but that tends to break compatibility with one OS or another. You’ll also find many don’t implement hardware flow control, so if you’re too slow or too fast packets will be dropped. Even different runs from a vendor might implement different interfaces, as they just glue and ship.
@b0rk aside from the all powerful libusb you also have WebUSB available in Chrome and friends.
There is also node-usb which offers a WebUSB like interface. https://github.com/node-usb/node-usb
It seems like every other USB library is actually just "libusb in a trenchcoat", so it may be unavoidable, but starting with high-level bindings definitely seems reasonable. PyUSB is another decent wrapper, for the Python-inclined.
Add comment