Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!rpi!uupsi!ncs.dnd.ca!jstewart
From: jstewart@ncs.dnd.ca (John Stewart)
Newsgroups: comp.dcom.lans
Subject: Re: X.25 Analyzer
Keywords: X.25 TCP/IP protocol analyzer
Message-ID: <1990Nov26.134035.25297@ncs.dnd.ca>
Date: 26 Nov 90 13:40:35 GMT
References: <3660@peyote.cactus.org>
Organization: Dept of National Defence
Lines: 19

In article <3660@peyote.cactus.org> cravey@peyote.cactus.org (Mark Cravey) writes:
>Has anyone had experience with an X.25 analyzer?  I have a card
>running TCP/IP on top of X.25.  At the mechanical/physical level, it is
>RS-449/422.  Does anyone else have a similar configuration?  What do
>you use to analyze these protocols?

Our long-haul network links use X.25 instead of leased lines. When we
need an analyzer, we use our fairly trusty Idacom serial analyzer.
This gives us a decode of the X.25 packets, but of course does not
decode the IP data.

I have seen some advertised that are small and cheap. ($$ wise).
AIM Electronics in Canada had one that looked pocketable.

Most of the TCP/IP over X.25 products that I have seen have some form 
of monitor for seeing the X.25 packet headers for call setup and clear.

John Stewart
jstewart@ncs.dnd.ca