Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
ref:qwknet [2012/07/19 19:54] – [See Also] digitalman | ref:qwknet [2012/07/19 21:48] – [Basics] Typo deuce |
---|
| |
QWK IDs (AKA BBSID) consist of between two and eight valid DOS characters and the first character must be alphabetic. QWK IDs must not contain the '@' character. It is extremely beneficial if all QWK IDs are unique in a given network of systems. QWK IDs that do not match this format may work for basic | QWK IDs (AKA BBSID) consist of between two and eight valid DOS characters and the first character must be alphabetic. QWK IDs must not contain the '@' character. It is extremely beneficial if all QWK IDs are unique in a given network of systems. QWK IDs that do not match this format may work for basic |
QWKnet functions, but many features may not work. QWK IDs are always considered case insensitive. The strings "SYSOP" and "NETMAIL" must are not valid QWK IDs. | QWKnet functions, but many features may not work. QWK IDs are always considered case insensitive. The strings "SYSOP" and "NETMAIL" are not valid QWK IDs. |
| |
A QWKnet node on a Synchronet BBS must be created specifically for QWK networking. This is done by using the node's QWK ID as the user name on the BBS and the sysop must give the account the 'Q' restriction. This restriction allows the uploaded REP packets to come from any user name (AKA Net Status) and automatically eliminates non-QWK networked sub-boards from the QWK packets. The 'Q' restriction causes the QWK menu to immediately come up at logon (rather than the normal "user" logon procedure), taglines are added to locally created messages being exported to REP packets, as well as other behavior differences from normal "user" accounts. Synchronet creates a NETFLAGS.DAT file for 'Q' restricted accounts that haven't disabled CONTROL files in the QWK packets, though Synchronet itself does not ever use the NETFLAGS.DAT - it's created for compatibility with non-Synchronet QWKnet nodes. | A QWKnet node on a Synchronet BBS must be created specifically for QWK networking. This is done by using the node's QWK ID as the user name on the BBS and the sysop must give the account the 'Q' restriction. This restriction allows the uploaded REP packets to come from any user name (AKA Net Status) and automatically eliminates non-QWK networked sub-boards from the QWK packets. The 'Q' restriction causes the QWK menu to immediately come up at logon (rather than the normal "user" logon procedure), taglines are added to locally created messages being exported to REP packets, as well as other behavior differences from normal "user" accounts. Synchronet creates a NETFLAGS.DAT file for 'Q' restricted accounts that haven't disabled CONTROL files in the QWK packets, though Synchronet itself does not ever use the NETFLAGS.DAT - it's created for compatibility with non-Synchronet QWKnet nodes. |
Yellow Y 3 | Yellow Y 3 |
Blue B 4 | Blue B 4 |
Magenta M 5 | Magenta M 5 |
Cyan C 6 | Cyan C 6 |
White W 7 | White W 7 |
First, the network topology (abbreviated for this example): | First, the network topology (abbreviated for this example): |
<code> | <code> |
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄVERTÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ | +----------------+---------VERT----------------------+ |
³ ³ ³ ³ | | | | | |
ÚÄÄÄÄÄÄPHOUSEÄÄÄÄÄ¿ DOMAIN NITEMOVE ÚÄÄÄÄÄÄCENTURYÄÄÄÄÄÄ¿ | +------PHOUSE-----+ DOMAIN NITEMOVE +------CENTURY------+ |
³ ³ ³ ³ ³ ³ ³ | | | | | | | | |
CIRCLE7 FANTAIR KRYSTAL ÚÄÄÄÄÄÄTLOCÄÄÄÄÄÄ¿ TALONBBS VSS_BBS PHOENIX | CIRCLE7 FANTAIR KRYSTAL +------TLOC------+ TALONBBS VSS_BBS PHOENIX |
³ ³ | | | |
BLAZING WILDHARE | BLAZING WILDHARE |
</code> | </code> |