Nп/п : 25 из 100
От : Wilfred van Velzen 2:280/464 17 ноя 26 22:31:40
К : Alexey Matrosov 17 ноя 26 00:41:02
Тема : Re: Blacklisting systems
----------------------------------------------------------------------------------
@TID: FMail-lnx64 2.3.4.1-B20260520
@RFC-X-No-Archive: Yes
@TZUTC: 0100
@CHRS: CP866 2
@PID: GED+LNX 2.0.0-b20260928
@MSGID: 2:280/464 6afcc97b
@REPLY: 2:203/910 6afcc3e3
Hi Alexey,
On 2026-11-17 21:57:44, you wrote to me:
WV>>>> (from 77:77/77@FTNStats, failed, S/R: 0/0 (0/0 bytes))
AM>>> The thing is the owner of that polling script doesn`t look like a
AM>>> real FTN sysop.
WV>> You can`t really tell anything from the logs who the owner is. But
WV>> since he is playing with Fidonet technology, I think it`s much more
WV>> likely someone involved with Fidonet, then not.
AM> Yeah, that could be someone familiar with FTN. But what`s the purpose of
AM> such
AM> polls?..
Well it could be something like Dimitry is doing (but not published yet).
Dimitry is giving back the data to Fidonet in a nice form on his website. ;-)
AM>>> It is better to be prepared and check one more time if our
AM>>> systems are ready for those kind of scenarios.
WV>> What kind of scenarios are you talking about?
AM> What I meant was that it might be a good idea to double check whether we
AM> are
AM> taking proper care of our unprotected inbound for instance ;)
On most systems that is not processed automatically...
AM>>> binkp/1.0 05 Oct 26 01:49:33 binkp[279306]: time: 23:48:33,
AM>>> unknown
WV>> Not the same time as your log lines, off by two hours (UTC?), and 1
WV>> minute. So one of yours clocks is not synchronized to the internet.
AM> No, that`s the the correct clock on my server`s side, I have CET which is
AM> UTC+1 now.
And early October you were on UTC+2, so the other side probably was displaying
UTC time.
AM> The clock is in sync with the internet time.
So the other side is not in sync, because of the 1 minute time difference.
WV>> I checked my logs, but there are no connections from a 94.19.*
WV>> address, nor is there "binkd-go" in my logs for the this year. So
WV>> this doesn`t seem to have been a fido wide probe. ;-)
AM> Yep, I also had only one incoming connection from that ip.
AM> But that doesn`t mean anything, since the previous example has a series of
AM> calls done from the 77:77/77 actually comes from a different ip each time
AM> (dynamic?).
+ 16 Nov 04:31:38 [15159] incoming session with
customer.lndngbr1.isp.starlink.com [9.246.113.252]
Starlink: That`s satelite connections from Elon Musks company. So very likely
dynamic.
Bye, Wilfred.
--- FMail-lnx64 2.3.4.1-B20260520
* Origin: FMail development HQ (2:280/464)
SEEN-BY: 103/705 124/5016 153/757 154/10 30 203/0 221/0 1 240/1120 5832 263/1
SEEN-BY: 280/464 1043 5003 5006 5555 292/854 8125 301/1 310/31 341/66 234
SEEN-BY: 396/45 423/120 460/58 469/122 550/278 633/280 712/848 770/1 5001/100
SEEN-BY: 5015/46 5020/290 715 806 921 1146 4441 9696 5023/24 5030/1081 1997
SEEN-BY: 5034/13 5051/44 5057/19
@PATH: 280/464 5001/100 5020/715