1. Forum
  2. FidoNet
  3. MYSTIC

  • IP Blocked event

    From Jeff Squires@1:120/457 to All on Thursday, January 28, 2021 16:46:54
    Is it possible for the IP Blocked event (Windows) could create a rule that would block ALL incoming ports? I was using the IP Blocked event as I was getting a ton of port probing and then all off a sudden I was unable to
    access my BBS remotely. I thought my IP provider was blocking the ports but
    it turned out there was a rule created in my WIN10 fire wall rules blocking
    ALL incoming ports/traffic. I deleted the rule and all was good for a day
    then the it happened again. I disabled the IP Blocked event and everything
    has been ok since.

    --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
    * Origin: Communication Connection 1:120/457 (1:120/457)
  • From g00r00@1:129/215 to Jeff Squires on Saturday, January 30, 2021 21:51:00
    Is it possible for the IP Blocked event (Windows) could create a rule
    that would block ALL incoming ports? I was using the IP Blocked event as
    I was getting a ton of port probing and then all off a sudden I was
    unable to access my BBS remotely. I thought my IP provider was blocking the ports but it turned out there was a rule created in my WIN10 fire

    The IP Blocked is an event type that executes a command line whenever an IP is blocked. What it executes is entirely up to you. There is a default event set up for various operating systems that is disabled by default. I am assuming you've enabled this one? If so you can go into the event editor and see exactly the command line that gets executed.

    --- Mystic BBS v1.12 A47 2021/01/29 (Windows/64)
    * Origin: Sector 7 | Mystic WHQ (1:129/215)