=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= = P/HUN Issue #3, Volume 2: Phile #9 of 11 = =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= An introduction to BITNET ------------------------- By Aristotle Jan 17, 1989 About BITNET: Because It's Time NET (BITNET) is the largest of the acedemic computer networks and one of the largest mainframe networks. BITNET connects hundreds of thousands of students and professors in Asia, Europe, Middle East, and North America. In 1988, BITNET had nearly 2000 computer systems at higher institutions connected to it. BITNET may not allow you to log onto mainframes, BUT it IS an invaluable source of information. While on BITNET, you can access certain services such as chat relays, file servers, electronic mail service, and info servers. (See below for more info) A little semi-technical info: The mainframes on BITNET are connected via constantly operating telephone lines or satellite links. Unlike packet-switching networks (ie. Telenet), BITNET is a store and forward network. That means that if you send a message from Florida to Kentucky, the computers in the network between Florida and Kentucky will store and forward it from each computer to computer until it reaches Kentucky. In BITNET there's only one path from Kentucky to Florida. Each computer is called a NODE. Below is an illustration of how a small section of the network would look like. A----B----C | | | D----E----F----G | | | H I----J ---K Example A. A message traveling from A to H would travel the following path: A-D-H Example B. A message traveling from A to F could travel one of two ways. These are: A-B-C-F or A-D-E-F Sometimes when a node is down, the message may be delayed or routed through different nodes as in example B. The time to transfer messages can vary from just a few seconds to an hour. This cause for this is usually one (or both) of two reasons. The first factor is the size of the message. Larger amounts of data take longer times to transmit. The second factor is the status of the network. As we all know, computers are prone to breaking down. Messages that cannot be routed past the downed node are stored in the net until there is a clear path to it's destination. Addresses: Each of the mainframes(NODE) on BITNET has it's own individual address. The addresses are usually an abbreviation of the name of the institution that supports the mainframe. One example is the University of Massachusettes "UMASS". The indiviuals that have access to BITNET also have their own addresses. These addresses are assigned to the user when he/she first sends information over BITNET. The entire address for a user is set up as follows: University of Kentucky Prime--+ | @ (AT)----------------------+ | | | User ID-------------------+ | | | | | | | | | | | | | | | | | $108@UKPR Note: Not all addresses give indication of the type of system. Also: On some machines, the BITNET ID will be different from the system ID. Ex. CS.DEPT.SMITH.J@UKPR is also $108@UKPR. Access: It is IMPOSSIBLE to access BITNET unless you can gain access to one of the nodes. That means, there are NO dial-ups that do not go through a mainframe. BITNET is supported by the institutions that have access to it and it is your right as a student to have access. It is NOT your right to access the mainframe though. A good way to gain access to BITNET is to go to your local university and ask or engineer an account for the use of BITNET. Uses: There are three basic methods of communicating via BITNET: mail, message, and file. Each method has it's own advantages and disadvantages. The interactive message (Let's just call it a message) is the fastest and most convenient method of transitting short amounts of information over BITNET. Messages are composed of one line of information that is sent VERY quickly to it's destination. You would use the message when chatting with someone at a different node. The bad part about messages is that if a node is down, your message is lost. You WILL recieve an error message though. Messages are usually sent via the TELL and SEND commands. Below are examples of the syntax for sending a message on the VM/CMS and Prime systems: TELL userid@node message or TELL 151133@DOLUNI1 Hey Terra, How are the guys at CCC doing? Mail: Electronic mail is the most versatile method of communication on BITNET. Unlike the message, a letter will be stored if a node is down. A letter can be from one word of text to however long you want it. It has been suggested to me to NOT transmit any mail over 3000 lines long (hmmm, maybe we should explore that one.) The actual file that is transmitted is really nothing more than a formatted text file with a header. When you send mail from you system, You will be prompted to input a subject so the header can include the sending address, recieving address, date, and subject. A piece of mail would look like this: Date: Fri, 13 Jan 89 18:26:12 EDT From: Terra <151133@DOLUNI1> Subject: Greetings To: $108@UKPR + ============================================================= + Hello Aristotle | | Regarding the information that I have been recieving | directed to a member of the | Chaos Computer Club....... rest of text Files: The file is the best way to send large amounts of information over BITNET. As with mail, files are stored until you read them or in the case of node being down, until they are back up. Any type of file can be sent via a file. They can be either text or binary. On a VM/CMS system, one would use the SHIP command to send a file over BITNET. Below is an example: SHIP filename filetype userid@node or SHIP phun3 txt $108@UKPR I suggest that you check your online help for information on sending info over BITNET. Now for the phun part.... FILE SERVERS, CHAT RELAYS, AND SERVICES: Servers are machines set up as automated databases for the distribution of various information. Servers respond to commands via mail or message. Not all use accept this type of communication. It all depends on the type of software the server is running. One would send a message to a server in the following syntax: TELL userid@node command or Tell listserve@bitnic help File servers are like servers but they are set up as databases that transmit files. They are kinda like BBS's. The best way to get started with a file server is to send it the help command. A good place to start is the Listserv@Bitnic system. It will send you all the information you will need to get started. Name servers have two functions. The first is to locate a person's address on BITNET and the second is to help you find people on BITNET with similar interests. (Hmmm, a hacker directory?) I suggest starting with the name server at Drew University. To find a particular person, just send the following to Drew: TELL NAMESERV@DREW SEARCH/NAME john doe If the person you are looking for is not registered, you will recieve a message informing you of that. To register yourself, send the following to Drew: TELL NAMESERV@DREW REGISTER first last interests or TELL NAMESERV@DREW REGISTER John Doe LMOS hacking A chat relay is set up to allow many users to chat with each other without having everyone sending messages to each other individually. When on a relay, the people on your channel (be it public or private) will all see the messages that you send to them. This is GREAT for phreaker conferences (Though it is NOT secure due to system operators) and just chatting with your friends over LONG distances. Geee and it is all legal too! To find out more about relays, just send the following: TELL RELAY@UTCVM help If your local relay is not UTCVM, you will receive a message tell you that and also your correct relay. Well, that's it for this file. If you have any questions about BITNET, you can contact me at the following boards: Hacker's Den 718-358-9209 The Outlet Private 313-261-6141 Newuser/Kenwood DOWNLOADED FROM P-80 SYSTEMS 304-744-2253 Downloaded From P-80 International Information Systems 304-744-2253 12yrs+