• BadIP

    From Ben Ritchey@1:393/75 to G00r00 on Sun Jun 25 00:24:31 2017
    Hi G00r00,

    Maybe it would help if MIS compared the domain/IP addy with the defined nodes and skipped BadIP if a match is made?


    .- Keep the faith, --------------------------------------------------.
    | |
    | Ben aka cMech Web: http|ftp|binkp|telnet://cmech.dynip.com |
    | Email: fido4cmech(at)lusfiber.net |
    | Home page: http://cmech.dynip.com/homepage/ | `----------- WildCat! Board 24/7 +1-337-984-4794 any BAUD 8,N,1 ---'

    ... How did this ugly woman get in my bed?
    --- GoldED+/LNX v1.1.5-b20170303 ... via Mystic BBS!
    * Origin: FIDONet - The Positronium Repository (1:393/75)
  • From Ben Ritchey@1:393/75 to G00r00 on Sun Jun 25 00:28:22 2017
    Hi G00r00,

    Maybe it would help if MIS compared the domain/IP addy with the defined nodes and skipped BadIP if a match is made? I've had nodes added when they shouldn't myself :)


    .- Keep the faith, --------------------------------------------------.
    | |
    | Ben aka cMech Web: http|ftp|binkp|telnet://cmech.dynip.com |
    | Email: fido4cmech(at)lusfiber.net |
    | Home page: http://cmech.dynip.com/homepage/ | `----------- WildCat! Board 24/7 +1-337-984-4794 any BAUD 8,N,1 ---'

    ... How did this ugly woman get in my bed?
    --- GoldED+/LNX v1.1.5-b20170303 ... via Mystic BBS!
    * Origin: FIDONet - The Positronium Repository (1:393/75)
  • From g00r00@1:129/215 to Ben Ritchey on Sun Jun 25 10:47:19 2017
    Hi G00r00,

    Maybe it would help if MIS compared the domain/IP addy with the defined nodes and skipped BadIP if a match is made?

    MIS probably isn't going to have any/much more work done to it, but MIS2 already provides a solution for this.

    In MIS2 you can define the IP banning separately per server. You can set the settings to be very non-aggressive or just disable auto IP banning entirely for BINKP. In MIS it was "all or nothing" for all servers, which was a design mistake on my part that led of this.

    What you suggest is a tricky because IP blocking works in a way that Mystic would never talk to the client in order to do the BINKP handshake and get the client address and password (in order to perform the exempt check).

    The real solution is to use MIS2 and manage the auto ban setting independently from the other servers. MIS2 is the future and MIS is going away.

    --- Mystic BBS v1.12 A35 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)
  • From Ben Ritchey@1:393/75 to G00r00 on Sun Jun 25 11:20:37 2017
    * An ongoing debate between g00r00 and Ben Ritchey rages on ...

    In MIS2 you can define the IP banning separately per server. You can
    set the settings to be very non-aggressive or just disable auto IP
    banning entirely for BINKP. In MIS it was "all or nothing" for all servers, which was a design mistake on my part that led of this.

    Cool, works for me!


    .- Keep the faith, --------------------------------------------------.
    | |
    | Ben aka cMech Web: http|ftp|binkp|telnet://cmech.dynip.com |
    | Email: fido4cmech(at)lusfiber.net |
    | Home page: http://cmech.dynip.com/homepage/ | `----------- WildCat! Board 24/7 +1-337-984-4794 any BAUD 8,N,1 ---'

    ... Spring is always a new beginning.
    --- GoldED+/LNX v1.1.5-b20170303 ... via Mystic BBS!
    * Origin: FIDONet - The Positronium Repository (1:393/75)