hostdisk.blogg.se

Logitech unifying software download page
Logitech unifying software download page








  1. #Logitech unifying software download page cracked
  2. #Logitech unifying software download page install
  3. #Logitech unifying software download page series
  4. #Logitech unifying software download page windows

Hitting the “Advanced” button: This also generated tons of USB traffic. If worst had come to worst, I would have just replicated these packets without knowing what they did. I made a gamble here and assumed logitech didn’t want this to be hard to do, and that this traffic was the program asking the dongle things like “Are you there? do you have any attached devices? what can you tell me about them?” and such.

logitech unifying software download page

Opening the program: This generated TONS of USB traffic that I really didn’t want to sift though. I went tested the logitech software by pressing buttons and watching the USB requests it generated. When I did that I got a lot of garbage, which I then had to sort through carefully and think about. The moral of the story is that usbmon doesn’t need no stinkin’ wireshark. Without the right setup packet, I kept getting USB I/O and USB pipe errors.

logitech unifying software download page

What didn’t dawn on me until I looked at the raw usbmon logs was that the values of the wValue, wIndex and wLength were reversed. I should have known something was fishy, because I knew the request length was 7 because 7 bytes were returned. a little endian interpretation would say the MSB was 1, then 1 then 0 so that the value is 6.įor the longest time I thought the wValue and wIndex of the control command I was trying to send were 0x1002 and 0x0200, because Wireshark was telling me that the setup packet in the USB request block was “21 09 10 02 02 00 07 00”. for example, if it received ‘011’ it would think that the most significant bit was 0, then 1 then 1, so it would say the decimal value was 3. This is basically the direction it “reads” data that is transmitted. For some reason, wireshark thinks USB is big endian. The I used wireshark to look at the output. Sudo mount -t debugfs none_debugfs /sys/kernel/debug I started out by mounting the debug filesystem so I could use usbmon (usb monitoring) which is some kind of linux utility. I paired and unpaired a few devices to test it.

#Logitech unifying software download page windows

I created a VM running windows XP, downloaded the software from logitech, and let the VM grab the usb dongle. This time around I installed virtual box from oracle (NOT the OSE edition, which doesn’t have usb extensions).

#Logitech unifying software download page install

It turns out it was mostly useless, due to the clunky interface, and I didn’t want to install pyusb on my windows partition, so I moved on to a different solution. I started by booting into windows and using a program called usblyser to analyze usb traffic. If within range of a paired receiver, it doesn’t make sense for a device to pair, because then your mouse would pair to other peoples receivers more or less at random (ever time you turned it on). Since these things are so tiny, and can be easily misplaced/stolen/eaten, I assumed that already paired devices would be willing to pair to another device given that they are not within range of a paired receiver. I figured I could take advantage of a case that the Logitech engineers must have planned for, loosing a receiver.

logitech unifying software download page

I decided my program really only needs to do one thing, which is to pair to devices not near other receivers. Thankfully I had another receiver and another machine to test on.

#Logitech unifying software download page cracked

Since I had already cracked a receiver open and soldered it onto the mobo of my EEEpc, I decided that 1) and 2) were out of the question.

  • Use one receiver per device (expensive in terms of usb ports).
  • Find a win/mac machine, pair, and basically pray that the devices never get unpaired.
  • This means that to use a keyboard and a mouse, you need to: There are no drivers, and this means there is no way to pair more than one device to a receiver.

    logitech unifying software download page

    After that, they are paired! This is awesome for windows/Mac users, because they can use the provided software to connect more devices. To pair to the first device, all you do is plug in the receiver, and turn on your peripheral.

    #Logitech unifying software download page series

    Just finished a reverse engineering and building a “driver” that will let you link more than one device to a Logitech unifying receiver in Linux! Yay! (Big thanks here goes to Kevin, who helped me through some bugs/was a console guru)įor those of you who haven’t used the “unified” series of products from logitech, the selling point is that you can have multiple wireless peripherals (Keyboards or mice) that all link up to single TINY USB dongle. *For those of you looking for something to let you attach more than one logitech device in linux, you should go to the downloads page.










    Logitech unifying software download page