netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: netfilter-devel@lists.netfilter.org,
	Sirine Chaitou <schit_2007@yahoo.fr>
Subject: Re: Reading traffic from a serial port
Date: Thu, 06 Sep 2007 13:31:10 +0200	[thread overview]
Message-ID: <46DFE4FE.9090705@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0709061321120.25942@fbirervta.pbzchgretzou.qr>

Jan Engelhardt wrote:
> On Sep 5 2007 17:30, Sirine Chaitou wrote:
> 
>>Hello,
>>I need to see a traffic flowing between two nodes over
>>a serial port /dev/ttyS0. The log files show me that
>>the traffic exchange is going on and is ok, but I
>>cannot see this traffic using ethereal for example.
>>Can anybody tell me about a tool to use for that
>>purpose?
> 
> 
> Are you running SLIP or not?


Completely off-topic for this list.

      reply	other threads:[~2007-09-06 11:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-05 15:30 Reading traffic from a serial port Sirine Chaitou
2007-09-06 11:21 ` Jan Engelhardt
2007-09-06 11:31   ` Patrick McHardy [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=46DFE4FE.9090705@trash.net \
    --to=kaber@trash.net \
    --cc=jengelh@computergmbh.de \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=schit_2007@yahoo.fr \
    /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).