🚀 go-pugleaf

In article <bwrmtp.8z9@wang.com> fitz@wang.com (Tom Fitzgerald) writes:
>> Dermot.Bradley@bbs.oit.unc.edu (Dermot Bradley) writes:
>> >I'm looking for somewhere that would provide UUCP access to Usenet.  What
>> >I need is somewhere that I can Telnet into ONLY USING THE DEFAULT PORT -
>> >i.e. I can't specify a port number!!.
>
>gtoal@ibmpcug.co.uk (Graham Toal) writes:
>
>> Any machine that offers a uucp connection will do it on the standard
>> port - uucp logins are just normal logins.
>
>This may be true in some cases, but not in general.  "Normal" telnet runs
>on port 23, and talks "telnet protocol" which is more than just the stuff
>you type and read.  It includes DO/DON'T/WILL/WON'T messages between the
>telnet client and server about all sorts of terminal capabilities and
>modes.
>
>UUCP connections generally come into port 540.  If you telnet to this port
>by hand, youll get a session that looks exactly like a telnet connection,
>but doesn't include all the hidden protocol stuff.
>
>Mr Bradley seems to be looking for a server on port 23 that doesn't try to
>use any real telnet protocol messages; and I don't know of such a thing.
>
>-- 

I've implemented UUCP over TELNET down here.  The reason I did it was that
I have a serial connection to a terminal server.  The terminal server does
a TELNET connection on my behalf.  So in your UUCP "chat script" you have
to add the add'l commands to the terminal server that instruct it to connect to
the appropriate node, then you have to have the std. login and password
part of the chat script.

The other tricky thing is that TELNET sessions are NOT 8-bit clear paths, like
what UUCP's 'g' protocol expects.  I had to specify to use UUCP's 'e' protocol,
which expects a 7-bit path.  The 'e' protocol does little or no error-checking, 
I think.  This wasn't a problem for me, since I was directly connected to the 
terminal server's port.  Your mileage may vary.

So you're BOTH right :-)


-- 
Spike White     Tybrin Corporation, Shalimar, FL   | Moderation in all things --
spike.white@tybrin.com                             | and abstinence in none! 
Disclaimer:  The guys down the hall disagree with everything I say! Guess 
	     who speaks for the company.