introduction
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
introduction [2018/01/03 15:02] – removed mbbsutil references - fully depreciated in 1.12 A37 avon | introduction [2018/01/03 21:55] – added additional switches avon | ||
---|---|---|---|
Line 10: | Line 10: | ||
MYSTIC -CFG This tells Mystic to start in local configuration mode. | MYSTIC -CFG This tells Mystic to start in local configuration mode. | ||
+ | | ||
+ | MYSTIC -ANSI This invokes the built in ANSI editor using the syntax | ||
+ | | ||
+ | open that file otherwise it will create an empty buffer. | ||
+ | |||
+ | The ANSI editor can load display files with color codes from | ||
+ | | ||
+ | can save in ASCII or Pipe Code or ANSI and includes variable | ||
+ | line length saving for ANSI files as well as some display | ||
+ | | ||
| | ||
MYSTIC -CP$ This tells Mystic in Unix environments to start in a | MYSTIC -CP$ This tells Mystic in Unix environments to start in a | ||
Line 18: | Line 28: | ||
| | ||
MYSTIC -IP$ This specifies the user's IP address which should be passed | MYSTIC -IP$ This specifies the user's IP address which should be passed | ||
- | into Mystic by the telnet server. | + | into Mystic by the telnet server. |
+ | |||
+ | MYSTIC -L This tells Mystic to start in a local login mode. | ||
MYSTIC -N# This specifies a specific node number. | MYSTIC -N# This specifies a specific node number. | ||
Line 27: | Line 39: | ||
| | ||
to only an hour even if they have many hours of time left | to only an hour even if they have many hours of time left | ||
+ | | ||
+ | MYSTIC -TEXT This invokes the built in text editor using the syntax | ||
+ | | ||
+ | open that file otherwise it will create an empty buffer. | ||
| | ||
MYSTIC -TID# This specifies the socket handle when using Mystic with a | MYSTIC -TID# This specifies the socket handle when using Mystic with a | ||
third party telnet server under Windows | third party telnet server under Windows | ||
- | | + | |
MYSTIC -U$ This specifies the username to login to Mystic with and must | MYSTIC -U$ This specifies the username to login to Mystic with and must | ||
be used along side the -P command to supply the password. | be used along side the -P command to supply the password. | ||
Line 73: | Line 89: | ||
protocols. | protocols. | ||
- | Telnet, POP3, SMTP, FTP, NNTP, BINKP, Events | + | TELNET, RLOGIN, SSH, BINKP, FTP, NNTP, POP3, SMTP, Events |
Note that the POP3, SMTP servers are used for Mystic BBS internal ' | Note that the POP3, SMTP servers are used for Mystic BBS internal ' | ||
Line 86: | Line 102: | ||
MYSTIC -CFG | MYSTIC -CFG | ||
- | |||
You can enable/ | You can enable/ | ||
Line 94: | Line 109: | ||
Setting up a telnet BBS is as simple as loading MIS and telnetting in! :) | Setting up a telnet BBS is as simple as loading MIS and telnetting in! :) | ||
- | === IP BLOCKING === | + | === IP BLOCKING |
- | MIS will check your Mystic DATA directory for file named " | + | MIS will check your Mystic DATA directory for file named BLACKLIST.TXT It will use this file to check against the IP addresses of incoming connections. |
- | you would simply add a line into the badip.txt file with that IP address. | + | you would simply add a line into the BLACKLIST.TXT file with that IP address. |
IP blocking supports wildcards too, so for example, you could put 123.123.123.* and block any IP address that begins with 123.123.123. | IP blocking supports wildcards too, so for example, you could put 123.123.123.* and block any IP address that begins with 123.123.123. | ||
Line 105: | Line 120: | ||
If this file does not exist, it will simply print " | If this file does not exist, it will simply print " | ||
- | You can also add a " | + | You can also add a WHITELIST.TXT file the Mystic DATA directory. This file will exempt an IP address from the DNS blacklist, DNS country check, and the auto ban IP systems. |
- | There is currently a developmental MIS2 server also available to play with :) It uses whitelist.txt and blacklist.txt respectively in the Mystic DATA directory. These files work the same way as the MIS counterparts. | + | Entries in both BLACKLIST.TXT and WHITELIST.TXT can contain a mixture of both IPV4 and IPV6 addresses and can contain a single wildcard, using an asterisk to mask an IP range. |
- | + | ||
- | Entries in these lists can contain a mixture of both IPV4 and IPV6 addresses and can contain a single wildcard, using an asterisk to mask an IP range. | + | |
=== DUPLICATE IP CONNECTIONS === | === DUPLICATE IP CONNECTIONS === | ||
Line 121: | Line 134: | ||
=== BUSY NOTIFICATIONS === | === BUSY NOTIFICATIONS === | ||
- | |||
If a connection is made when all of the nodes configured for telnet are being used, MIS will attempt to send them the contents of busy.txt from the Mystic DATA directory. | If a connection is made when all of the nodes configured for telnet are being used, MIS will attempt to send them the contents of busy.txt from the Mystic DATA directory. |
introduction.txt · Last modified: 2023/01/20 03:36 by avon