linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-c-programming@vger.kernel.org
Subject: Re: tcpdump equivalent for the serial port
Date: Fri, 12 Sep 2003 16:05:42 +0200	[thread overview]
Message-ID: <20030912140542.GP14376@lug-owl.de> (raw)
In-Reply-To: <3F61CC14.20607@abcpages.com>

[-- Attachment #1: Type: text/plain, Size: 1562 bytes --]

On Fri, 2003-09-12 15:37:24 +0200, Nicolae Mihalache <mache@abcpages.com>
wrote in message <3F61CC14.20607@abcpages.com>:
> 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.

Your approach won't work, but I can hint you to another. If you don't
need the *wire states*, but only the data your application receives (or
transmits), then this is easy. Simply use strace or a preload lib to
intercept open, close, read and write.

That way, you don't monitor the serial port itself, but the application
using it. For me, that has always been enough:-)

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
      ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-09-12 14:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-12 13:37 tcpdump equivalent for the serial port Nicolae Mihalache
2003-09-12 13:50 ` Mariano Moreyra
2003-09-12 14:01   ` Nicolae Mihalache
2003-09-12 14:08     ` Mariano Moreyra
2003-09-12 14:05 ` Jan-Benedict Glaw [this message]
2003-09-12 14:23   ` Nicolae Mihalache
2003-09-12 14:39     ` Jan-Benedict Glaw
2003-09-12 15:33       ` Nicolae Mihalache
2003-09-12 14:34 ` Jamie Le Tual

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=20030912140542.GP14376@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=linux-c-programming@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;
as well as URLs for NNTP newsgroup(s).