home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Rat's Nest 1
/
ratsnest1.iso
/
incoming
/
hgrnode.lst
< prev
next >
Wrap
File List
|
1997-04-26
|
15KB
|
320 lines
; HGRnet nodelista 23.04-97.
;
;
Zone,109,HGRnet_Finland,HGRnet,Node_Coordinator,358-5-2264823,9600,CM,XA,MNP,V34,HST,V42B,FAX,NC
Region,100,HGRnet,Kotka_FIN,Juha_Ääpälä,358-5-2264823,9600,CM,XA,MNP,V34,HST,V42B,FAX
;
Host,100,SouthEast_Finland,Kotka_FIN,Juha_Ääpälä,358-5-2264823,9600,CM,XA,MNP,V34,HST,V42B,FAX
Hub,100,Hangar,Kotka,Juha_Ääpälä,358-5-2264823,9600,CM,XA,MNP,V34,HST,V42B,FAX
,111,Hangar,Kotka,Juha_Ääpälä,358-5-2264823,9600,CM,XA,MNP,V34,HST,V42B,FAX
,112,Hangar,Kotka,Juha_Ääpälä,358-5-2264823,9600,CM,XA,MNP,V34,HST,V42B,FAX
,150,Lusmu,Anjalankoski,Antti_Pässilä,358-5-3674193,9600,CM,XA,V32B
,200,ParaSite BBS,Kotka,Kimmo_Viitanen,358-5-2287040,9600,CM,XA,V32B
,371,Assimilation,Kuusankoski,Ilkka_Tommola,358-5-3822006,9600,CM,XA,V34
,555,Mordor_BBS,Iitti,Juha_Talikka,358-5-3264428,9600,V34,TuH
,609,Poks,Kouvola,Jukka_Hynninen,358-5-3118677,9600,XW,V34,V42B
,629,Digital_Imagination,Kouvola,Vesa_Jääskeläinen,358-5-3119340,9600,XX,V34,V42B,TwG
,769,ToxicAnt,Lappeenranta,Jari_Kohvakka,358-5-4527789,9600,XA,V32B,V42B,CM
,888,Rölli's Lair BBS,Kotka,Samppa_Rönkä,358-5-2188621,9600,V34,TXE
;
Host,200,Helsinki_Area,Kirkkonummi,Ari_Liekola,358-9-2218725,9600,CM,XA,V32B
Hub,100,Actus_Purus_BBS,Kirkkonummi,Ari_Liekola,358-9-2218725,9600,CM,XA,V32B
;
Host,300,Southwest_Finland,Raisio,Johan_Paul,358-2-4384838,9600,CM,XW,V34,V42B
Hub,100,RedZone,Raisio,Johan_Paul,358-2-4384838,9600,CM,XW,V34,V42B
,150,The_Edge,Rauma,Ville_Ilen,358-2-8251610,9600,CM,XX,V34,V42B
;
Host,400,West_Finland,Seinäjoki,Jouni_Harju,358-6-4231305,9600,CM,V42B,V34,XW
Hub,100,Scream,Seinäjoki,Jouni_Harju,358-6-4231305,9600,CM,V42B,V34,XW
;
;
; Flags
; -------------------------------------------------------
; V21 CCITT V21 300 bps full duplex
; V22 CCITT V22 1200 bps full duplex
; V29 CCITT V29 9600 bps half duplex
; V32 CCITT V32 9600 bps full duplex
; V32B CCITT V32bis 14400 bps full duplex
; V33 CCITT V33
; V34 CCITT V34 28800 bps full duplex
; V42 LAP-M error correction w/fallback to MNP 1-4
; V42B LAP-M error correction w/fallback to MNP 1-5
; MNP Microcom Networking Protocol error correc
;
; H96 Hayes V9600
; HST USR Courier HST
; H14 USR Courier HST up to 14.4Kbps
; H16 USR Courier HST up to 16.8Kbps
; MAX Microcom AX/96xx series
; PEP Packet Ensemble Protocol
; CSP Compucom Speedmodem
; V32T V.32 Terbo mode
; VFC Rockwell's V.Fast Class
; ZYX Zyxel (implies V.32Bis & V.42Bis)
;
; CM Node accepts mail 24 hours a day
; MO Node does not accept human callers
; LO Node accepts calls Only from Listed addresses
;
;
; Below is a cut from the fido net nodlist for additional flags
;
;S NOTE: Many V22 modems also support Bell 212A.
;S
;S If no modem flag is given, ITU-T V.22 is assumed within zone 2
;S for 1200bps, while Bell 212A is assumed for 1200 bps systems in
;S other zones, ITU-T V22bis is assumed for 2400 bps systems.
;S
;S A separate modem capability flag should not be used when it can be
;S determined by the modem flag. For instance, a modem flag of HST
;S implies MNP. V32B implies V32 and V42B implies V42. MNP,HST and
;S V32,V32B and V42,V42B flag pairs are unnecessary. H14 implies HST
;S and H16 implies H14 as well as V42.Bis .
;S
;S
;S The following flags define the type(s) of compression of mail
;S packets supported.
;S
;S Flag Meaning
;S
;S MN No compression supported
;S
;S NOTE: The only compression method standard in
;S FidoNet is archiving, using the standard SEA ARC
;S format, with archive names defined by the
;S specification for ARCMail 0.6. The absence of the
;S MN flag indicates that ARCMail 0.6 compression is
;S supported by this node.
;S
;S
;S The following flags indicate the types of file/update requests
;S supported.
;S
;S |----------------------------------------------------------|
;S | | Bark | WaZOO |
;S | |-------------------------|-------------------------|
;S | | File | Update | File | Update |
;S | Flag | Requests | Requests | Requests | Requests |
;S |------|------------|------------|------------|------------|
;S | XA | Yes | Yes | Yes | Yes |
;S | XB | Yes | Yes | Yes | No |
;S | XC | Yes | No | Yes | Yes |
;S | XP | Yes | Yes | No | No |
;S | XR | Yes | No | Yes | No |
;S | XW | No | No | Yes | No |
;S | XX | No | No | Yes | Yes |
;S |----------------------------------------------------------|
;S
;S
;S The following software is qualified to use the
;S appropriate file request flag:
;S
;S |---------------------------------------|
;S | File Req Flag Software Package |
;S |---------------------------------------|
;S | XA Frontdoor <1.99b |
;S | Frontdoor 2.01+ |
;S | Dutchie 2.90c |
;S | Binkleyterm >2.1 |
;S | D'Bridge <1.3 |
;S | TIMS |
;S |---------------------------------------|
;S | XB Binkleyterm 2.0 |
;S | Dutchie 2.90b |
;S |---------------------------------------|
;S | XC Opus 1.1 |
;S |---------------------------------------|
;S | XP Seadog |
;S |---------------------------------------|
;S | XR Opus 1.03 |
;S |---------------------------------------|
;S | XW Fido >12M |
;S | Tabby |
;S |---------------------------------------|
;S | XX D'Bridge 1.30 |
;S | Frontdoor 1.99b |
;S | InterMail 2.01 |
;S | T-Mail |
;S |---------------------------------------|
;S | None QMM |
;S |---------------------------------------|
;S
;S
;S
;S The following flag defines gateways to other domains (networks).
;S
;S Flag Meaning
;S
;S Gx..x Gateway to domain 'x..x', where 'x..x` is a string
;S of alphanumeric characters. Valid values for 'x..x'
;S are assigned by the FidoNet International
;S Coordinator. This flag is not authorized for use by
;S any node unless specifically authorized by the IC or
;S FidoNet Inter-Network Coordinator. Registered
;S domain gateways include:
;S
;S uucp to be used only by nodes in a list of
;S authorized fidonet.org sites available at
;S 1:1/31.
;S
;S intlnet Contact David Nugent for further details
;S
;S
;S The following flags define the dedicated mail periods supported.
;S They have the form "#nn" or !nn where nn is the UTC hour the mail
;S period begins, # indicates Bell 212A compatibility, and !
;S indicates incompatibility with Bell 212A.
;S
;S Flag Meaning
;S
;S #01 Zone 5 mail hour (01:00 - 02:00 UTC)
;S #02 Zone 2 mail hour (02:30 - 03:30 UTC)
;S #08 Zone 4 mail hour (08:00 - 09:00 UTC)
;S #09 Zone 1 mail hour (09:00 - 10:00 UTC)
;S #18 Zone 3 mail hour (18:00 - 19:00 UTC)
;S #20 Zone 6 mail hour (20:00 - 21:00 UTC)
;S
;S NOTE: When applicable, the mail period flags may
;S be strung together with no intervening commas, eg.
;S "#02#09". Only mail hours other than that standard
;S within a node's zone should be given. Since
;S observance of mail hour within one's zone is
;S mandatory, it must not be indicated.
;S
;S
;S The final field may be used for user-specific values. If present,
;S field MUST be the last field present in the nodelist entry. The
;S user field is separated from the rest of the nodelist entry by a
;S comma (,) and the first character is an upper case "U". Flags
;S within this field are separated from each other with a single
;S comma.
;S
;S
;S Field Meaning
;S
;S Ux..x A user-specified string, which may contain any
;S alphanumeric character except blanks. This string
;S may contain one to thirty-two characters of
;S information that may be used to add user-defined
;S data to a specific nodelist entry. The character "U"
;S should NOT be repeated, eg, "U,XXX,YYY" not "UXXX,UYYY".
;S
;S For maximum compatibility with FTN software, it is
;S recommended that the initial "U" is immediately followed
;S by a comma and the any user flags required, as in the
;S above example.
;S
;S This string is NOT to be used for advertisements, or
;S non-essential information. If you have questions
;S concerning the use of this string, please contact your
;S Network, Regional or Zone Coordinator.
;S
;S This string may not be used, in zone 2, without ZC/2
;S authorisation.
;S
;S Zone 2 authorised 'user' flags:-
;S
;S Modem capability flags
;S
;S <None for the moment>
;S
;S NetMail Coordination when (NC not= Host)
;S
;S NC Network Coordinator. This flag is ONLY to be used by
;S the Network Coordinator of a net which has split the
;S duties of NC and Host and the NC does NOT occupy the
;S Net/0 position in the nodelist.
;S
;S EchoMail Coordination:
;S
;S ZEC Zone EchoMail Coordinator. Not more than one entry
;S in the zone 2 segment may carry this flag and that must
;S be the current Zone EchoMail Coordinator.
;S
;S REC Regional EchoMail Coordinator. Not more than one
;S entry in any region may carry this flag and that must
;S be the current Regional EchoMail Coordinator.
;S
;S NEC Network EchoMail coordinator. Not more than one entry
;S in any net may carry this flag and that must be the
;S current Network EchoMail Coordinator of that Net. This
;S flag will be authorised by the relevant Regional EchoMail
;S Coordinator.
;S
;S Note: * Redundant AKAs used to indicate EchoMail
;S Coordination functions are no longer permitted.
;S * One *EC-flag is valid for all AKA's of a given
;S sysop
;S
;S Special flags:
;S
;S K12 The K12-flag identifies systems offering the full
;S range of educational K12-conferences.
;S
;S Special technical nodenumbers:
;S
;S 2:2/1000 ZEC. Override of the "U,ZEC"-flag.
;S
;S 2:2/1001 Echolist-keeper.
;S
;S 2:2/1002 Postmaster of "z2.fidonet.org". Internet-gates as well
;S as use of the GUUCP must be approved by this person.
;S
;S System open hours:
;S
;S Txx Availability flag for non-CM nodes indicating the
;S hours during which the node is available in addition
;S to ZMH. This must be in accordance with the recommen-
;S dations in FSC-0062 and the reference table reproduced
;S below:
;S
;S +------+----+ +------+----+ +------+----+ +------+----+ +------+----+
;S |Letter|Time| |Letter|Time| |Letter|Time| |Letter|Time| |Letter|Time|
;S +------+----+ +------+----+ +------+----+ +------+----+ +------+----+
;S | A |0000| | F |0500| | K |1000| | P |1500| | U |2000|
;S | a |0030| | f |0530| | k |1030| | p |1530| | u |2030|
;S | B |0100| | G |0600| | L |1100| | Q |1600| | V |2100|
;S | b |0130| | g |0630| | l |1130| | q |1630| | v |2130|
;S | C |0200| | H |0700| | M |1200| | R |1700| | W |2200|
;S | c |0230| | h |0730| | m |1230| | r |1730| | w |2230|
;S | D |0300| | I |0800| | N |1300| | S |1800| | X |2300|
;S | d |0330| | i |0830| | n |1330| | s |1830| | x |2330|
;S | E |0400| | J |0900| | O |1400| | T |1900| | | |
;S | e |0430| | j |0930| | o |1430| | t |1930| | | |
;S +------+----+ +------+----+ +------+----+ +------+----+ +------+----+
;S
;S
;S ISDN connected nodes:
;S
;S ISDNA 19200 N 8 1, ITU-T V.110/ECMA 102, Hayes compatible,
;S ISDN only
;S
;S ISDNB 38400 N 8 1, ITU-T V.110/ECMA 102, Hayes compatible,
;S ISDN only
;S
;S ISDNC 64000, ISDN Common API, X.75, ISDN only
;S
;S Technical restrictions:
;S
;S ITU-T V.110 is a Modem emulation with implementation of connect requests via
;S Hayes command set or V.25.bis. As the Hayes AT command set is used on
;S analog connections, it is recommended for use on ISDN connections as well.
;S
;S For ALL 3 flags, the following restrictions apply:
;S
;S ONLY nodes with the SAME FLAG may CONNECT with each other. This is due to
;S the fact that under ISDN, auto-baud detect is not possible and CAPI
;S applications currently cannot connect using V.110 modem emulation.
;S
;S Nodes using these flags should use a modem "speed" of 300 baud. This is
;S due to limitations imposed by nodelist processing software.
;S
;S Nodelist entries would look (perhaps) like this:
;S
;S ,34,Deti's_BBS,Dortmund,Detlef_Koester,99-999-1234567,300,U,ISDNA
;S
;S ,34,Deti's_BBS,Dortmund,Detlef_Koester,99-999-2345678,300,U,ISDNB
;S
;S ,34,Deti's_BBS,Dortmund,Detlef_Koester,99-999-3456789,300,U,ISDNC
;S