linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mariano Moreyra" <moremari@aca.org.ar>
To: 'Nicolae Mihalache' <mache@abcpages.com>,
	linux-c-programming@vger.kernel.org
Subject: RE: tcpdump equivalent for the serial port
Date: Fri, 12 Sep 2003 10:50:43 -0300	[thread overview]
Message-ID: <000101c37934$dcd34740$0b04a8c0@aca.org.ar> (raw)
In-Reply-To: <3F61CC14.20607@abcpages.com>

Hi Nicolae,
I think that what you want to do is not posible just with a software.
You have to build a special cable to do that (somebody tell me if I'm wrong,
or if knows another option)
In my job we have one of those cables because we needed to see what was
going on between two applications that talk to each other via serial port.
The bad thing is that you need a third computer that would be the sniffer.


-----Mensaje original-----
De: linux-c-programming-owner@vger.kernel.org
[mailto:linux-c-programming-owner@vger.kernel.org]En nombre de Nicolae
Mihalache
Enviado el: Viernes, 12 de Septiembre de 2003 10:37
Para: linux-c-programming@vger.kernel.org
Asunto: tcpdump equivalent for the serial port


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.

Thanks,
mache

-
To unsubscribe from this list: send the line "unsubscribe
linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2003-09-12 13:50 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 [this message]
2003-09-12 14:01   ` Nicolae Mihalache
2003-09-12 14:08     ` Mariano Moreyra
2003-09-12 14:05 ` Jan-Benedict Glaw
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='000101c37934$dcd34740$0b04a8c0@aca.org.ar' \
    --to=moremari@aca.org.ar \
    --cc=linux-c-programming@vger.kernel.org \
    --cc=mache@abcpages.com \
    --cc=mariano_moreyra@aca.org.ar \
    /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).