• IP Blocking

    From Immortal@21:1/185 to All on Sunday, December 04, 2016 13:13:00
    If someone manages to get their IP banned by mystic, are they permanently banned or is it a temporary ban? I was testing fTelnet last night and managed to get myself banned. Even after removing my IP from blacklist.txt and adding it to whitelist.txt, a few minutes later I got banned again. I shut off the
    IP banning for now. I'm guessing its permanent since my blacklist.txt has
    866 IP addresses in it already after just a few weeks.

    Immortal

    --- Mystic BBS v1.12 A31 (Windows)
    * Origin: Lightning BBS -- lightningbbs.com:2400 (21:1/185)
  • From bcw142@21:1/145.2 to Immortal on Sunday, December 04, 2016 17:53:00
    On 12/04/16, Immortal said the following...
    If someone manages to get their IP banned by mystic, are they permanently banned or is it a temporary ban? I was testing fTelnet last night and managed to get myself banned. Even after removing my IP from blacklist.txt and adding it to whitelist.txt, a few minutes later I got banned again. I shut off the IP banning for now. I'm guessing its permanent since my blacklist.txt has 866 IP addresses in it already
    after just a few weeks.

    Immortal

    I guess you got banned on mis2? I don't use it so I don't have quite that issue. The blacklist & whitelist are for mis2 only, mis using badip.txt and goodip.txt. Perhaps you didn't know that? Add your addresses to the
    goodip.txt and whitelist.txt and the links you rely on (like FSXNET). I have most of the nodes on FSX & RTN nets in my goodip.txt so that doesn't happen.

    --- Mystic BBS v1.12 A31 (Linux)
    * Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)
  • From Immortal@21:1/185 to bcw142 on Sunday, December 04, 2016 19:30:00
    On 12/04/16, bcw142 said the following...

    I guess you got banned on mis2? I don't use it so I don't have quite that issue. The blacklist & whitelist are for mis2 only, mis using badip.txt and goodip.txt. Perhaps you didn't know that? Add your addresses to the goodip.txt and whitelist.txt and the links you rely on (like FSXNET). I have most of the nodes on FSX & RTN nets in my goodip.txt so that
    doesn't happen.

    I have been running MIS, ran MIS2 for a while until I realized it wasn't running the events then switched to MIS. I think it was the BADIP.TXT that I got added to. I'll add myself to GOODIP.TXT, but I think I'll just disable blocking for now. I'm back to just running on my non standard port and not
    on 23. As soon as I opened 23 back up, all 5 nodes were filled almost instantly, I couldn't even log into mystic -cfg. Pretty sad. I've run my
    BBS on port 23 for years and never had such an issue until recently. My old Wildcat system was hard coded to port 23 and had no blocking capabilities at all and it was never a problem. Good thing, with only 2 or 4 nodes it would
    be clogged full of bots 24/7.

    Immortal

    --- Mystic BBS v1.12 A31 (Windows)
    * Origin: Lightning BBS -- lightningbbs.com:2400 (21:1/185)
  • From Vk3jed@21:1/109 to Immortal on Monday, December 05, 2016 16:35:00
    Immortal wrote to bcw142 <=-

    I have been running MIS, ran MIS2 for a while until I realized it

    I run both with no dramas.


    ... But if I kill him, it would start a war.
    --- MultiMail/Win32 v0.49
    * Origin: Freeway BBS - freeway.apana.org.au (21:1/109)
  • From Avon@21:1/101 to Immortal on Monday, December 05, 2016 20:25:00
    On 12/04/16, Immortal pondered and said...

    If someone manages to get their IP banned by mystic, are they permanently banned or is it a temporary ban? I was testing fTelnet last night and

    Permanently until the sysop removes them from badip.txt and blacklist.txt

    Make sure you close and restart your servers to pick up any changes.

    Best, Paul

    --- Mystic BBS v1.12 A31 (Windows)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)
  • From bcw142@21:1/145.2 to Immortal on Monday, December 05, 2016 05:59:00
    On 12/04/16, Immortal said the following...
    I have been running MIS, ran MIS2 for a while until I realized it wasn't running the events then switched to MIS. I think it was the BADIP.TXT that I got added to. I'll add myself to GOODIP.TXT, but I think I'll
    just disable blocking for now. I'm back to just running on my non standard port and not on 23. As soon as I opened 23 back up, all 5
    nodes were filled almost instantly, I couldn't even log into mystic
    -cfg. Pretty sad. I've run my BBS on port 23 for years and never had such an issue until recently. My old Wildcat system was hard coded to port 23 and had no blocking capabilities at all and it was never a problem. Good thing, with only 2 or 4 nodes it would be clogged full of bots 24/7.

    Immortal

    As long as it works for you;) There are a number of measures that can be
    added including firewalls and other front-ends including Mystic. I'm under constant attack, but Mystic is doing OK with that for the most part. I've rarely had a problem getting in by doing it locally (mystic -cfg), they can't get in the SSH port I have opened (non-standard), so I can always get in that way. My data/badip.txt is up to 19990 entries but still seems to be running.

    --- Mystic BBS v1.12 A31 (Linux)
    * Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)
  • From Immortal@21:1/185 to Avon on Monday, December 05, 2016 20:38:00
    On 12/05/16, Avon said the following...
    Permanently until the sysop removes them from badip.txt and blacklist.txt

    Make sure you close and restart your servers to pick up any changes.

    Good to know, thanks.

    Immortal

    --- Mystic BBS v1.12 A31 (Windows)
    * Origin: Lightning BBS -- lightningbbs.com:2400 (21:1/185)