Xref: utzoo comp.protocols.tcp-ip:11964 comp.dcom.lans:5299
Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!emory!att!watmath!watserv1!broehl
From: broehl@watserv1.waterloo.edu (Bernie Roehl)
Newsgroups: comp.protocols.tcp-ip,comp.dcom.lans
Subject: Re: X.25 terminal/port servers out there?
Message-ID: <1990Jun27.195629.25792@watserv1.waterloo.edu>
Date: 27 Jun 90 19:56:29 GMT
References: <4355.26879a8d@vax5.cit.cornell.edu>
Distribution: comp
Organization: University of Waterloo
Lines: 27

In article <4355.26879a8d@vax5.cit.cornell.edu> jeh@vax5.cit.cornell.edu writes:
>What I'm really looking for is the X.25 equivalent of an Annex 
>box that has an Ethernet port on one side and the appropriate 
>synchronous serial port on the other

Hmm.  Don't know if this will work, but there are HDLC cards for PCs...
could you do it with a PC, an ethernet card, an HDLC card and NOS?
You'd have to hack the code a bit, but the low-level stuff and the LAPB
stuff is already there.  (Don't know whether it handles X.25, or if it's
hardcoded for AX.25 only).  You could then write an application (using
Phil's socket routines) that provides a Telnet-to-outbound X.25 capability.
It would listen on the standard Telnet port, and when it gets a call it
opens an X.25 connection.

Dial-in would be similar; incoming sessions would act like telnet clients.

(Hmm... this might actually be useful around here, too).

If Phil is listening, he could probably tell you (us) whether it'll work or
not.  I'm not at all bothered by writing the upper layers myself, but digging
into the guts of LAPB might be a lot of work.

-- 
	Bernie Roehl, University of Waterloo Electrical Engineering Dept
	Mail: broehl@watserv1.waterloo.edu OR broehl@watserv1.UWaterloo.ca
	BangPath: {allegra,decvax,utzoo,clyde}!watmath!watserv1!broehl
	Voice:  (519) 747-5056 [home]  (519) 885-1211 x 2607 [work]