-
Notifications
You must be signed in to change notification settings - Fork 18
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
Software does not work on Kali Linux #7
Comments
Hi, I'm really sorry about that, there seems to be a problem with the G610, does the program detect your keyboard? I don't have the G610 at hand and I've asked multiple guys to collect Wireshark dumps for the G610 but nobody seems to have the time, can you please collect some dumps for different actions and lable each dump with the corresponding action, and then share them with me and I will have a look at them and solve the problem quickly. |
Hi, I don't know how to do it, but if you give me the instructions i will be happy to do it 😃
I don't know if the software detects the keyboard because when i open it, the mouse show the simbol that is loading something, then the software closes by itself.
…________________________________
From: MohamadSaada <[email protected]>
Sent: 25 August 2017 13:22
To: MohamadSaada/LogiGSK
Cc: marceeu; Author
Subject: Re: [MohamadSaada/LogiGSK] Software does not work on Kali Linux (#7)
Hi, I'm really sorry about that, there seems to be a problem with the G610, does the program detect your keyboard? I don't have the G610 at hand and I've asked multiple guys to collect Wireshark dumps for the G610 but nobody seems to have the time, can you please collect some dumps for different actions and lable each dump with the corresponding action, and then share them with me and I will have a look at them and solve the problem quickly.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#7 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/Ad5LQ4N6339c3U93hqyzQdUGoVublnbmks5sbq6PgaJpZM4PCiKF>.
|
@marceeu I'm sorry I didn't reply earlier, but somehow I missed your comment. If you can download a VM software like VirtualBox, and install a windows OS on that VM (guest OS). Then install a program like WireShark on the host machine. In the VM software, specify that the keyboard should be used in the guest OS(Windows). Install Logitech software on the windows guest OS. In the host OS run WireShark, and record traffic from the USB port that the keyboard is attached to. Once you start recording, run a specific effect through the Logitech software, record all the data that has been sent to the keyboard and save in a file named with that specific effect's name. Repeat the operation for as many different effects as you possibly can. Once you have all the different effects' files, send them to me through a link to a google drive or dropbox directory and I will take it from there. If I have these files I should solve the issue in no time. |
Hi Mo - I'm also not seeing the software work for my G610. I've got some technical chops so I should be able to get the Wireshark dumps to you in a little while if you still think that would help this issue? |
Update: The linux version of Wireshark is happy to decode USB, but the properties I can filter on doesn't seem to include source or destination address, so I'm getting all the keyboard USB activity too... |
So here's a capture with the keyboard "owned" by a Win10 VirtualBox guest via an Ubuntu host. This is just setting one individual key, because with effects on, the Software sends a massive amount of USB data. That's what you asked for, but it didn't seem right. Let me know if that's actually what you wanted. I've filtered out a bunch of other USB activity, but the key setting is the last few packets. |
Hi, I'm using the last dist of Kali linux, I,v tried everything, compile the pkg by myself, donwload the deb and rpm from the repo and installed they etc.. i can install the soft but when i open it nothing happens. I"m using a G610
The text was updated successfully, but these errors were encountered: