Mark@HAMSTER.BUSINESS.UWO.CA (Mark Bramwell VE3PZR) (01/12/90)
============================================================================== One addition I would like to see is the ability to have a signon file transmitted when someone TELNETed or FTPed into NOS. For example, I get alot of people TELNETing into an XT that I have here. It would be nice, if a text file was then displayed at their screen giving instructions on how to disconnect, and FTP into HAMSTER. The file doesn't have to be different for TELNET and FTP but it would be nice. Thanks phil. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Mark Bramwell, VE3PZR Located in sunny London, Ontario Internet: mbramwel@uwo.ca IP Address: 129.100.22.100 Packet: VE3PZR @ VE3GYQ UWO Phone: (519) 661-3714
karn@jupiter..bellcore.com (Phil R. Karn) (01/13/90)
In article <1457@HAMSTER.business.uwo.ca> Mark@hamster.business.uwo.ca writes: >One addition I would like to see is the ability to have a signon file >transmitted when someone TELNETed or FTPed into NOS. For example, I get >alot of people TELNETing into an XT that I have here. It would be nice, >if a text file was then displayed at their screen giving instructions on >how to disconnect, and FTP into HAMSTER. The file doesn't have to be >different for TELNET and FTP but it would be nice. Actually, several people have made a strong case that what I call a telnet "server" shouldn't be called that at all, and it shouldn't listen on port 23. I'm thinking of moving it to the "ttylink" port (TCP port 87) so it won't keep confusing people who telnet into PCs expecting login prompts. Those who really DO want to talk interactively can always specify the port number in their telnet commands. Phil