Ozzie Kill trying to use the manual .doc or .pdf files previously sent. All four of the texts were in one file. Attached are the separate files used to put that manual together For FlexNet User Commands summary use H.FPR (that is the on line User help file) For FlexNet User Commands Detail use FLXUSRC.TXT (that is an extract from the main Flexnet manual) For F6FBB User Commands use BBS_CMDS.TXT For MULTI Usage use MULTI_US,TXT Also attached For Hierarchial Addressing use HADDRESS.INF For NTS Addressing Use NTSZIPS 73 Bob, K2BJG -----Inline Attachment Follows----- 5 BBS COMMANDS: --------------- BBS COMMANDS. Here is an overview of what the BBS-commands do: ; : A command-line starting with a ; is ignored. Nothing happens, and there is no prompt back.. ? : Reading the help file. Type ?[COMMAND] to obtain help on a basic command. > : "Break" between channels. Type > [CALLSIGN] [TEXT] to send a text to a connected callsign on another channel. The BBS will advice you that the text has been delivered. This text cannot be longer than one line. This command is not allowed in read-only mode. = : Connection between two channels. Type = [CALLSIGN] to get connected to a callsign on another channel. The callsign can be connected only if it is not busy in a command; the BBS should be idle (waiting for a command). If the callsign is not available, you may either wait or you may cancel your request. The callsign currently busy in forwarding tasks cannot be connected. Use Ctrl-Z to leave this mode. This command is not allowed in read-only mode. ! : Provide a short and minimal information on the BBS usage. % : Use this command to see the status of all channels right now. A : Abort the BBS output at any time. When reading messages with paging, the commands N and C are available, too. Use N to skip the reading of the rest of current message, and start on the next message. Use C to read the rest of the message(s) without paging. B or Bye : Disconnects the BBS. Note that the "last listed" parametre is updated. When the user does a "hard disconnect", the last-listed parametre is NOT updated. C : Enters the conference mode, multiconnection. CW: Shows a list of the callsigns involved in the current conference. D : Invokes the FBBDOS, or receives a file from the BBS if the command is followed by a file name. F : Switches to Server mode, and access to special commands. G : Accesses the Gateway mode, if gateway is allowed in the BBS. H : Shows short help. For help with specific commands, see the ? command. I : Information about this BBS. This command displays the file FRANCAIS.INF (or another language depending upon the configuration and the language attributed to the involved channel). I callsign : Gives the information on callsign taken from the white pages database. Callsign can include wildcards. ID : Shows how many records there are in the WP database. I@ bbs : Gives the users of BBS found in the WP database. IH route : Gives the users of the hierarchical route area from WP database (wildcards allowed). IN string : Gives the WP-records including "string" in the name from the WP database. IQ string : Gives the WP-records including "string" in the QTH from the WP database. IZ Zip : Gives the users of the ZIP code area from WP database (wildcards are allowed). J-commands list the callsigns heard by or connected on the BBS. JK : Shows the last 20 connected callsigns. JA : Connected callsigns on port A. JB : Connected callsigns on port B, etc... J1 : Heard callsigns on port A. J2 : Heard callsigns on port B, etc... K-commands delete messages sent by you or to you. K msg# : Deletes a message identified by its number. KM : Deletes all the messages addressed to you, that you don't yet read. The messages not read will not be deleted. L : Lists the new messages since the last usage of this command. LA : List messages with status A. LB : Lists bulletins. LC [mask] : List the messages which "TO" filed matches with mask. * (star) allows to list all the messages and should be the default value. Type "LC *" to see all messages. LC alone gives the current mask. Mask is recorded for each user while disconnecting. LD> YYMMDD : Lists the messages received after the specified date. LD< YYMMDD : Lists the messages received before the specified date. LE : List messages that could not be forwarded. LF : List FORWARDED messages. LH : List HELD messages. LK : List KILLED messages. LM : Lists the messages TO YOU. LN : Lists the NEW messages TO YOU. LP : List PRIVATE messages. LU : Lists all unread messages to/from the user. LX : List messages with status X. LY : List messages that have been read (status Y). LL 10: Lists the last 10 messages. LR : Equivalent to L but the messages are listed in reverse order. LS text : Searches for a text in the messages titles. Usage of wildcards is allowed. LT : List Traffic (for NTS-messages). L$ : List bulletins with status $. L< Callsign : Lists the message originated from [Callsign]. The wildcards are allowed. L> Callsign : Lists the messages destinated to [Callsign]. Wildcards are allowed. L@ [BBS] : Lists the messages VIA BBS if specified. L@ alone lists the message without route. The wildcards are allowed. L msg#- : Lists all messages, starting from msg# L msg#-msg# : Lists messages between the given numbers. M msg# File : Transfers the text of the message msg# to the file File. This file will be placed in the directory USERS or from the root in case of a SYSOP user. MH msg# File : Identical, but the format is the R command. MV msg# File : Identical, but the format is the V command. MA msg# File : Transfers the text of the message msg# to the file File. This file will be placed in the directory USERS or from the root in case of a SYSOP user. The message is appended to the existing file. MHA msg# File : Identical, but the format is the R command. The message is appended to the file. MVA msg# File : Identical, but the format is the V command. The message is appended to the file. N : Enters or modifies the name (max 12 characters allowed). NH : Enters or modifies the Home BBS. A point deletes the current Home BBS. NL : Enters or modifies the QRA locator. NP : Modifies the password for the access via telephone modem. NQ : Enters or modifies the city (Qth). NZ : Enters or modifies the Zip Code. O : Displays the setting of various options. OL : Lists the available languages. OL number : Selects a language. ON : Shows the number-base for messages. See also ON number below. ON number : Defines the number of the thousand base for the messages. Example: ON 37 defines number 37000 as being the base for numbering the messages. Then the command R 25 will cause the message 37025 to be read, although R 36025 will actually read the message nr 36025. OP : Validates or disables the scrolling of pages. OP nbr of lines : Initializes the page scrolling OR : Validates or disables the ability to list all messages, if the user has access to the whole list of messages by default (See security code 256 of INIT.SRV). PG [program]: PG alone gives the list of PG programs available in the BBS. If followed by a program name gives the control to this program. The PG program can also be called by its name. If the name is the same that an existing command, the existing command will be replaced with the PG program. PS : Gives the list of servers available in the BBS. R-commands are for reading messages. Note: When reading messages with paging, the commands N and C are available, too. Use N to skip the reading of the rest of current message, and start on the next message. Use C to read the rest of the message(s) without paging. R msg# msg# : Reads the messages by their numbers. RM : Reads all the messages to you. RN : Reads all the NEW messages to you. RU : Read all unread messages to/from you. R> callsign : Read all messages to a callsign. R< callsign : Read all messages from a callsign. S[type] callsign : Sends a message or a bulletin. If the type is not specified, it will be processed as a private, provided the destination callsign is a valid one, otherwise it will be considered as a bulletin. SP callsign : Sends a private message. S callsign @ BBSCALLSIGN : Sends a message to a station AT another BBS through forward. BBSCALLSIGN can be an address of hierarchical type, for example F6FBB.FRA.EU. Type "SB ALL" to send a bulletin addressed to ALL. The message must be terminated by a Ctl Z or /EX followed by a return. Warning: the /EX must be in the first column. SC Msg# Callsign @ BBSCALLSIGN : Copies a message or bulletin to the specified callsign. Such a copy will always be of the "personal" type. When relying to a CP SYSOP message, the title is changed back to the original. SR [Msg# [title]] : Replies to a message already read or formerly suppressed, or to a message matching the specified number. If the title is not stated, it will be the title of the read message, with the mention "Re:" placed ahead. T : Pages the SysOp. Should the SysOp not be available within a minute, you will be advised accordingly and automatically returned to the normal BBS menu. TH : Gives access to the themes-zone. Lists messages by themes, as setup in the file THEMES.SYS. Available commands in this zone, are H (list themes) L (list messages in current theme) R msg# (read message in current theme) number (change to theme#) U : Uploads a file from the user to the server of the BBS. The file will be written in the root directory of the FBBDOS. The U command is to be typed at the BBS prompt, it is not necessary to go to FBBDOS first. V : Version number of this BBS software. It gives also the number of active messages, and the next message number. V msg# msg# : Reads the messages by their numbers, including the headers. VM : Reads all the messages TO you, including the headers. VN : Reads all the NEW messages TO you, including the headers. W : Lists the files which are within the user directory. This command can be followed by a mask specifying search criteria or a directory name; in the latter case, the directory contents will be listed. X : Toggles "normal" or "expert" status. "Normal" grants the extended menus, "expert" provides only minimal information. Y : Binary transfer program using the YAPP protocol. As a user, you should also have the YAPP protocol available your end, in order to be able to transfer binary data. YD File : Downloads a file FROM the BBS TO you. YI [mask] : Lists the available binary files, and their description. YN [mask] : Lists the NEW binary files since your last connection. YU File : Uploads a binary file from you TO the BBS. You cannot replace or modify an already existing file. YW [mask] : Lists the available binary files. YZ Filename : Deletes the specified filename in the YAPP directory. Z Filename : Deletes the specified filename in the user directory. -----Inline Attachment Follows----- Note: This file is an extract fron the Flexnet Sysop Manual. 4.1. User Commands ------------------ User commands are all the commands normal users can access. The sysop has a set of additional commands or may specify additional parameters to normal user commands. In this documentation, means entering of a Carriage Return, $0D. The "=>" is the system prompt of FlexNet;input is expected now. All input can be made either upper or lower case.Is another command entered than those listed below, the node answers with: "invalid command". 4.1.1. Ltest News -------------------- Syntax: A The A-Command shows the text for latest news as set by the sysop. After a cold reboot this text is empty. 4.1.2. eacon --------------- Syntax: B The B-Command shows the current beacon file. In this file you can see which beacon is sent on which port in which interval. After a cold reboot the default beacon is sent on port 0 or 1. 4.1.3. onvers mode --------------------- Syntax: C If no callsign is given, the CONNECT command puts you in convers mode. By this mode, a great number of stations can have a round table conversation There are 255 different convers channels available. After entering the C-Command, you get a list of all stations connected to the node and, if they are in convers mode, too, the channel on which they are. Now the node prompts for a number, which selects the channel you want to join. Example: =>C users: 0: DL1AA 0:DL1ZZ ---: DL2XY 73: DG3FBL 73: DK7WJ channel ? 73 *** starting convers, exit: /q In this example, DL1AA and DL1ZZ are on channel no. 0 and DG3FBL and DK7WJ on channel 73. DL2XY is connected to the node without being in convers mode. Having given the desired number 73, the conversation starts. All stations logged in onto the chosen channel get the message: " : *** Logon" While being in convers mode you have the following commands at your disposal: "/w" shows all stations connected to the node (with convers channel number if available) "/c" shows the actual channel number "/c n" switches to channel n "/s " sends private msg to only "/m " sends private msg to only "/q" quits convers mode If a station disconnects while being in convers mode or quits convers mode, all other users of the channel get the message: ": *** Logoff". If a user changes to another channel, the users of the left channel get the message: ": *** switched to channel n" If there is no channel number entered on convers start-up, convers mode is ended immediately. You are then prompted for a new command. 4.1.4. onnect ---------------- Syntax: C Call [via] [digi1 digi2 ... digi8] The CONNECT command is used to connect further onwards. The node will try to connect you to the station via the path you specified. To confirm your command, you get the message "link setup...".As soon as the connection is made, you will get "*** connected to " from the node. When the called station did not respond, you get "*** failure with ". If the called station sends a Busy (DM), the message "*** busy from " is sent to you. The link setup can be interrupted by sending a single to the node. If you see the message "*** can`t connect twice", you have tried to establish a QSO which already exists with the same callsign fields. With the C-Command it is also possible to change the user port, if the node has more than one. By typing "C -7" you change to the port with the SSID 7. This is acknowledged by the message "*** : SSID OK". If you connect to another station from the node onwards, and that station disconnects you, you will get reconnected to the node. To show you what happened, you get a "*** reconnected to " then. A connect request will be denied, if it causes a loop in the network. If, for example, you are connected to DB0KT via DB0ODW, you cannot connect back to DB0ODW nor to other nodes behind DB0ODW. You should quit the QSO with DB0KT then and retry after the reconnect. Example: (user is connected to DB0HP) => C DB0ODW link setup... *** connected to DB0ODW RMNC/FlexNet V3.3d - DB0ODW - JN49 IQ - Help mit H => C DB0HP *** DB0ODW: loop detected => Q 73! *** reconnected to DB0HP => 4.1.5. estinations --------------------- Syntax: D [call] The DESTINATIONS command prints out the destination table maintained by the node. In this table all nodes, where the autorouter knows a way to, are shown. For every callsign there are the SSID range of the callsign and the average round trip time in 100 ms steps are shown. As an optional parameter a destination callsign may be given. The node will now try to work out the way to this node and will show it (after some seconds, depending on the (round-trip time). Uppercase callsigns mean that the node knows the FlexNet protocol, lower case callsigns are inserted by the autorouter to reach the next FlexNet node. The characters "???" mean, that the previous digi does not know the way to the destination. This may happen, when the route to the destination is reorganized at the moment or when the destination is not reachable anymore. The "D-Table" is usually the same on all nodes. Only when round trip times get too high, a node is not shown anymore. Only nodes that you can reach without link loops are shown by default. This reduces link load and has the advantage that you will see only the nodes that are not in your direction. By using the option "*", you will get the complete list. Another possibility is the selective display of a part of the list. By entering "D HB9" for example, you get all destinations starting with "HB9", i.e. the whole Swiss network. Both parameters may be used together. If you type "D * HB9" you will get all Swiss destinations, including these you cannot reach without loops. 4.1.6. ind ------------- Syntax: F call With the FIND command it is possible to look for a station which is standby on this or another node. When the F-Command and the callsign are entered, the digi sends UI-frames with the POLL-bit set to this station via some neighbor nodes. Source callsign is the callsign of the OM who issued the FIND command. If the called station hears the frame, it will answer with a DM- Frame. The node analyses all frames coming back and is able to determine if this was an answer of the FIND command. If this is the case, you will get a message via which node the station was found. If the called station is already connected to the node, no special frame is sent and the user will get the message that the user is QRV on the digi. Example: =>F DK7WJ *** DK7WJ found via DB0ODW => Only the node via which the called station was found is put out. It will be known to the autorouter. If the station was not found, a system prompt "=>" appears again. Since the used UI and DM frames may get lost, it is advisable to use the FIND command more than only once to be sure the user is not QRV. Due to the protocol, the SSID of the called station must be known. 4.1.7. elp ------------- Syntax: H The H-Command prints out the text-file HELP. The text can be entered by the sysop only and should give short help text about using the node. After a cold reboot the text is empty. 4.1.8. nfo ------------- Syntax: I The I-Command prints out the text-file INFO. This text can be entered by the sysop only and should provide information about the node (QTH, equipment, antennas and so on). After a cold reboot the text is empty. 4.1.9. (In/Out) -------------------- Syntax: IO The IO-Command shows the state of the I/O-ports of the RMNC reset card. There are 16 lines in and 16 lines out. The latter may be set only by the sysop. Using this ability it is possible to remote control the node by hardware. There are no limits to the fantasy of the sysop. The data is shown binary. Example: =>IO I: 0000 0000 0000 0000 O: 0000 0000 0000 0000 => The input lines are shown first and then those of the output. 0 means "low", 1 means "high". The meaning of the single bits needs to be documented by the sysop. 4.1.10. inks --------------- Syntax: L The LINKS-Command displays the link table set up by the sysop. Example: =>L DB0KT 0-7 60/68 P1 DB0AAC 0-15 (---) P2 DB0IE 0-1 583 P3 @ DB0EQ 0-8 (355/399) via DB0IE DK7WJ 8-11 44/67 P0 - DB0ABA P4 DB0BBS 0-15 --- P5 In the first column the callsigns of the neighbor nodes are shown. Second column shows the SSID ranges of these stations (default: 0-15). In the third column you read the round trip time to the neighbor in 100 ms - steps. No number here means that the round trip time is not calculated. Three hyphens mean that the link is not available at the moment. Three hyphens within brackets mean that the link is not available but the autorouter is aware of another way to the station. If there is only one number in the column, the link partner does not know about the FlexNet protocol, or the internode QSO could not be established. When the sysop knows that the neighbor does not know the FlexNet protocol, he may set the attribute "@" to the link. Then only the link is tested, not if the partner knows the protocol. If the round trip time is surrounded by brackets, the link is so bad that it is not made known to the network. If there are two numbers, separated by a diagonal stroke, the neighbor is a FlexNet node. In this case the round trip times of both directions are shown. If these values are within brackets, the autorouter knows a better way to the destination, i.e. the direct link is not used. The 4th column shows either the port number of the link to the neighbor (on direct links) or the stations via which the neighbor is reachable. A hyphen behind the port number means that the link is not made known to the network. This may be used for temporary links or software tests for example. 4.1.11. cal --------------- Syntax: LO The LO-Command shows the text-file LOCAL. This text is appended to the CTEXT for local users, but it can be displayed by the LO command separately. The text may only be entered by the sysop. After a cold reboot this text is empty. 4.1.12. ail -------------- Syntax: M The MAIL-Command connects you to the nearest BBS as defined by the sysop. This command therefore works like a "Connect" command with predefined destination. The BBS callsign can be shown with "M ?" (notice the space!) 4.1.13. eard ---------------- Syntax: MH [options] The MHeard-Command by default displays the last 30 direct heard callsigns. Optionally, a port number, a callsign (with or without SSID) or a number (16 ... 200) of entries to be listed, may be given. 4.1.14. call ---------------- Syntax: MY The mycall command gives the callsign and the SSID range of the node. Example: => MY mycall: DB0ODW, SSID's: 0-7 => 4.1.15.

