User Tools

Site Tools


introduction

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
introduction [2018/01/03 15:02] – removed mbbsutil references - fully depreciated in 1.12 A37 avonintroduction [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 
 +                 mystic -ansi <filename>. If <filename> is supplied it will
 +                 open that file otherwise it will create an empty buffer.
 +                 
 +                 The ANSI editor can load display files with color codes from 
 +                 PCBoard,Wildcat, Mystic's pipe codes, and ANSI.  The editor 
 +                 can save in ASCII or Pipe Code or ANSI and includes variable 
 +                 line length saving for ANSI files as well as some display 
 +                 options that can be set specifically to Mystic BBS
      
   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.  Ex: -IP125.132.54.741                            +                 into Mystic by the telnet server.  Ex: -IP125.132.54.741 
 +                  
 +  MYSTIC -L      This tells Mystic to start in a local login mode.                           
        
   MYSTIC -N#     This specifies a specific node number.  There is usually   MYSTIC -N#     This specifies a specific node number.  There is usually
Line 27: Line 39:
                  permitted to use this session.  Ex: -T60 limits the user                  permitted to use this session.  Ex: -T60 limits the user
                  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 
 +                 mystic -text <filename>. If <filename> is supplied it will
 +                 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.  If                  be used along side the -P command to supply the password.  If
Line 73: Line 89:
 protocols.  It can support one or all of the following: protocols.  It can support one or all of the following:
  
-TelnetPOP3SMTP, FTP, NNTP, BINKP, Events+TELNETRLOGINSSH, BINKP, FTP, NNTP, POP3, SMTP, Events
  
 Note that the POP3, SMTP servers are used for Mystic BBS internal 'Email' only at this time. The Events system is used by Mystic to call other programs based on time of day or as semaphores are created that trigger events such as importing echomail and/or netmail. Note that the POP3, SMTP servers are used for Mystic BBS internal 'Email' only at this time. The Events system is used by Mystic to call other programs based on time of day or as semaphores are created that trigger events such as importing echomail and/or netmail.
Line 86: Line 102:
  
   MYSTIC -CFG   MYSTIC -CFG
- 
  
 You can enable/disable different server types, change their listening ports, and some other options. You can enable/disable different server types, change their listening ports, and some other options.
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 + EXCEPTIONS ===
  
-MIS will check your Mystic DATA directory for file named "badip.txt". It will use this file to check against the IP addresses of incoming connections.  For example, if you wanted to block 123.123.123.123 +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.  For example, if you wanted to block 123.123.123.123 
-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 "BLOCKED" to the connection's terminal and disconnect them. If this file does not exist, it will simply print "BLOCKED" to the connection's terminal and disconnect them.
  
-You can also add a "goodip.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.  The format of the file is the same as "badip.txt". If you know of certain IP addresses you never want to see auto banned on your system - "goodip.txt" is a great way to ensure that never happens!+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.  The format of the file is the same as BLACKLIST.TXT. If you know of certain IP addresses you never want to see auto banned on your system - WHITELIST.TXT is a great way to ensure that never happens!
  
-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.  For example "127.*" would block any IPV4 address that begins with "127." IPV6 works in the same way, expand the IPV6 address up to the point where you want to wildcard it, such as "014f:*"
- +
-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.  For example "127.*" would block any IPV4 address that begins with "127." IPV6 works in the same way, expand the IPV6 address up to the point where you want to wildcard it, such as "014f:*"+
  
 === 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 this file does not exist, it will simply 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 this file does not exist, it will simply
introduction.txt · Last modified: 2023/01/20 03:36 by avon

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki