From: Jamie Le Tual <jletual@kmtechnologies.com>
To: linux-c-programming@vger.kernel.org
Subject: Re: tcpdump equivalent for the serial port
Date: Fri, 12 Sep 2003 10:34:34 -0400 [thread overview]
Message-ID: <3F61D97A.7020202@kmtechnologies.com> (raw)
In-Reply-To: <3F61CC14.20607@abcpages.com>
I would probably try to see if I could alter the kernel serial port
driver, there may even be an API in the driver for what you want.
That's where I would start.
Peace,
Jamie
Nicolae Mihalache wrote:
> 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
>
> .
>
next prev parent reply other threads:[~2003-09-12 14:34 UTC|newest]
Thread overview: 10+ 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
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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-12 15:37 Nicolae Mihalache
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=3F61D97A.7020202@kmtechnologies.com \
--to=jletual@kmtechnologies.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.