Hello everyone - I ran my BBS with Mystic software for a couple of years and then for some reason I got bored with it and switched to Synchronet. After using Synchronet for a while, I began to appreciate Mystic more and more. For me, Synchronet has way too much crap on it and it is difficult to customize. With Mystic, it's easy t create new menus, put any command you want on them, and just customize the heck out of your BBS.
I am going to be sticking with Mystic now. The only thing I don't like is the difficulty I have finding doors that will work with a 64-bit computer, I want to have lots of fun games to play, so to solve this problem, I joined Doorparty. If you're not familiar with it, Doorparty is a free gaming network put together at Throwback BBS. With just a little bit of effort, you can connect your BBS to Doorparty and instantly have access to dozens of cool games. It's great and I highly recommend it. For info and instructions, go to: http://throwbackbbs.com
Hello everyone - I ran my BBS with Mystic software for a couple of years and then for some reason I got bored with it and switched to Synchronet. After using Synchronet for a while, I began to appreciate Mystic more
and more. For me, Synchronet has way too much crap on it and it is difficult to customize. With Mystic, it's easy t create new menus, put
any command you want on them, and just customize the heck out of your
BBS.
Hello everyone - I ran my BBS with Mystic software for a couple of years and then for some reason I got bored with it and switched to Synchronet. After using Synchronet for a while, I began to appreciate Mystic more
and more. For me, Synchronet has way too much crap on it and it is difficult to customize. With Mystic, it's easy t create new menus, put
any command you want on them, and just customize the heck out of your
BBS.
I am going to be sticking with Mystic now. The only thing I don't like
is the difficulty I have finding doors that will work with a 64-bit computer, I want to have lots of fun games to play, so to solve this problem, I joined Doorparty. If you're not familiar with it, Doorparty
is a free gaming network put together at Throwback BBS. With just a
little bit of effort, you can connect your BBS to Doorparty and
instantly have access to dozens of cool games. It's great and I highly recommend it. For info and instructions, go to: http://throwbackbbs.com
Still, I genuinely miss running my board on SBBS but, well, that's just how things go sometimes. Gotta pick my battles. The focus now is getting around to making those custom menu's and then promoting this place.
Maybe I'll move back to SBBS in the future -- who knows. For now I'm
just going with where the mystic winds take me...
Nothing says you can't run 2 boards, 1 on SBBS andone on Mystic. I didI've heavily consi
Bucko wrote to Kurisu <=-
Nothing says you can't run 2 boards, 1 on SBBS and one on Mystic. I did that for a couple of years, and also had an Enigma board too... All
done in VM's.. SBBS allows for a lot of stuff that can be brought over
to the Mystic board. I have been considering modifying a SBBS to have a main menu of IRC, InterBBS chat, and whatever else fancies me at the
Huh.. you may have helped inspire yet another crazy idea. Like I need any more of those :D
It's your vision as the Sysop that ultimately determines how your board looks and feels. If having to use another BBS as a doorway to offer
users a better experience, go for it!
I even went as far as using Mystic as a Front end
to my C64 board I was using the bot checker to help with
a bot issue I was having. That is until I figured out
the C64 doesn't have a esc key!! LOL It sure worked
though...
I am curious about other peoples' experiences dealing with bots and what has worked and what hasn't worked. If I understand the Mystic bot checker, it requires callers to press a specific key (usually Esc)
within some time after connecting, and before presenting the login
prompt - is this correct?
I am curious about other peoples' experiences dealing with bots and w has worked and what hasn't worked. If I understand the Mystic bot checker, it requires callers to press a specific key (usually Esc) within some time after connecting, and before presenting the login prompt - is this correct?
So I'm relatively new to the construction and maintenance of a BBS
system. I've been up and down a few times with my mystic setup and I to see the gate crashers getting banned too. I ended up setting the auto IP to some lower numbers and definitely use the human check via button sequence if you pass that gate.
99% of the actual traffic on my system is me... But remove SYSOP
tinkering and it quickly becomes the ravenous bot army.
I bet that did a heck of a job of quieting things down! :)
Have you tried other solutions for bot connections? I have been running
a 'telnet ringdown server' that I wrote to accept connections on one
port and pass them off to any open port from a list (each node of my BBS listens on a different port). Immediately it was apparent that some protection against portscanning bots was needed, so I have implemented a check for malicious login attempts that triggers a temporary IP ban, and it has helped.
I am curious about other peoples' experiences dealing with bots and what has worked and what hasn't worked. If I understand the Mystic bot checker, it requires callers to press a specific key (usually Esc)
within some time after connecting, and before presenting the login
prompt - is this correct?
Actually, a friend of mine wrote a bot checker for me.
Currently it is very rudementary, where all you do is
hit // to get past it, but the final version will allow
a LOT of different things to go on with the Image BBS
for the 64.. InterBBS chatting is one thing, live
weather updates, this all on a 1 line/modem computer. It
is a full "modem"/front end for the C64. It's gonna be
really hot for the Image BBS..
As I said in a previous post, the Mystic bot checker works great. About 2 years ago just about all of the C-Net Amiga BBS sysOp's
were being attacked non stop (why I have no idea!) I got connected to over 1500 times in a 10 hour period, all 10 lines of my board
were non stop answering and hanging up. One of the
sysOp's wrote a mpl to allow Mystic to connect, run the
bot check and immediately transfer to the C-Net (this
was the set up I used for my Image board) and it helped
tremendously. Then we got the offending IP address and
found out it was the same IP attacking 3 different
boards at the same time, we all blocked it and the issue went away..
yeah i made it so i log in silently .. kinda feel bad for my one daily caller because my last callers screen is usually just a wall of his nickname :)
Using Mystic ACS codes, you can also set it up for you that only your first connection of the day is logged. :P
Using Mystic ACS codes, you can also set it up for you that only your first connection of the day is logged. :P
Oh, I'll have to look into that.
I am curious about other peoples' experiences dealing with bots and w has worked and what hasn't worked. If I understand the Mystic bot checker, it requires callers to press a specific key (usually Esc) within some time after connecting, and before presenting the login
Sounds very interesting, the extra features sound awesome. Looking forward to hearing more!
The bots sure are tenacious! I have been logging attempts to connect,
to see the default credentials being tested, and use these as keywords
to identify bots - for example, if someone connects and the first thing they type is 'root' - that's a bot. That triggers a temporary IP ban (which extends in duration each time it is triggered), which has worked well.
In the past couple weeks, 42 different times the IP 190.211.255.106 connected to me and was banned. The same IP connected another 141 times while banned.
5 different times the IP 153.0.123.152 connected to me and was banned. The same IP connected another 1248 times while banned!
I've had 2345 unique IPs trigger bans in the past month or so. It's at least kinda interesting to study. :)
Chris/akacastor
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,052 |
Nodes: | 17 (0 / 17) |
Uptime: | 06:58:09 |
Calls: | 501,013 |
Files: | 109,383 |
D/L today: |
70 files (4,360K bytes) |
Messages: | 304,696 |