From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <00b301c428f1$1ec6f040$48db7d50@SOMA> From: "boyd, rounin" To: <9fans@cse.psu.edu> References: <003501c428e5$39cdffc0$48db7d50@SOMA> <007501c428e8$1b974a40$48db7d50@SOMA> Subject: Re: [9fans] telnet MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Date: Fri, 23 Apr 2004 07:09:13 +0200 Topicbox-Message-UUID: 6913ab5c-eacd-11e9-9e20-41e7f4b1d025 > there might be more than one tcp. right now it > works great to run telnet /net.alt/tcp!outside-machine. all the world is not 11271. /net or /net.alt should be irrelevant. the routing should just work. it does on lunix and the last time i was in the unix room binding /net.alt it just worked too. > why does it need to be tcp? it doesn't. > it just shuttles bytes around if it's not connecting to a telnet port, > so telnet il!emelie!9fs works fine. il died years ago. it should be transparent, and as i've said before the CODE bound it to 'net' 'tcp'. it should also allow the flexibility to choose how you want to connect. but these are all moot points. telnet talks tcp, for almost all cases. the code in netmkaddr() and telnet play games, which should not be played.