From: Nicolae Mihalache <mache@abcpages.com>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: tcpdump equivalent for the serial port
Date: Fri, 12 Sep 2003 17:37:34 +0200 [thread overview]
Message-ID: <3F61E83E.402@abcpages.com> (raw)
Hello!
I'm interested if somebody has any ideea how to write a program that is able to sniff the data passing through a serial port the same way tcpdump is able to show the data passing through the ethernet cable, i.e. without disturbing the application that sends/receives the data.
I've seen few programs that basically work as tunnels opening a pseudo-console where the application connects and writing on the other side to the serial device. This approach is not very useful because I want to be able to start/stop my sniffer without interupting the communication and also the application can control different settings of the serial port which probably will not be forwarded by the tunnel.
Another sugestion was to monitor rather the application using ptrace than the serial port itself but this has the inconvenience that I only get the data when the application reads it not when it arrives.
I wonder if there is any support provided in the kernel for this.
Thanks,
mache
reply other threads:[~2003-09-12 15:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F61E83E.402@abcpages.com \
--to=mache@abcpages.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox