LAN Creating Tutorial v1.0 by _GPT_ for General Release This tutorial is Copyright © Joe Elleson 2002 No part of this document may be duplicated or altered without my prior consent. (Except for downloading it to your computer of course) If you have any questions please e-mail webmaster@groovypigthing.com - I will try to answer all your queries. --- LANs are created by making a text file, and putting it in the directory \data\lans in your uplink directory. The LAN file takes the following format: --- NAME Name of LAN goes here COMPANY Name of company goes here IP the IP for your LAN (xxx.xxx.xxx.xxx) XPOS The X position for the system on the world map YPOS The Y position for the system on the world map ; NUM SYSTEMTYPE XPOS YPOS SECUR DATA1 DATA2 DATA3 DATAX ; --------------------------------------------------------------------------- ; systems go here. . ; LINK FROM FROMX FROMY TO TOX TOY SECUR ; ------------------------------------------------------- ; links go here . ; VALIDSUBNET FOR FROM ; -------------------------- ; valid subnets go here . ; DATA NUM TEXT ; ------------------ ; data for terminals goes here. . --- The NAME, COMPANY, XPOS and YPOS should be self explanatory. --- SYSTEMS The systems are the largest part of this tutorial. To declare a system you use a line as follows: NUM SYSTEMTYPE XPOS YPOS SECUR DATA1 DATA2 DATA3 DATAX NUM is the number for the system, starting at 0, and ascending for each new system. SYSTEMTYPE is the type of system, and can be any of the following: ROUTER - A Router. This is where you connect to when you connect to the LAN. Only one of these can exist on a LAN, and you should include it on your system as system 0. HUB - A Hub. This simply acts as an intermediate system between two other systems, or a way to connect one system to more than one system. TERMINAL - A Terminal. This is a computer on the LAN. You cannot do anything to it except gain access to it by hacking it, but it can contain information. MAINSERVER - The Main Server. This is the main system of the LAN and if it is shut down then so is the whole LAN. It contains a file server, a log server and a console. FILESERVER - A File Server, which stores files. LOGSERVER - A Log Server, which stores logs. AUTHENTICATION - An Authentication Server. This lock and unlocks a lock on the LAN. ISOLATIONBRIDGE - An Isolation Bridge. Probably the most complicated system to work with. It operates 2 locks, and is used to Lock one of them, and unlock the other, and hence Isolate part of the LAN. LOCK - A Lock, which, if locked, cannot be passed through without unlocking it with an authentication server, or using LAN Force on it. RADIOTRANSMITTER - A Radio Transmitter. Connects to any Radio receiver on the LAN, given the right frequency. RADIORECEIVER - A Radio Receiver. Receives a connection from a radio transmitter. MODEM - A Modem. Can be accessed from your gateway with the right phone number, and can be used to gain access to the LAN 'further in' than the router. XPOS and YPOS are the possition of the system in the LAN. SECUR is the level of security for the systems and can be set to 1, 2 or 3. Use 3 for the most secure systems. For each system, 4 sets of data can be specified. Data1, Data2, Data3 and DataX. If either of Data 1, 2 or 3 is not required for a system, they should be set to -1. DataX should be left blank unless required. To refer one of the Data's to another system, the number of the system is used. --- Now I will describe which data is required for each system. Isolation Bridges ISOLATIONBRIDGE Data1: Should be specified to be a lock on the LAN. The Isolation bridge will lock it when you enable the Isolation Bridge. You should set this lock to be unlocked originally. Data2: Should be specified to be a lock on the LAN. The Isolation Bridge will unlock it when you enable the Isolation Bridge. You should set this lock to be locked originally. Authentication Servers AUTHENTICATION Data1: This should be specified to be a lock on the LAN. The Authentication Server will lock and unlock this lock. Locks LOCK Data1: If set to 0, the lock will start off unlocked. If set to 1, the lock will start off locked. Main Servers MAINSERVER Data1, Data2 and Data3: These are optional, but if used, should be specified to be a lock on the LAN. The Main Server will be "GuardedBy" these locks, and you will not be able to access the main server until they are unlocked. 1, 2 or 3 locks may be specified. Note: There should only be 1 main server on a LAN. Radio Transmitters RADIOTRANSMITTER No additional data is required. It will connect to any Receiver on the LAN, given the right frequency. Radio Receiver RADIORECEIVER Data1: The Frequency required to connect in Ghz (between 140 and 180, inclusive). Data2: The frequency required to connect in Mhz (between 0 and 9). For example, if Data1 is 154, and Data2 is 5, then the frequency for the system would be 154.5 Any Transmitter on the LAN will be able to connect to them. Note: All Receivers should have different frequencies. This makes a maximum of 410 (I think...) receivers on one LAN. Terminals TERMINAL No additional data is required. 'Data' to be contained on the Terminal should be specified in the Data section and the end of the text file. Hubs HUB No additional data is required. Routers ROUTER No additional data is required. Modems MODEM DataX: This should be set to the modem's phone number. For example 01234-123456. This is the standard format of telephone number, although I don't see why phone numbers of different length shouldn't be used. Note: Spaces are not allowed in phone numbers, use a hyphen instead. Log Server LOGSERVER I don't think any data is needed. Any locks specified in Data 1, 2 and 3 *may* guard the Log Server, but I haven't ever tried. Confirmation of this would be nice. Please feel free to e-mail me of you try this) File Server FILESERVER I don't think any data is needed. Any locks specified in Data 1, 2 and 3 *may* guard the File Server, but I haven't ever tried. Confirmation of this would be nice. Please feel free to e-mail me of you try this) An example of a declaration of a system would be as follows: 0 ROUTER 500 500 3 -1 -1 -1 --- LINKS Links are used to connect systems together. The format for declaring a link is as follows: LINK FROM FROMX FROMY TO TOX TOY SECUR LINK just specifies a link. It does not matter which order links are specified in, so LINK should just be set to LINK. FROM is the number of the system the link is from. FROMX and FROMY are used to denote where on the image of the system the link should connect to. 0, 0 is at the top left of the image, and 1, 1 is the bottom right. TO is the number of the system the link is to. TOX and TOY are used to denote where on the image of the system the link should connect to. 0, 0 is at the top left of the image, and 1, 1 is the bottom right. SECUR is how secure the links are. This can be set to 1, 2 or 3. For the most secure systems, 3 should be specified. An example of a link declaration is as follows: LINK 0 1.0 0.5 1 0.0 0.5 3 --- VALID SUBNETS A valid subnet is used to allow only one system to connect to another system. For instance, it could be used to specify that only one specific temrinal may connect to a certain authentication server. The format of a line decalring a valid subnet is as follows: VALIDSUBNET FOR FROM As with links, the order doesn't matter, so VALIDSUBNET should be set to VALIDSUBNET. FOR should be the number of the system which is being protected. FROM should be the number of the system which is allowed to access the system specified to be protected. An example of a declaration of a valid subnet is as follows: VALIDSUBNET 10 9 --- DATA This is the data stored on a terminal. The format is as follows: DATA NUM TEXT As with links and valid subnets, DATA should just be set to DATA. NUM is the number of the terminal which you want the data to be on. TEXT is the text you want on the terminal. It can only have a length of something like 220 characters, although that number isnt exact. I don't know if there are any characters which you may not use. An example of a line declaring data would be as follows: DATA 5 Hello. Please visit www.groovypigthing.com --- Note the . at the end of each section. This marks the end of the section when it is compiled into the user file, and should not be removed, or the game will slow to a halt when you try to create a new user. Also note the use of ; at the beginning of lines. A semicolon at the start of a line denotes a comment in the text file, so everything after it will be ignored when it is 'compiled'. --- To incorporate you LAN into the game, you must simply put it in \data\lans in your uplink directory. The text file may be called anything. When you create a new user, the lan will be available to conenct to. Also, a company in the name that you specified will be created, with an Internal Services Machine, Central Mainframe, (another) LAN, and a Public Access Server. Your LAN will be available to find at InterNIC, and the voice required to access the main server will be on the public access server of the company you created. --- That's it! I hope this has been useful and if you have any questions, comments or suggestions please do not hesitate to contact me at webmaster@groovypigthing.com ---