arameters -------------------- Syntax: P The PARAMETERS command puts out a list of the current parameters and some channel statistics. Additionally, the links as shown with the command are displayed. Example: => P po id td qso usr tifr rifr tkby rkby qty mode links 1 -- 10 30 1 365 287 50 33 100 9600d*+ DB0KT 0-10 6/6 2 -- 1 36 1 271 908 30 163 99 19200d*+ DB0GV 0-0 4 3 -- 1 1 1 0 0 0 0 100 9600d*+ DB0GV 6-6 10 4 -- 40 3 1 27 3 2 0 82 1200*+ DB0TCP 0-15 580/647 5 -- 1 50 1 835 377 102 55 100 19200dtr*+ DB0SHI 0-15 11/39 6 -- 1 39 1 582 546 78 42 100 38400d*+ DB0GV 10-12 1/1 7 -- 40 4 1 31 3 2 0 70 1200*+ DB0ASF 0-15 229/243 8 7 40 8 8 184 36 34 1 92 1200*+ The single columns mean: po: Port number id: Port SSID, on interlink-only ports "--" td: TxDelay in 10 ms units qso: number of QSOs on this port, internode QSOs are also counted usr: number of stations heard on this port (since 3 mins) tifr: transmitted I-frames within the last 10 mins rifr: received I-frames within the last 10 mins tkby: transmitted kilobytes within the last 10 mins rkby: received kilobytes within the last 10 mins qty: quality of the channel; this is updated every 10 mins, but not if there was nothing to send. mode: Baudrate on this port, additionally: "c" KISS: CRC-Mode, HDLC: Software-DCD (depends on hardware) "d" fullduplex "t" external TX-Clock "r" external RX-Clock "z" NRZ mode "m" DAMA master "s" port is synchronized "u" port is user port "y" autosysop "+" 8 Mhz CPU-Clock (RMNC) "!" 12 Mhz CPU-Clock (RMNC) "#" 16 Mhz CPU-Clock (RMNC) links: see -Command When counting the I-frames, re-iterated frames and frames which got lost due to DISC are not counted. The kilobyte statements are only the contents of the acknowledged I-frames, re-iterations are not counted, too. Thus, this is the genuine net data rate. 4.1.16. uit -------------- Syntax: Q The QUIT-Command ends the QSO with the node. After a "73!" you get disconnected. If you are connected from another FlexNet node, you will be reconnected to that node. 4.1.17. etsearch ------------------- Syntax: S The SETSEARCH-Command displays all digipeaters via which the FIND-Command searches for someone. Example: =>S search digi's: DB0ODW DB0KT via DB0ODW DB0AAI via DB0ODW DB0DA via DB0ODW DB0IE via DB0ODW => The frame generated by the FIND-Command would be sent via DB0ODW, DB0KT, DB0DA, DB0AAI and DB0IE. 4.1.18. alk -------------- Syntax: T [] With this command you can talk to other users connected to the node. There are two modes: If there is a text given behind the callsign, then this line is sent and you get back to the prompt. Thus, you have to issue a new Talk-Command for each line. By "T " you get into the permanent talk mode which can be left later by using "/q". This is similar to convers mode, with the difference that it does not happen on a convers channel. All Convers-Commands are active and the current status can be displayed with "/c". 4.1.19. sers --------------- Syntax: U [n] The USERS-command displays all users which have a QSO with or via the node. Additional information is provided: Example: => U 1: S5 P0: DB0ODW>DG3FBL 6: S7 U1 P0: DB0ODW>DK7WJ 35: S5 P0: DL1AA>DB0GV v DB0ODW DB0KT 2014: S5 P8: DB0GV>DL1AA v DB0KT DB0ODW i.e. 1. column: QSO number. The node uses this number for internal management of the QSO. 2. column: QSO state. This number shows the state of the QSO. (see appendix for explanation) 3. column: shows the number of unacknowledged frames of the QSO, if there are any. 4. column: port 5. column: calls and digipeater field The QSOs with the node are shown first, then the ones which run via the node. Additional parameters may be specified on the "U" command line. If you enter an "i", only QSOs with the node are shown. If you enter a port number, you get all QSOs via that port. Using "U *" you get additional information about the QSOs. The parameters may be combined. For example, "U * 4" shows all QSOs on port 4 with detailed information. Example: => U * 1: S5 F100 M3 P0 : DB0ODW > DG3FBL 6: S7 U1 F87 M7 P0 : DB0ODW > DK7WJ 35: S5 ! F50 M4 P0 : DL1AA > DB0GV v DB0ODW DB0KT 2014: S5 ! F66 M7 P8 : DB0GV > DL1AA v DB0KT DB0ODW Additionally, the actual FRACK time "Fxxx" and the MAXFRAME "Mx" are shown for each QSO. On DAMA masters the DAMA priority is shown instead of FRACK. A "!" in front of the F-value says, that the QSO is using header- compression (see section 9.8). -----Inline Attachment Follows----- Command summary for FlexNet Nodes (Version 3.3g) ------------------------------------------------ A shows information about Destination calls B shows beacon text C [options] connect to station ; possible options: : use path via : use path via with : use path via (a maximum of 6 of these options can be given) C - change to (user)port C shows all participants of convers (with channelnumber) and users of the infobox (with '---'); after the prompt 'channel?' you can type the channel number to enter a spe- cific channel or type RETURN to go back to the infobox commands in the convers mode: /w shows all users of convers and infobox /w shows all users of convers channel /c shows the current channel number of the convers /s sends to the user /t starts talk mode to user /t exits talk mode /q Quit, exits convers or talk mode D shows destination table (list of reachable nodes) with SSID range and RTT in tenth of a second D like D, shows only destinations with the string e.g. prefix or suffix D * like D, shows also destinations that would be available via a loop D * combination of 'D *' and 'D ' D shows RTT and choosen path to D * shows RTT via different available paths D > shows RTT of all nodes of the path in between F search for H shows this help text I shows information about the node (if available) L shows link information of the node L * like L, additionally shows the last 16 measured RTT's LO shows local info text M connects to the (local) mailbox (if defined) M ? shows call of the (local) mailbox (if defined) MH shows MHeard list: list of stations with time since the last activity; possible options: : callsign : shows only stations with the string e.g. prefix or suffix : shows last 16..300 entries; default: 30 entries MY shows callsign of the node with SSID range P shows parameters (layer 1/2 parameters) P * like P, with additional information (see below) P [*] like P or 'P *' only for port Q disconnect from the node S shows searchpaths for the FIND command (setsearch text) ST shows internal port statistics T talk mode, sends to user T * sends to all users connected to the infobox T starts talk mode to user , the talk mode uses the same command set like the convers mode U shows user list; possible options: '*' : also shows Maxframe and Frack '=' : shows only the QSO's directly with the node (infobox) : shows only QSO's on port : shows only user Additional information when using the commands 'L *' and 'P *' : (d:142 v:1 t:193d,14h) | | +---------- time since last start/reset (uptime) | +-------------- software revision (minor updates) +-------------------- number of destinations stored in the routing list; these destination are reachable via FlexNet routing -----Inline Attachment Follows----- MULTI, server for FBB-BBS. (By LA6CU, Per) This server is used to send multi personal copies of messages. MULTI may work in 2 ways. 1: WITH DAT-FILES: created and installed on the bbs by the Sysop. In this case the original is adressed to a special "call", which is a file name of a data file created by the bbs Sysop containing the calls of everyone that shall have one. In this example all messages sent to SP CLUB will be copied to all callsigns in the file CLUB.DAT, while messages sent to SP TEST will be copied to all callsigns in the file TEST.DAT. The .DAT-files must consist of callsigns (@BBS and H-adresses allowed) for all those that shall have a copy. There are 4 different copy-types. A (action) : This is the callsign that will receive the message, or perform the action described in the message. C (copy) : This callsign receives a copy of the message. I (information) : This callsign receives a copy for information. H (hidden) : This callsign receives a copy, but his callsign will not appear in the footnotes of the message, telling who has received a copy. There may be more than one callsign on each line (starting with A, I, C or H) seperated by a comma. There may be maximum 100 callsigns altogether. Comment-lines are extras, they MUST start with a # From version 3.00 there will also be a seperate line with a letter corresponding to the language the server will use. What letter corresponds to what language, is explained in below. Example of CLUB.DAT: E <----- Use ENGLISH language for CLUB-server A LA6CU, LA1B, LA2D <----- Copies to the people doing the job A LA6GDA <----- " " " " " " " May be several lines if there is not enough room in one line. I LA5RBA <----- LA5RBA is informed on the matter C LA6IM @ LA6IM <----- LA6IM receives a copy for updating his node-lists H LA2GIA <----- LA2GIA receives a copy, but will not appear in the list of callsigns at the end of each message. Beware: The .DAT-files shall consist of callsigns and comments, nothing else ! No /EX, no * and no *** end of file. MULTI will NOT send a copy back to the originator, even if he also is in the .DAT-file. This to avoid "looping" of messages. MULTI will send an acknowledge-message back to the originator, telling him that the copying was successful, and show him a list of all callsigns that will receive such a copy. 2: WITH ALL CALLSIGNS DIRECTLY IN THE ORIGINAL-MESSAGE. -------------------------------------------------------- MULTI still works exactly as above. Users themselves can decide what callsigns will receive a copy. This is done by addressing the message to any one of the forms of MULTI as indicated below, which specifies the language to be used, and by including the callsigns in the message itself. From version 3.00 SP MULTI uses the default language. Other languages may be configured. For example you may have: MULTI MULTI (for default language) MULTIE MULTI (for english language) MULTIF MULTI (for french language) MULTIH MULTI (for netherlands language) MULTIN MULTI (for norwegian language) So, you may send the same message SP MULTI, SP MULTIE, SP MULTIF, SP MULTIH, SP MULTIN etc. The first 5 letters must always be MULTI, when used without DAT-file. Default language will typically be english (SP MULTI), but the users have the possibillity to use others, as configured. Users will now be able to send messages to MULTI, like this: SP MULTI The program will now collect the info on who will receive a copy, from the message itself, and not from a seperat .DAT-file like SP CLUB or SP TEST still will do. There are 4 different copy-types. A (action) : This is the callsign that will receive the message, or perform the action described in the message. C (copy) : This callsign receives a copy of the message. I (information) : This callsign receives a copy for information. H (hidden) : This callsign receives a copy, but his callsign will not appear in the footnotes of the message, telling who has received a copy. (In addition one may use CC: instead of only C for Copy. Special request..) There may be more than one callsign on each line (starting with A, I, C or H) seperated by a comma. There may be maximum 100 callsigns altogether. Comment-lines are extras, they MUST start with a # Example: SP MULTI Digipeater upgrade <----- Title of message A LA6CU, LA1B, LA2D <----- Copies to the people doing the job A LA6GDA <----- " " " " " " " I LA5RBA <----- LA5RBA is informed on the matter C LA6IM @ LA6IM <----- LA6IM receives a copy for updating his node-lists H LA2GIA <----- LA2GIA receives a copy, but will not appear in the list of callsigns at the end of each message. --------- <----- After the last callsign, there must be a string of at least 5 '-' before the actual message. Then follows the contents of the message, and end with Ctrl-Z or /EX. As ususal, the sender will receive a message saying that the copies were made. The messages to all the other calligns will be identical, and look like this: Message via LA6CU MULTI-server (v3.00) : Contents of message ============================================================================ For action : LA6GDA, LA6CU, LA1B, LA2D. For copy : LA6IM. For information : LA5RBA. ============================================================================ All copies are identical, but A, C and I determines in which line in the footnotes the callsigns will appear. A callsign after an H will not appear in the footnotes. ----- Note: Origional text modified by K2BJG. -----Inline Attachment Follows----- BBS Hierarchical Addressing Protocol Authors: Dave Wolf, WO5H Roy Engehausen, AA4RE Hank Oredson, W0RLI Greg Jones, WD5IVD Date: August 30th, 1994 Adopted by TAPR: March 3rd, 1995 Send Updates to Attached Tables to: Dave Wolf, WO5H Packet: wo5h@wo5h.#dfw.tx.usa.noam Internet: wo5h@tapr.org Fax: (817) 295-6232 ------------------------------------------------------------------------- Introduction The TAPR BBS Special Interest Group recommends the adoption of the x.3.4 hierarchical address protocol. After discussion of previous articles on hierarchical addressing standards (1,2) and taking into account international issues of regional/state name sizes, the TAPR BBS Special Interest Group recommends the adoption of the x.3.4 standard on an international basis. x is defined as 2, 3, or 4 letter region names as defined by the country. Examples of x.3.4: @WA6GVD.CA.USA.NOAM @EA2CMO.EAZ.ESP.EURO @F5JGK.FAQI.FRA.EURO Regional identifiers may be duplicated in different countries (i.e. AK, Alaska, USA, could be used in another country as a regional identifier); however, Country and Continental identifiers SHOULD NOT be used as regional names. It is important to note that there is a distinct and significant difference between HIERARCHICAL ADDRESSES and FLOOD DESIGNATORS. Hierarchical address elements are common to all messages (bulletins, P and T types) and are the foundation of the digital forwarding system. Flood designators are used for routing and filtering bulletins. Geographical flood designators are likely based upon hierarchical address elements. It is therefore important that any attempt to establish standards concentrate first on hierarchical address elements. Standards for flood designators can follow. It is the purpose of this document to generate a changing recommendation that reflects current hierarchical routing. Reference Tables at the end will be changed as necessary to reflect current configurations within the international BBS network. These tables will need to be changed and updated in order to meet future needs of user and sysops. Hierarchical Routing Syntax Summary This summary uses a modified Backus-Naur form to summarize the syntax for hierarchical addressing. [] = optional @hierarchial_address bbs.[#octothorpe.][region.]country.continent bbs valid callsign as defined by local communications authority #octothorpe. #area.[#octothorpe.] #area area as defined by the local region See Table 4 for list of current area identifiers region 2,3, or 4 character region identifier as defined by the country. See Table 3 for list of region identifiers country 3 character country identifier as defined by ANSI X.12 and EDIFACT. Published in ISO 3166-1981(E/F). See Table 2 for country identifiers continent 4 character continental identifier. See Table 1 for continental identifiers. ------ Examples: F6CNB.#SETX.TX.USA.NOAM KB7WE.#WWA.WA.USA.NOAM OH6RBV.#VAA.FIN.EURO SK2AT.AC.SWE.EURO OH6RBG.FIN.EURO KE7KD.#NONEV.NV.USA.NOAM WX3K.#NOCAL.CA.USA.NOAM ------ References: 1. Jenkins, Lew (N6VV), Dave Toth (VE3GYQ), and Hank Oredson (W0RLI). International Routing Designators. Proceedings of the ARRL 7th Computer Networking Conference. Columbia Maryland. October 1, 1988. pp. 91-93. 2. Clark, Tom (W3IWI). Some comments on the `H`ierarchical Continent Address Designator. Proceedings of the ARRL 9th Computer Networking Conference. London, Ontario Canada. September 22, 1990. pp. 278-279. ------ TABLE 1: Continent Identifiers EURO -- Europe MEDR -- Mediterranean INDI -- Indian Ocean including the Indian subcontinent MDLE -- Middle East SEAS -- South-East Asia ASIA -- The Orient NOAM -- North America (Canada, USA, Mexico) CEAM -- Central America CARB -- Caribbean SOAM -- South America AUNZ -- Australia/New Zealand EPAC -- Eastern Pacific NPAC -- Northern Pacific SPAC -- Southern Pacific WPAC -- Western Pacific NAFR -- Northern Africa CAFR -- Central Africa SAFR -- Southern Africa ANTR -- Antarctica ------ TABLE 2: Country Identifiers ARG -- Argentina AUS -- Australia AUT -- Austria BEL -- Belgium BMU -- Bermuda BOL -- Bolivia BRA -- Brazil BRN -- Brunei BGR -- Bulgaria CAN -- Canada CHL -- Chile CHN -- China COL -- Colombia CRI -- Costa Rica CUB -- Cuba DNK -- Denmark DOM -- Dominican Republic ECU -- Ecuador EGY -- Egypt SLV -- El Salvador FIN -- Finland FRA -- France PYF -- French Polynesia DEU -- Germany GRC -- Greece GRL -- Greenland GTM -- Guatemala HTI -- Haiti HND -- Honduras HKG -- Hong Kong HUN -- Hungary ISL -- Iceland IND -- India IDN -- Indonesia IRL -- Ireland ISR -- Israel ITA -- Italy JPN -- Japan PRK -- Korea, North KOR -- Korea, South LBN -- Lebanon LIE -- Liechtenstein LUX -- Luxembourg MYS -- Malaysia MEX -- Mexico MCO -- Monaco MAR -- Morocco NLD -- Netherlands NZL -- New Zealand NIC -- Nicaragua NOR -- Norway PAK -- Pakistan PAN -- Panama PRY -- Paraguay PER -- Peru PHL -- Phillipines POL -- Poland PRT -- Portugal ROM -- Romania SAU -- Saudi Arabia SGP -- Singapore ZAF -- South Africa ESP -- Spain SWE -- Sweden CHE -- Switzerland SYR -- Syria TWN -- Taiwan THA -- Thailand TUR -- Turkey GBR -- United Kingdom USA -- United States URY -- Uruguay SUN -- USSR ??? (Document needs latest defintions) VEN -- Venezuela YUG -- Yugoslavia ------ TABLE 3: Region Identifiers organized by Country Codes. ARG -- Argentina BA -- ?? CF -- ?? AUS -- Australia ?? AUT -- Austria ?? BEL -- Belgium HT -- ?? LG -- ?? OVN -- ?? WVL -- ?? BMU -- Bermuda ?? BOL -- Bolivia ?? BRA -- Brazil RS -- ?? SP -- ?? BRN -- Brunei ?? BGR -- Bulgaria ?? CAN -- Canada NF -- Newfoundland AB -- Alberta BC -- British Columbia MB -- Manitoba NB -- New Brunswick NS -- Nova Scotia NW -- Northwest Territories ON -- Ontario PQ -- Province du Quebec SK -- Saskatchewan YK -- Yukon CHL -- Chile ?? CHN -- China ?? COL -- Colombia ?? CRI -- Costa Rica ?? CUB -- Cuba ?? DNK -- Denmark ?? DOM -- Dominican Republic ?? ECU -- Ecuador ?? EGY -- Egypt ?? SLV -- El Salvador ?? FIN -- Finland ?? FRA -- France FCEN -- ?? FRPA -- ?? FCAL -- ?? FPDL -- ?? FMLR -- ?? FNOR -- ?? FCOR -- ?? FPOC -- ?? FAQI -- ?? PYF -- French Polynesia ?? DEU -- Germany BY -- ?? GRC -- Greece ?? GRL -- Greenland ?? GTM -- Guatemala none HTI -- Haiti ?? HND -- Honduras ?? HKG -- Hong Kong ?? HUN -- Hungary ?? ISL -- Iceland ?? IND -- India ?? IDN -- Indonesia ?? IRL -- Ireland ?? ISR -- Israel ?? ITA -- Italy IEMR -- ?? IFVG -- ?? ILOM -- ?? IPIE -- ?? IPUG -- ?? ISAR -- ?? ISIC -- ?? ITAA -- ?? IVEN -- ?? MO -- ?? JPN -- Japan ?? PRK -- Korea, North ?? KOR -- Korea, South ?? LBN -- Lebanon ?? LIE -- Liechtenstein ?? LUX -- Luxembourg ?? MYS -- Malaysia ?? MEX -- Mexico ?? MCO -- Monaco ?? MAR -- Morocco ?? NLD -- Netherlands ?? NZL -- New Zealand ?? NIC -- Nicaragua ?? NOR -- Norway ?? PAK -- Pakistan ?? PAN -- Panama ?? PRY -- Paraguay ?? PER -- Peru ?? PHL -- Phillipines ?? POL -- Poland ?? PRT -- Portugal CTPT -- ?? ROM -- Romania ?? SAU -- Saudi Arabia ?? SGP -- Singapore ?? ZAF -- South Africa ?? ESP -- Spain EAA -- Alicante EAAB -- Albacete EAAL -- Almeria EAAV -- Avila EAB -- Barcelona EABA -- Badajoz EABI -- Vizcaya (Bilbao) EABU -- Burgos EAC -- Coruna EACA -- Cadiz EACC -- Caceres EACE -- Ceuta EACO -- Cordoba EACR -- Ciudad Real EACS -- Castellon EACU -- Cuenca EAGC -- Gran Canaria EAGI -- Gerona EAGR -- Granada EAGU -- Guadalajara EAH -- Huelva EAHU -- Huesca EAJ -- Jaen EAL -- Lerida EALE -- Leon EALO -- Logrono EALU -- Lugo EAM -- Madrid EAMA -- Malaga EAML -- Melilla EAMU -- Murcia EANA -- Navarra (Pamplona) EAO -- Oviedo EAOR -- Orense EAP -- Palencia EAPM -- Baleares (Palma de Mallorca) EAPO -- Pontevedra EAS -- Santander EASA -- Salamanca EASE -- Sevilla EASG -- Segovia EASO -- Soria EASS -- Guipuzcoa (San Sebastian) EAT -- Tarragona EATE -- Teruel EATF -- Tenerife EATO -- Toledo EAV -- Valencia EAVA -- Valladolid EAVI -- Alava (Vitoria) EAZ -- Zaragoza EAZA -- Zamora SWE -- Sweden AC -- ?? CHE -- Switzerland ?? SYR -- Syria ?? TWN -- Taiwan ?? THA -- Thailand ?? TUR -- Turkey ?? GBR -- United Kingdom (need a list of routing numbers by county) #1 -- ?? #2 -- ?? # ...-- ?? USA -- United States AK -- Alaska AL -- Alabama AR -- Arkansas AZ -- Arizona CA -- California CO -- Colorado CT -- Connecticut DE -- Delaware FL -- Florida GA -- Georgia HI -- Hawaii IA -- Iowa ID -- Idaho IL -- Illinois IN -- Indiana KS -- Kansas KY -- Kentucky LA -- Louisiana MA -- Massachusetts MD -- Maryland ME -- Maine MI -- Michigan MI -- Mississippi MN -- Minnesota MO -- Missouri MT -- Montana NC -- North Carolina ND -- North Dakota NE -- Nebraska NH -- New Hampshire NJ -- New Jersey NM -- New Mexico NV -- Nevada NY -- New York OH -- Ohio OK -- Oklahoma OR -- Oregon PA -- Pennsylvania RI -- Rhode Island SC -- South Carolina SD -- South Dakota TN -- Tennessee TX -- Texas UT -- Utah VA -- Virginia VT -- Vermont WA -- Washington WI -- Wisconsin WV -- West Virginia WY -- Wyoming URY -- Uruguay MVD -- ?? SUN -- USSR ??? (Document needs latest defintions) ?? VEN -- Venezuela YUG -- Yugoslavia SRB -- ?? ------ Table 4: Area Defintions This table to be defined during the comment period. All readers are suggested to submit their regional area defintions for inclusion in the table. Be sure to include the region and country. Example: #DFW.TX.USA -- Dallas/Ft Worth Texas Area would be an entry in this table. -----Inline Attachment Follows----- SUBJECT: 3 Digit Zip Codes ------------------------------------------------ MA 010,011,012,013,014,015,016,017,018,019,020,021,022,023,024,025,026,027 RI 028,029 NH 030,031,032,033,034,035,036,037,038 ME 039,040,041,042,043,044,045,046,047,048,049 VT 050,051,052,053,054,055,056,057,058,059 CT 060,061,062,063,064,065,066,067,068,069 NJ 070,071,072,073,074,075,076,077,078,079,080,081,082,083,084,085,086,087, 088,089 NY 100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117, 118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135, 136,137,138,139,140,141,142,143,144,145,146,147,148,149 PA 150,151,152,153,154,155,156,157,158,159,160,161,162,163,164,165,166,167, 168,169,170,171,172,173,174,175,176,177,178,179,180,181,182,183,184,185, 186,187,188,189,190,191,192,193,194,195,196 DE 197,198,199 DC 200,201,202,203,204,205 MD 206,207,208,209,210,211,212,213,214,215,216,217,218,219 VA 220,221,222,223,224,225,226,227,228,229,230,231,232,233,234,235,236,237, 238,239,240,241,242,243,244,245,246 WV 247,248,249,250,251,252,253,254,255,256,257,258,259,260,261,262,263,264, 265,266,267,268,269 NC 270,271,272,273,274,275,276,277,278,279,280,281,282,283,284,285,286,287, 288,289 SC 290,291,292,293,294,295,296,297,298,299 GA 300,301,302,303,304,305,306,307,308,309,310,311,312,313,314,315,316,317, 318,319 FL 320,321,322,323,324,325,326,327,328,329,330,331,332,333,334,335,336,337, 338,339,340,341,342 AL 350,351,352,353,354,355,356,357,358,359,360,361,362,363,364,365,366,367, 368,369 TN 370,371,372,373,374,375,376,377,378,379,380,381,382,383,384,385 MS 386,387,388,389,390,391,392,393,394,395,396,397,398,399 KY 400,401,402,403,404,405,406,407,408,409,410,411,412,413,414,415,416,417, 418,419,420,421,422,423,424,425,426,427,428,429 OH 430,431,432,433,434,435,436,437,438,439,440,441,442,443,444,445,446,447, 448,449,450,451,452,453,454,455,456,457,458,459 IN 460,461,462,463,464,465,466,467,468,469,470,471,472,473,474,475,476,477, 478,479 MI 480,481,482,483,484,485,486,487,488,489,490,491,492,493,494,495,496,497, 498,499 IA 500,501,502,503,504,505,506,507,508,509,510,511,512,513,514,515,516,517, 518,519,520,521,522,523,524,525,526,527,528,529 WI 530,531,532,534,535,536,537,538,539,540,541,542,543,544,545,546,547,548, 549 MN 550,551,552,553,554,555,556,557,558,559,560,561,562,563,564,565,566,567, 568,569 SD 570,571,572,573,574,575,576,577,578,579 ND 580,581,582,583,584,585,586,587,588,589 MT 590,591,592,593,594,595,596,597,598,599 IL 600,601,602,603,604,605,606,607,608,609,610,611,612,613,614,615,616,617, 618,619,620,621,622,623,624,625,626,627,628,629 MO 630,631,632,633,634,635,636,637,638,639,640,641,642,643,644,645,646,647, 648,649,650,651,652,653,654,655,656,657,658,659 KS 660,661,662,663,664,665,666,667,668,669,670,671,672,673,674,675,676,677, 678,679 NE 680,681,682,683,684,685,686,687,688,689,690,691,692,693,694,695,696,697, 698,699 LA 700,701,702,703,704,705,706,707,708,709,710,711,712,713,714,715 AR 716,717,718,719,720,721,722,723,724,725,726,727,728,729 OK 730,731,732,733,734,735,736,737,738,739,740,741,742,743,744,745,746,747, 748,749 TX 750,751,752,753,754,755,756,757,758,759,760,761,762,763,764,765,766,767, 768,769,770,771,772,773,774,775,776,777,778,779,780,781,782,783,784,785, 786,787,788,789,790,791,792,793,794,795,796,797,798,799 CO 800,801,802,803,804,805,806,807,808,809,810,811,812,813,814,815,816,817, 818,819 WY 820,821,822,823,824,825,826,827,828,829,830,831 ID 832,833,834,835,836,837,838,839 UT 840,841,842,843,844,845,846,847,848,849 AZ 850,851,852,853,854,855,856,857,858,859,860,861,862,863,864,865,866,867, 868,869 NM 870,871,872,873,874,875,876,877,878,879,880,881,882,883,884,885,886,887, 888,889 NV 890,891,892,893,894,895,896,897,898,899 CA 900,901,902,903,904,905,906,907,908,909,910,911,912,913,914,915,916,917, 918,919,920,921,922,923,924,925,926,927,928,929,930,931,932,933,934,935, 936,937,938,939,940,941,942,943,944,945,946,947,948,949,950,951,952,953, 954,955,956,957,958,959,960,961,962,963,964,965,966 HI 967,968 GU 969 OR 970,971,972,973,974,975,976,977,978,979 WA 980,981,982,983,984,985,986,987,988,989,990,991,992,993,994 AK 995,996,997,998,999