TZUTC: -0400   
   MSGID: 1104.binkd@1:2320/105 250bb31a   
   REPLY: 2:5030/1997@fidonet 60a62a61   
   PID: Synchronet 3.18c-Linux master/dcb003099 Dec 31 2020 GCC 7.5.0   
   TID: SBBSecho 3.12-Linux master/dcb003099 Dec 31 2020 GCC 7.5.0   
   BBSID: CAPCITY2   
   CHRS: ASCII 1   
   > By the way, binkd can handle multiple connections simultaneously, so I can't   
   r   
   > lly imagine how a single node can cause DoS by polling your system every 2   
   min   
   > es.   
      
   The issue is that the polling node is using the test node number, /999,   
   instead of an assigned number.  Anyone else who is trying to test a new   
   connection, who does not somehow manage to get their polls all done in the   
   2-minute window, will have whatever response messages they were looking for   
   picked up by the offending node.   
      
   Paul -- if nothing else, maybe you could set up a second/new test node,   
   like /9999, to allow others to test?   
      
   Mike   
      
      
    * SLMR 2.1a * I idiot-proof my programs, but along comes a bigger idiot   
   --- SBBSecho 3.12-Linux   
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)   
   SEEN-BY: 1/123 90/1 103/705 105/81 114/709 120/340 457 616 123/10   
   SEEN-BY: 123/131 124/5016 129/215 305 154/10 30 40 50 700 203/0 220/50   
   SEEN-BY: 220/80 90 221/0 6 226/30 227/114 201 229/100 101 200 310   
   SEEN-BY: 229/424 426 550 664 700 720 1016 1017 240/5832 249/109 110   
   SEEN-BY: 249/206 307 317 280/464 5003 5555 282/1038 288/100 292/854   
   SEEN-BY: 292/8125 301/1 310/31 317/3 322/757 342/200 396/45 423/120   
   SEEN-BY: 460/58 633/280 712/848 770/1 2320/0 105 195 304 2452/250   
   SEEN-BY: 3634/12   
   PATH: 2320/105 154/10 280/464 229/101 426