Using Wine version 1.8 on Ubuntu 14.04.5 I'm trying to use a AVRT5 APRS amateur radio GPRS tracker which has a serial interface. The device is supplied with a Prolific USB serial converter which comes up as /dev/ttyUSB0 which I have sym linked to COM1
The bundled GPRS tracker config software installs and runs OK under Wine. But my attempts to sniff the serial port traffic fails using all the standard Linux methods I know.
I also tried using the Windows program Serial Port Monitor under Wine http://www.eltima.com/products/serial-port-monitor/ . This program says it cannot detect any serial ports.
Under Windows 7 the config program and Serial Port Monitor both work well and I can intercept all the serial traffic
Any ideas please folks?
Bill
On Tue, Nov 29, 2016 at 1:22 AM Bill Lionheart billlionheart@gmail.com wrote:
Using Wine version 1.8 on Ubuntu 14.04.5 I'm trying to use a AVRT5 APRS amateur radio GPRS tracker which has a serial interface. The device is supplied with a Prolific USB serial converter which comes up as /dev/ttyUSB0 which I have sym linked to COM1
Can you please cd into your dosdevices folder and run this command?
ls -Fl
(that's an uppercase F and a lowercase L)
Then we will also need to see permissions of the serial device, so run this:
ls -l /dev/ttyUSB0
That's a lowercase L again... and run this too:
id -a
With all this info we can rule out a couple problems, chief among them: 1. Is the symlink named correctly and actually pointing to something that exists 2. Do you actually have permissions to access the serial port
If you provide the output of all three of these commands, we should be able to help.
-Chris
On 27 November 2016 at 22:53, Bill Lionheart billlionheart@gmail.com wrote:
The bundled GPRS tracker config software installs and runs OK under Wine. But my attempts to sniff the serial port traffic fails using all the standard Linux methods I know.
Which were those, and what happens?
I also tried using the Windows program Serial Port Monitor under Wine http://www.eltima.com/products/serial-port-monitor/ . This program says it cannot detect any serial ports.
Without knowing much about the software in question, I think there's a good chance it works by hooking into the (Windows) kernel driver for the serial port, or doing something similar. Perhaps that could be made to work in Wine, but you'll likely have much more success with intercepting the traffic on the Linux side.
Thanks for your reply Henri,
I tried socat with a virtual serial port but I could only see what the config program sent and it got no reply. And slsniff ,sltrace and jpnevulator. All prevented the config program seeing the device. Morre details on my post https://forum.winehq.org/viewtopic.php?f=8&t=28031 on Wine-hq forum
I also tried usb monitoring with wireshark and it did not stop the program running but I didnt understand the output and I couldnt see anything I expected so maybe I just didnt get it. Just now though
Actually just now I tried tshark following exactly this suggestion https://ludovicrousseau.blogspot.co.uk/2014/10/ccid-usb-spy-using-wireshark...., this worked perfectly and did not prevent the two way serial communications.
So the moral of this problem is for serial port sniffing of a Windows program running under Wine, tshark. As I understand it tshark is just command line wire shark. Main thing is it just worked and saved all the serial traffic in a file.
Thanks for all the help and encouragement (including emails off the list), and for Bob Wye for encouraging me to post on wine-devel. I hope this will also be of some help in the future for wine developers in diagnosing serial communications problems to know that tshark is probably worth trying first (for a USB to serial converter at least)
Best wishes
Bill
On 4 December 2016 at 12:05, Henri Verbeet hverbeet@gmail.com wrote:
On 27 November 2016 at 22:53, Bill Lionheart billlionheart@gmail.com wrote:
The bundled GPRS tracker config software installs and runs OK under Wine. But my attempts to sniff the serial port traffic fails using all the standard Linux methods I know.
Which were those, and what happens?
I also tried using the Windows program Serial Port Monitor under Wine http://www.eltima.com/products/serial-port-monitor/ . This program says it cannot detect any serial ports.
Without knowing much about the software in question, I think there's a good chance it works by hooking into the (Windows) kernel driver for the serial port, or doing something similar. Perhaps that could be made to work in Wine, but you'll likely have much more success with intercepting the traffic on the Linux side.
On 4 December 2016 at 18:17, Bill Lionheart billlionheart@gmail.com wrote:
I tried socat with a virtual serial port but I could only see what the config program sent and it got no reply. And slsniff ,sltrace and jpnevulator. All prevented the config program seeing the device. Morre details on my post https://forum.winehq.org/viewtopic.php?f=8&t=28031 on Wine-hq forum
From that post it sounds like the communication from the
application/Wine to the sniffer is working fine, but either the communication from the sniffer to the device or from the device back to the sniffer not so much. My first guess would be to look at the way the sniffer communicates with the serial port (rate, etc.), but perhaps you've already verified that.
I also tried usb monitoring with wireshark and it did not stop the program running but I didnt understand the output and I couldnt see anything I expected so maybe I just didnt get it. Just now though
Actually just now I tried tshark following exactly this suggestion https://ludovicrousseau.blogspot.co.uk/2014/10/ccid-usb-spy-using-wireshark...., this worked perfectly and did not prevent the two way serial communications.
So the moral of this problem is for serial port sniffing of a Windows program running under Wine, tshark. As I understand it tshark is just command line wire shark. Main thing is it just worked and saved all the serial traffic in a file.
Glad you got it to work somehow. It's certainly odd that wireshark wouldn't work right while tshark would, since they're capturing the traffic in the same way. Since usbmon is more of a generic USB monitor though, is there any chance wireshark was capturing traffic from a different USB device, like e.g. a USB mouse?
-
Bill Lionheart -
Christopher Harrington -
Henri Verbeet