From: Krzysztof Halasa <khc@pm.waw.pl>
To: "Eble, Dan" <DanE@aiinet.com>
Cc: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: Re: serial port-to-netdevice tap
Date: Wed, 16 Jun 2004 13:55:32 +0200 [thread overview]
Message-ID: <m3hdtbn2dn.fsf@defiant.pm.waw.pl> (raw)
In-Reply-To: <C060DFCD9697A842B3189B458524FDC205D2C9@AIMAIL1.ai.aiinet.com> (Dan Eble's message of "Tue, 15 Jun 2004 11:50:01 -0400")
"Eble, Dan" <DanE@aiinet.com> writes:
> A coworker of mine wants an easy way to monitor data transfer and control
> line changes on an serial port. His first impulse was to create a /proc
> file, but I suggested a netlink socket, or even a raw net device so that he
> can take advantage of libpcap for some pretty powerful filtering. Does
> anything like this exist already?
With character device? I don't think so. One could use a pseudo
terminal combo, though. Another option is to use two additional ports
with their RX lines connected to both TX and RX lines of the main
port. Depends on requirements.
I use a "data acquisition" card with all the async serial protocol
etc. analysis in (quite simple) software.
A "strace" (if you want to see what a process does) could be a help as
well.
--
Krzysztof Halasa, B*FH
prev parent reply other threads:[~2004-06-16 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-15 15:50 serial port-to-netdevice tap Eble, Dan
2004-06-16 11:55 ` Krzysztof Halasa [this message]
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=m3hdtbn2dn.fsf@defiant.pm.waw.pl \
--to=khc@pm.waw.pl \
--cc=DanE@aiinet.com \
--cc=netdev@oss.sgi.com \
/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).