Path: utzoo!utgpu!water!watmath!clyde!att!rutgers!aramis.rutgers.edu!athos.rutgers.edu!hedrick From: hedrick@athos.rutgers.edu (Charles Hedrick) Newsgroups: comp.protocols.tcp-ip Subject: Re: Specification of Berkeley networking utilities Message-ID: Date: 27 Oct 88 00:20:34 GMT References: <845@acer.stl.stc.co.uk> <1988Oct24.200243.19459@utzoo.uucp> <211@cwjcc.CWRU.Edu> <4896@b-tech.ann-arbor.mi.us> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 18 >Don't forget the transparency. Full 8 bit file transfers (like uucp 'g') >don't work over telnet). We do UUCP and xmodem over telnet all the time. Rutgers.edu is a major UUCP hub. All of its dialup UUCP transactions are done through TCP/IP terminal servers. (For reasons of efficiency on the host, we are experimenting with having the terminal server go through a raw TCP connection directly into uucpd. However most connections still go through telnet.) For complete transparency, we require the user to type "term download" on the terminal server. This disables the sequence that would otherwise get you back into command mode on the terminal server (like ~ in rlogin), and makes a set of protocol choices that provide an 8 bit transparent path with most of our server telnet implementations. You could do this by using telnet binary mode. However since binary mode doesn't always seem to work on Unix telnet, we do it in normal mode simply by making sure that we choose an end of line representation that is consistent with the one used by the Unix server telnet.