• Blacklisting systems

    From Nick Andre@1:229/426 to All on Monday, November 16, 2026 18:15:45
    Certain systems have taken it upon themselves to rectally probe my system, often using unique IP addresses or AI cloud nonsense... because "they can".

    Can a feature be added to BinkD to blacklist/drop/refuse systems from connecting? ie. A simple text file containing the FTN addresses.

    A simple yes/no answer will suffice... willing to do Paypal $$ if the former.

    Nick

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Nigel Reed@1:124/5016 to Nick Andre on Monday, November 16, 2026 22:59:46
    On Mon, 16 Nov 2026 18:15:45 +0000
    "Nick Andre" (1:229/426) <Nick.Andre@f426.n229.z1.fidonet> wrote:

    Certain systems have taken it upon themselves to rectally probe my
    system, often using unique IP addresses or AI cloud nonsense...
    because "they can".

    Can a feature be added to BinkD to blacklist/drop/refuse systems from connecting? ie. A simple text file containing the FTN addresses.

    A simple yes/no answer will suffice... willing to do Paypal $$ if the
    former.

    Short, simple answer. Probably not but you could...

    1. Stop all incoming connections and only connect to outgoing
    connections to pick up mail.

    2. Resolve the IPs of all the servers in the nodelist and use iptables
    or similar firewall to let those through and block everything else.
    This is a problem with dynamic IPs so you'd have to refresh at regular intervals.

    3. Who cares? What will they get? binkd header and nothing else because
    they cannot authenticate, so it ties up a port, you've got 65000 of
    them.

    4. Write a script to parse your log, pull out ips that don't connect
    and use a timed ipset to block them for a week or two, or the entire
    subnet.


    5. Write a perl hook to only let through servers you want to allow in.

    With all that said, you're still going to have people connecting to the sockets, it's just the different ways to deny them either beforehand
    via iptables or some other firewall, or after the fact with
    configurations that would eventually get denied anyway due to them not
    being in the list of nodes.
    --
    End Of The Line BBS - Plano, TX
    telnet endofthelinebbs.com 23
    --- SBBSecho 3.38-Linux
    * Origin: End Of The Line BBS - endofthelinebbs.com (1:124/5016)
  • From Nigel Reed@1:124/5016 to Nick Andre on Tuesday, November 17, 2026 11:08:36
    On Tue, 17 Nov 2026 06:59:01 +0000
    "Nick Andre" (1:229/426) <Nick.Andre@f426.n229.z1.fidonet> wrote:


    20261117 03:30:21 [56428] incoming from 192.42.116.16 (34424)

    20261117 03:34:05 [6392] incoming session with 143.20.185.77

    bbs@bbs:~/sbbs-git$ host 192.42.116.16
    16.116.42.192.in-addr.arpa domain name pointer tor-exit.hartvoorinternetvrijheid.nl.
    bbs@bbs:~/sbbs-git$ host 143.20.185.77
    77.185.20.143.in-addr.arpa domain name pointer exitnode.eu.

    Both the IPs are tor exit nodes. Maybe run the ips through a lookup and
    find common names for exit nodes and blacklist those in your firewall.
    --
    End Of The Line BBS - Plano, TX
    telnet endofthelinebbs.com 23
    --- SBBSecho 3.38-Linux
    * Origin: End Of The Line BBS - endofthelinebbs.com (1:124/5016)
  • From Nigel Reed@1:124/5016 to Wilfred van Velzen on Tuesday, November 17, 2026 12:13:01
    Re: Re: Blacklisting systems
    By: Wilfred van Velzen to Alexey Matrosov on Tue Nov 17 2026 18:22:34

    addr: 77:2/110@scinet

    This shut down yonks ago.
    --- SBBSecho 3.38-Linux
    * Origin: End Of The Line BBS - endofthelinebbs.com (1:124/5016)
  • From Nigel Reed@1:124/5016 to Wilfred van Velzen on Tuesday, November 17, 2026 13:41:37
    On Tue, 17 Nov 2026 19:36:20 +0100
    "Wilfred van Velzen" (2:280/464)
    <Wilfred.van.Velzen@f464.n280.z2.fidonet> wrote:

    Hi Nigel,

    On 2026-11-17 12:13:01, you wrote to me:

    addr: 77:2/110@scinet

    This shut down yonks ago.

    So somebody forgot to tell the nodes? ;-)

    But thanks, I'll forward the message to my link.

    Dion shut it down in August 2022. You'd think they'd have noticed..oh,
    maybe not. :) There were several posts in SCISYSOP so they should have
    known about it.
    --
    End Of The Line BBS - Plano, TX
    telnet endofthelinebbs.com 23
    --- SBBSecho 3.38-Linux
    * Origin: End Of The Line BBS - endofthelinebbs.com (1:124/5016)
  • From Nigel Reed@1:124/5016 to Wilfred van Velzen on Tuesday, November 17, 2026 15:28:03
    On Tue, 17 Nov 2026 18:22:34 +0100
    "Wilfred van Velzen" (2:280/464)
    <Wilfred.van.Velzen@f464.n280.z2.fidonet> wrote:


    + 16 Nov 04:31:38 [15159] incoming session with customer.lndngbr1.isp.starlink.com [9.246.113.252]

    I must admit, I never checked because I don't really care. That said, I
    did check out of curiosity and have a number of connections for 77:77
    and they're all from starlink.com IPs. I was going to suggest blocking
    their /16 but the address ranges I see are all 145.224.0.0/16 so I
    guess that's not going to work.
    --
    End Of The Line BBS - Plano, TX
    telnet endofthelinebbs.com 23
    --- SBBSecho 3.38-Linux
    * Origin: End Of The Line BBS - endofthelinebbs.com (1:124/5016)
  • From Nick Andre@1:229/426 to Nigel Reed on Tuesday, November 17, 2026 06:59:01
    On 16 Nov 26 22:59:46, Nigel Reed said the following to Nick Andre:

    A simple yes/no answer will suffice... willing to do Paypal $$ if the
    former.

    Short, simple answer. Probably not but you could...

    The problem is that a dipshit has taken it upon himself to write an AI process that polls here using a bogus FTN address, with either nonexistant zone 5, 6 or a Net number greater than the highest Net-number in Fidonet.

    Two examples:

    20261117 03:30:21 [56428] incoming from 192.42.116.16 (34424)
    20261117 03:30:21 [19992] incoming session with 192.42.116.16
    20261117 03:30:21 [19992] SYS Hobbs-Barnett
    20261117 03:30:21 [19992] ZYZ Jacqueline Parker
    20261117 03:30:21 [19992] LOC South Todd
    20261117 03:30:21 [19992] NDL 115200,TCP,BINKP
    20261117 03:30:21 [19992] TIME Tue, 17 Nov 2026 08:30:28 +0000
    20261117 03:30:21 [19992] VER binkd/1.1a-115/Linux binkp/1.1
    20261117 03:30:21 [19992] addr: 5:29425/23919@fidonet

    20261117 03:34:05 [6392] incoming session with 143.20.185.77
    20261117 03:34:05 [6392] SYS Alvarez, Mccormick and Anderson
    20261117 03:34:05 [6392] ZYZ Richard Hill
    20261117 03:34:05 [6392] LOC Port Caitlinmouth
    20261117 03:34:05 [6392] NDL 115200,TCP,BINKP
    20261117 03:34:05 [6392] TIME Tue, 17 Nov 2026 08:34:11 +0000
    20261117 03:34:05 [6392] VER binkd/1.1a-115/Linux binkp/1.1
    20261117 03:34:05 [6392] addr: 5:29108/27673@fidonet

    The poll session completes because theres nothing to exchange, okay great, but it would be nice if BinKD could just drop the bogus session entirely based on my criteria or regex.

    In the meantime I wrote my own process to auto-shitlist these entries, a bit convoluted but working.

    Nick

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Mike Powell@1:2320/107 to Nick Andre on Tuesday, November 17, 2026 15:34:50
    On 16 Nov 26 22:59:46, Nigel Reed said the following to Nick
    Andre:

    A simple yes/no answer will suffice... willing to do Paypal
    $$ if the former.

    Short, simple answer. Probably not but you could...

    The problem is that a dipshit has taken it upon himself to
    write an AI process that polls here using a bogus FTN address,
    with either nonexistant zone 5, 6 or a Net number greater than
    the highest Net-number in Fidonet.


    I was thinking it was the typical connect and hang up nonsense, like the port scanners do. Whoever this is knows what they are doing, i.e. connecting to a binkd server. What I wonder is who has time to do this, even if it is AI generated. What a bunch of crap.

    Mike

    --- ScorpioWeb v0.39a (Linux/x86_64)
    * Origin: capitolcityonline.net * KY, USA (1:2320/107)
  • From Nick Andre@1:229/426 to Mike Powell on Tuesday, November 17, 2026 11:59:36
    On 17 Nov 26 15:34:50, Mike Powell said the following to Nick Andre:

    I was thinking it was the typical connect and hang up nonsense, like the po scanners do. Whoever this is knows what they are doing, i.e. connecting to binkd server. What I wonder is who has time to do this, even if it is AI generated. What a bunch of crap.

    There are a couple of characters I suspect, but can't prove it.

    Nick

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Alexey Matrosov@2:203/910 to Nick Andre on Tuesday, November 17, 2026 17:46:17
    Hello Nick,

    Tuesday November 17 2026 06:59, you wrote to Nigel Reed:

    The problem is that a dipshit has taken it upon himself to write an AI process that polls here using a bogus FTN address, with either
    nonexistant zone 5, 6 or a Net number greater than the highest
    Net-number in Fidonet.

    The poll session completes because theres nothing to exchange, okay
    great, but it would be nice if BinKD could just drop the bogus session entirely based on my criteria or regex.

    In the meantime I wrote my own process to auto-shitlist these entries,
    a bit convoluted but working.

    Nowadays there are some bots polling your system from a weird addresses without a good reason.
    In my case I'm getting those sort of calls from 77:77/77 once per week or so. To eliminate this kind of annoyances I've implemented a listed detection and conditional abortsession in qico.

    And then I have this condition in my qico config:

    "if address 77:77/* : abortsession Session refused"

    Or you can simply restrict all sessions with non-listed systems based on the nodelist, and apply an exclusion to allow only some of those unlisted you are familiar with:

    "if (!listed) & (!address 2:5001/100.5001) : abortsession Not listed"

    Something like that could also be implemented to binkd.
    But it is also a great idea to implement a regex conditions.

    = fidonews (2:203/910) ========================================================
    Msg : 248 of 282 Snt Loc Scn
    From : Alexey Matrosov 2:203/910 25 Oct 26 15:30:26
    To : All
    Subj : qico 0.60.3 =============================================================================== * Originally in enet.sysop
    * Crossposted in fido_sysop

    Hej All,

    qico 0.60.3 is out.

    qcc works with NetBSD's own curses again.

    qcc can also show the session history the daemon writes to the binlog.
    Pass the binlog path when you start qcc.

    Two new config words. 'listedfrom' chooses where a node counts as listed:
    the nodelist, a password or subst line, or either.
    'abortsession', inside if, ends the session after the handshake and before
    any files, and gives a reason. In an if, use them for a listed-only
    policy, or when a particular address should get no session.

    See 'Changes' for the full notes.

    Code and changelog: https://github.com/glasslike/qico

    Mvh,
    Alex.

    --- .-. .- -... .- .-. -... . .-.
    * Origin: Rabarber > Skelleftea > Sweden (2:203/910)

    ==== End golded_out.txt ====


    Mvh,
    Alex.

    --- .-. .- -... .- .-. -... . .-.
    * Origin: Rabarber > Skelleftea > Sweden (2:203/910)
  • From Nick Andre@1:229/426 to Nigel Reed on Tuesday, November 17, 2026 12:40:04
    On 17 Nov 26 11:08:36, Nigel Reed said the following to Nick Andre:

    Both the IPs are tor exit nodes. Maybe run the ips through a lookup and find common names for exit nodes and blacklist those in your firewall.

    Thanks, I've added two additional Tor exit-node blacklists to my firewall.

    Nick

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Wilfred van Velzen@2:280/464 to Alexey Matrosov on Tuesday, November 17, 2026 18:22:34
    Hi Alexey,

    On 2026-11-17 17:46:17, you wrote to Nick Andre:

    Nowadays there are some bots polling your system from a weird
    addresses without a good reason. In my case I'm getting those sort of calls from 77:77/77 once per week or so.

    I get those too:

    + 16 Nov 04:31:38 [15159] incoming session with customer.lndngbr1.isp.starlink.com [9.246.113.252]
    - 16 Nov 04:31:38 [15159] SYS FTNStats Census
    - 16 Nov 04:31:38 [15159] ZYZ FTNStats Robot
    - 16 Nov 04:31:38 [15159] LOC Internet
    - 16 Nov 04:31:38 [15159] VER ftn-stats/0.1.0 binkp/1.1
    + 16 Nov 04:31:38 [15159] addr: 77:77/77@FTNStats (n/a or busy)
    ? 16 Nov 04:31:38 [15159] no AKAs in common domains or all AKAs are busy
    + 16 Nov 04:31:38 [15159] done (from 77:77/77@FTNStats, failed, S/R: 0/0 (0/0 bytes))
    16 Nov 04:31:38 [15159] session closed, quitting...

    To eliminate this kind of annoyances I've implemented a listed
    detection and conditional abortsession in qico.

    I'm not annoyed by them, because it's so infrequent. But it would be more respectful to the systems they poll, if they used their real SYS, ZYZ and fido address, like Dimitry does for his scanning:

    + 14 Nov 08:23:06 [28635] incoming session with 2603:c020:c00f:4d7e:0:7dac:811f:801
    - 14 Nov 08:23:06 [28635] SYS nodelist.fidonet.cc
    - 14 Nov 08:23:06 [28635] ZYZ Dmitry Protasoff
    - 14 Nov 08:23:06 [28635] LOC London, UK
    - 14 Nov 08:23:06 [28635] VER NodelistDB/1.0 binkp/1.1
    - 14 Nov 08:23:06 [28635] TIME 14 Nov 26 07:23 UTC
    + 14 Nov 08:23:06 [28635] addr: 2:5001/100.5001@fidonet
    + 14 Nov 08:23:06 [28635] done (from 2:5001/100.5001@fidonet, OK, S/R: 0/0 (0/0 bytes))
    14 Nov 08:23:06 [28635] session closed, quitting...

    Btw: Net 77 is already in use by some real nets. I see these in my logs:

    addr: 77:2/110@scinet
    addr: 77:3/81@ultranet

    And on https://docs.google.com/spreadsheets/d/17pmf7cS9ocU99Rm6qlJD_OncqmbDI5Qj8Yw99A5bgVc/edit?gid=0#gid=0
    I see even more:

    77 Tanguito
    77 SpectroNet
    77 LCRNet
    77 LifeNet


    Bye, Wilfred.

    --- FMail-lnx64 2.3.4.1-B20260520
    * Origin: FMail development HQ (2:280/464)
  • From Alexey Matrosov@2:203/910 to Wilfred van Velzen on Tuesday, November 17, 2026 19:02:21
    Hello Wilfred,

    Tuesday November 17 2026 18:22, you wrote to me:

    Nowadays there are some bots polling your system from a weird
    addresses without a good reason. In my case I'm getting those
    sort of calls from 77:77/77 once per week or so.

    I get those too:
    (from 77:77/77@FTNStats, failed, S/R: 0/0 (0/0 bytes))

    To eliminate this kind of annoyances I've implemented a listed
    detection and conditional abortsession in qico.
    I'm not annoyed by them, because it's so infrequent. But it would be
    more respectful to the systems they poll, if they used their real SYS,
    ZYZ and fido address, like Dimitry does for his scanning:

    Btw: Net 77 is already in use by some real nets. I see these in my
    logs:
    addr: 77:2/110@scinet
    addr: 77:3/81@ultranet

    The thing is the owner of that polling script doesn't look like a real FTN sysop. So, the reason of those polls is blurry to me.
    It is better to be prepared and check one more time if our systems are ready for those kind of scenarios.
    There is another example, a couple of month ago I got a call with FREQ from unlisted system pretending to be my point:

    05 Oct 26 01:49:33 binkp[279306]: answering incoming call
    05 Oct 26 01:49:33 binkp[279306]: remote is 94.19.123.34
    05 Oct 26 01:49:33 binkp[279306]: starting inbound Binkp session
    05 Oct 26 01:49:33 binkp[279306]: Binkp: got unknown NUL: "OPT"
    05 Oct 26 01:49:33 binkp[279306]: address: 2:203/910.9999@fidonet
    05 Oct 26 01:49:33 binkp[279306]: system: binkd-go livetest
    05 Oct 26 01:49:33 binkp[279306]: from: livetest
    05 Oct 26 01:49:33 binkp[279306]: sysop: livetest
    05 Oct 26 01:49:33 binkp[279306]: phone: -Unpublished-
    05 Oct 26 01:49:33 binkp[279306]: flags: [115200] (null)
    05 Oct 26 01:49:33 binkp[279306]: mailer: binkd/1.1a-115/Unix binkp/1.0
    05 Oct 26 01:49:33 binkp[279306]: time: 23:48:33, unknown
    05 Oct 26 01:49:33 binkp[279306]: we have: 0b mail, 0b files
    05 Oct 26 01:49:33 binkp[279306]: options: Binkp/Plain
    05 Oct 26 01:49:33 binkp[279306]: start recv: 49bc92b7.req, 0 bytes, estimated time 00:00:01
    05 Oct 26 01:49:33 binkp[279306]: rcvd: 49bc92b7.req, 0 bytes, 0 cps [ok]
    05 Oct 26 01:49:33 binkp[279306]: executing '(null) /tmp/qsrif.4430a'
    05 Oct 26 01:49:33 binkp[279306]: exec '(null) /tmp/qsrif.4430a' returned rc=512
    05 Oct 26 01:49:33 binkp[279306]: can't open '/tmp/qfls.4430a' for reading
    05 Oct 26 01:49:33 binkp[279306]: total: 0:00:00 online, 0b sent, 0b received 05 Oct 26 01:49:33 binkp[279306]: session with 2:203/910.9999 successful [ok] 05 Oct 26 01:49:33 binkp[279306]: exiting with rc=0

    Mvh,
    Alex.

    --- .-. .- -... .- .-. -... . .-.
    * Origin: Rabarber > Skelleftea > Sweden (2:203/910)
  • From Wilfred van Velzen@2:280/464 to Nigel Reed on Tuesday, November 17, 2026 19:36:20
    Hi Nigel,

    On 2026-11-17 12:13:01, you wrote to me:

    addr: 77:2/110@scinet

    This shut down yonks ago.

    So somebody forgot to tell the nodes? ;-)

    But thanks, I'll forward the message to my link.


    Bye, Wilfred.

    --- FMail-lnx64 2.3.4.1-B20260520
    * Origin: FMail development HQ (2:280/464)
  • From Tommi Koivula@2:221/1 to Alexey Matrosov on Tuesday, November 17, 2026 21:01:56
    Hi Alexey.

    17 Nov 26 17:46, you wrote to Nick Andre:

    Nowadays there are some bots polling your system from a weird addresses without
    a good reason. In my case I'm getting those sort of calls from 77:77/77 once
    per week or so. To eliminate this kind of annoyances I've implemented a listed
    detection and conditional abortsession in qico.

    I see those probes from 77:77/77 too. Not really a problem, but I've set up a session password for it :D

    === Cut ===
    16 Nov 26 05:31:34 binkp[626463]: answering incoming call
    16 Nov 26 05:31:34 binkp[626463]: remote is 9.246.113.252
    16 Nov 26 05:31:34 binkp[626463]: starting inbound Binkp session
    16 Nov 26 05:31:34 binkp[626463]: address: 77:77/77@FTNStats
    16 Nov 26 05:31:34 binkp[626463]: system: FTNStats Census
    16 Nov 26 05:31:34 binkp[626463]: from: Internet
    16 Nov 26 05:31:34 binkp[626463]: sysop: FTNStats Robot
    16 Nov 26 05:31:34 binkp[626463]: phone: (null)
    16 Nov 26 05:31:34 binkp[626463]: flags: [0] (null)
    16 Nov 26 05:31:34 binkp[626463]: mailer: ftn-stats/0.1.0 binkp/1.1
    16 Nov 26 05:31:34 binkp[626463]: time: 00:00:00, unknown
    16 Nov 26 05:31:34 binkp[626463]: Bad password
    16 Nov 26 05:31:34 binkp[626463]: total: 0:00:00 online, 0b sent, 0b received 16 Nov 26 05:31:34 binkp[626463]: session with 77:77/77 failed [ok]
    16 Nov 26 05:31:34 binkp[626463]: exiting with rc=4
    === Cut ===

    And then I have this condition in my qico config:

    "if address 77:77/* : abortsession Session refused"

    Thanks! I'll put that to my qico too!

    'Tommi

    --- GoldED+/LNX 2.0.0-b20260928
    * Origin: nntps://news.fidonet.fi (2:221/1)
  • From Alexey Matrosov@2:203/910 to Tommi Koivula on Tuesday, November 17, 2026 20:12:47
    Hello Tommi,

    Tuesday November 17 2026 21:01, you wrote to me:

    Nowadays there are some bots polling your system from a weird
    addresses without a good reason. In my case I'm getting those
    sort of calls from 77:77/77 once per week or so. To eliminate
    this kind of annoyances I've implemented a listed detection and
    conditional abortsession in qico.
    I see those probes from 77:77/77 too. Not really a problem, but I've
    set up a session password for it :D

    That also works well haha ;)

    And then I have this condition in my qico config:
    "if address 77:77/* : abortsession Session refused"
    Thanks! I'll put that to my qico too!

    No worries, just let me know if you have any other improvement ideas :)

    Mvh,
    Alex.

    --- .-. .- -... .- .-. -... . .-.
    * Origin: Rabarber > Skelleftea > Sweden (2:203/910)
  • From Wilfred van Velzen@2:280/464 to Alexey Matrosov on Tuesday, November 17, 2026 21:02:47
    Hi Alexey,

    On 2026-11-17 19:02:21, you wrote to me:

    (from 77:77/77@FTNStats, failed, S/R: 0/0 (0/0 bytes))

    The thing is the owner of that polling script doesn't look like a real
    FTN sysop.

    You can't really tell anything from the logs who the owner is. But since he is playing with Fidonet technology, I think it's much more likely someone involved with Fidonet, then not.

    So, the reason of those polls is blurry to me.

    "FTNStats" -> someone gathering data about fidonet systems? But indeed blurry...

    It is better to be prepared and check one more time if our systems are ready for those kind of scenarios.

    What kind of scenarios are you talking about?

    There is another example, a couple of month ago I got a call with FREQ from unlisted system pretending to be my point:

    05 Oct 26 01:49:33 binkp[279306]: answering incoming call
    05 Oct 26 01:49:33 binkp[279306]: remote is 94.19.123.34

    That's a Russian IP address. The provider could probably track it down if they were forced to, so that someone isn't really trying to hide his identity...

    05 Oct 26 01:49:33 binkp[279306]: starting inbound Binkp session
    05 Oct 26 01:49:33 binkp[279306]: Binkp: got unknown NUL: "OPT"
    05 Oct 26 01:49:33 binkp[279306]: address: 2:203/910.9999@fidonet
    05 Oct 26 01:49:33 binkp[279306]: system: binkd-go livetest
    05 Oct 26 01:49:33 binkp[279306]: from: livetest
    05 Oct 26 01:49:33 binkp[279306]: sysop: livetest
    05 Oct 26 01:49:33 binkp[279306]: phone: -Unpublished-
    05 Oct 26 01:49:33 binkp[279306]: flags: [115200] (null)
    05 Oct 26 01:49:33 binkp[279306]: mailer: binkd/1.1a-115/Unix binkp/1.0 05 Oct 26 01:49:33 binkp[279306]: time: 23:48:33, unknown

    Not the same time as your log lines, off by two hours (UTC?), and 1 minute. So one of yours clocks is not synchronized to the internet.

    05 Oct 26 01:49:33 binkp[279306]: we have: 0b mail, 0b files
    05 Oct 26 01:49:33 binkp[279306]: options: Binkp/Plain

    I checked my logs, but there are no connections from a 94.19.* address, nor is there "binkd-go" in my logs for the this year.
    So this doesn't seem to have been a fido wide probe. ;-)

    Bye, Wilfred.

    --- FMail-lnx64 2.3.4.1-B20260520
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Tuesday, November 17, 2026 21:16:52
    Hi Tommi,

    On 2026-11-17 21:01:56, you wrote to Alexey Matrosov:

    I see those probes from 77:77/77 too. Not really a problem, but I've
    set up a session password for it :D

    What does that accomplish? You don't have matching Zone numbers, so the connection fails anyway. And he doesn't even seems to be trying to deliver any files. And node information is already exchanged (I think?) before the password is checked.


    Bye, Wilfred.

    --- FMail-lnx64 2.3.4.1-B20260520
    * Origin: FMail development HQ (2:280/464)
  • From Alexey Matrosov@2:203/910 to Wilfred van Velzen on Tuesday, November 17, 2026 21:57:44
    Hello Wilfred,

    Tuesday November 17 2026 21:02, you wrote to me:

    (from 77:77/77@FTNStats, failed, S/R: 0/0 (0/0 bytes))
    The thing is the owner of that polling script doesn't look like a
    real FTN sysop.
    You can't really tell anything from the logs who the owner is. But
    since he is playing with Fidonet technology, I think it's much more
    likely someone involved with Fidonet, then not.

    Yeah, that could be someone familiar with FTN. But what's the purpose of such polls?..

    So, the reason of those polls is blurry to me.
    "FTNStats" -> someone gathering data about fidonet systems? But indeed blurry...

    Indeed.

    It is better to be prepared and check one more time if our
    systems are ready for those kind of scenarios.
    What kind of scenarios are you talking about?

    What I meant was that it might be a good idea to double check whether we are taking proper care of our unprotected inbound for instance ;)

    There is another example, a couple of month ago I got a call with
    FREQ from unlisted system pretending to be my point:
    05 Oct 26 01:49:33 binkp[279306]: answering incoming call
    05 Oct 26 01:49:33 binkp[279306]: remote is 94.19.123.34
    That's a Russian IP address. The provider could probably track it down
    if they were forced to, so that someone isn't really trying to hide
    his identity...

    Yes, it would seem so.

    binkp/1.0 05 Oct 26 01:49:33 binkp[279306]: time: 23:48:33,
    unknown
    Not the same time as your log lines, off by two hours (UTC?), and 1 minute. So one of yours clocks is not synchronized to the internet.

    No, that's the the correct clock on my server's side, I have CET which is UTC+1 now. The clock is in sync with the internet time.

    05 Oct 26 01:49:33 binkp[279306]: we have: 0b mail, 0b files
    05 Oct 26 01:49:33 binkp[279306]: options: Binkp/Plain
    I checked my logs, but there are no connections from a 94.19.*
    address, nor is there "binkd-go" in my logs for the this year. So this doesn't seem to have been a fido wide probe. ;-)

    Yep, I also had only one incoming connection from that ip.
    But that doesn't mean anything, since the previous example has a series of calls done from the 77:77/77 actually comes from a different ip each time (dynamic?).

    Mvh,
    Alex.

    --- .-. .- -... .- .-. -... . .-.
    * Origin: Rabarber > Skelleftea > Sweden (2:203/910)
  • From Wilfred van Velzen@2:280/464 to Alexey Matrosov on Tuesday, November 17, 2026 22:31:40
    Hi Alexey,

    On 2026-11-17 21:57:44, you wrote to me:

    (from 77:77/77@FTNStats, failed, S/R: 0/0 (0/0 bytes))
    The thing is the owner of that polling script doesn't look like a
    real FTN sysop.
    You can't really tell anything from the logs who the owner is. But
    since he is playing with Fidonet technology, I think it's much more
    likely someone involved with Fidonet, then not.

    Yeah, that could be someone familiar with FTN. But what's the purpose of such
    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. ;-)

    It is better to be prepared and check one more time if our
    systems are ready for those kind of scenarios.
    What kind of scenarios are you talking about?

    What I meant was that it might be a good idea to double check whether we are
    taking proper care of our unprotected inbound for instance ;)

    On most systems that is not processed automatically...

    binkp/1.0 05 Oct 26 01:49:33 binkp[279306]: time: 23:48:33,
    unknown
    Not the same time as your log lines, off by two hours (UTC?), and 1
    minute. So one of yours clocks is not synchronized to the internet.

    No, that's the the correct clock on my server's side, I have CET which is UTC+1 now.

    And early October you were on UTC+2, so the other side probably was displaying UTC time.

    The clock is in sync with the internet time.

    So the other side is not in sync, because of the 1 minute time difference.

    I checked my logs, but there are no connections from a 94.19.*
    address, nor is there "binkd-go" in my logs for the this year. So
    this doesn't seem to have been a fido wide probe. ;-)

    Yep, I also had only one incoming connection from that ip.
    But that doesn't mean anything, since the previous example has a series of calls done from the 77:77/77 actually comes from a different ip each time (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)
  • From Nick Andre@1:229/426 to Alexey Matrosov on Tuesday, November 17, 2026 18:51:00
    likely someone involved with Fidonet, then not.

    Yeah, that could be someone familiar with FTN. But what's the purpose of su polls?..

    Two comments... because "they can"... of which results in me quoting the
    famous phrase "We can't have nice things"...

    Nick

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Dmitry Protasoff@2:5001/100 to Wilfred van Velzen on Wednesday, November 18, 2026 02:14:42
    Hello Wilfred!

    In a message of 17 Nov 26 22:31, Wilfred wrote to Alexey:

    Well it could be something like Dimitry

    It's actually Louis Northmore, 2:250/8.
    90% sure about that.

    But I am very much ok that he made Nick unhappy. The last time Nick was very upset about my nationality, it's much better that someone native to the Western Europe made him even more angry :)

    See you,
    dp.
    --- FidoMail v0.1.5-313-g440ace32
    * Origin: livin' on the edge (2:5001/100)
  • From Nick Andre@1:229/426 to Dmitry Protasoff on Tuesday, November 17, 2026 21:25:58
    It's actually Louis Northmore, 2:250/8.
    90% sure about that.

    But I am very much ok that he made Nick unhappy. The last time Nick was ver upset about my nationality, it's much better that someone native to the Western Europe made him even more angry :)

    To which I will simply reply that one can only imagine if this was all someone from Zone 1 doing this nonsense targeted towards you idiots - All of you would effeminately scream murder and demand your happy-Belgian ZC2 act on it.

    Actually its somewhat amusing, the both of you uneducated dipshits need to carefully re-read about the "Excessively annoying behavior" clause of Policy you all agreed to.

    Nick

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Dmitry Protasoff@2:5001/100 to Nick Andre on Wednesday, November 18, 2026 02:50:20
    Hello Nick!

    In a message of 17 Nov 26 21:25, Nick wrote to Dmitry:

    To which I will simply

    This is what you've wrote:

    "There are a couple of characters I suspect, but can't prove it."

    And I figured out who it was and found proof in like 10 minutes. The rest is irrelevant. You're simply incompetent.

    You can scream at your monitor all you want, but you just proved that you can't do it and I can.

    Live with it (if you can) ;)

    See you,
    dp.
    --- FidoMail v0.1.5-313-g440ace32
    * Origin: livin' on the edge (2:5001/100)
  • From Nick Andre@1:229/426 to Dmitry Protasoff on Tuesday, November 17, 2026 22:32:57
    On 18 Nov 26 02:50:20, Dmitry Protasoff said the following to Nick Andre:

    And I figured out who it was and found proof in like 10 minutes. The rest i irrelevant. You're simply incompetent.

    You can scream at your monitor all you want, but you just proved that you can't do it and I can.

    Bahaha... whats next? Peel off the mask and reveal yourelf to be Jas Hud?

    Nick

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Alexey Matrosov@2:203/910 to Wilfred van Velzen on Wednesday, November 18, 2026 06:29:27
    Hello Wilfred,

    Tuesday November 17 2026 22:31, you wrote to me:

    Yeah, that could be someone familiar with FTN. But what's the
    purpose of such 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. ;-)

    That's obviously true! :) Dmitry is doing a good thing, and he is doing it from a recognizable address within his system.

    Yep, I also had only one incoming connection from that ip.
    But that doesn't mean anything, since the previous example has a
    series of calls done from the 77:77/77 actually comes from a
    different ip each time (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.

    Oh. Yeah and we can't block the whole thing, so some known good system could also run on Musk' internet.
    So for example here they offer quite good prices for fixed-line internet.

    Mvh,
    Alex.

    --- .-. .- -... .- .-. -... . .-.
    * Origin: Rabarber > Skelleftea > Sweden (2:203/910)
  • From Tommi Koivula@2:221/360 to Wilfred van Velzen on Wednesday, November 18, 2026 08:48:32
    On 17.11.2026 22.16, Wilfred van Velzen wrote:

    On 2026-11-17 21:01:56, you wrote to Alexey Matrosov:

    I see those probes from 77:77/77 too. Not really a problem, but I've
    set up a session password for it :D

    What does that accomplish? You don't have matching Zone numbers, so the connection fails anyway. And he doesn't even seems to be trying to
    deliver any files. And node information is already exchanged (I think?) before the password is checked.

    Actually, it did not fail before I set the password.

    09 Nov 26 10:03:03 binkp[1247691]: answering incoming call
    09 Nov 26 10:03:03 binkp[1247691]: remote is 145.224.90.62
    09 Nov 26 10:03:03 binkp[1247691]: starting inbound Binkp session
    09 Nov 26 10:03:03 binkp[1247691]: address: 77:77/77@FTNStats
    09 Nov 26 10:03:03 binkp[1247691]: system: FTNStats Census
    09 Nov 26 10:03:03 binkp[1247691]: from: Internet
    09 Nov 26 10:03:03 binkp[1247691]: sysop: FTNStats Robot
    09 Nov 26 10:03:03 binkp[1247691]: phone: -Unpublished-
    09 Nov 26 10:03:03 binkp[1247691]: flags: [0] (null)
    09 Nov 26 10:03:03 binkp[1247691]: mailer: ftn-stats/0.1.0 binkp/1.1
    09 Nov 26 10:03:03 binkp[1247691]: time: 00:00:00, unknown
    09 Nov 26 10:03:03 binkp[1247691]: we have: 0b mail, 0b files
    09 Nov 26 10:03:03 binkp[1247691]: options: Binkp/MB/Plain
    09 Nov 26 10:03:04 binkp[1247691]: total: 0:00:01 online, 0b sent, 0b received 09 Nov 26 10:03:04 binkp[1247691]: session with 77:77/77 successful [ok]
    09 Nov 26 10:03:04 binkp[1247691]: exiting with rc=0

    But this is qico, not related to this echo.

    'Tommi

    --- FastEcho/2 1.46.1 Revival
    * Origin: nntp://rbb.fidonet.fi - Finland (2:221/360.0)
  • From Yegor Gluhov@2:382/736 to Tommi Koivula on Wednesday, November 18, 2026 10:14:51
    Hello Tommi!

    18 Nov 26 08:48, you wrote to Wilfred van Velzen:

    I see those probes from 77:77/77 too. Not really a problem, but I've
    set up a session password for it :D
    What does that accomplish? You don't have matching Zone numbers, so the
    connection fails anyway. And he doesn't even seems to be trying to deliver
    any files. And node information is already exchanged (I think?) before the
    password is checked.
    Actually, it did not fail before I set the password.
    [...]
    But this is qico, not related to this echo.

    In binkd it fails:

    16 Nov 04:32:09 [86644] binkp init done, socket # is 5
    + 16 Nov 04:32:09 [86644] incoming session with customer.lndngbr1.isp.starlink.com [9.246.113.252]
    16 Nov 04:32:09 [86644] send message NUL OPT CRAM-MD5-a62ae49e0ee848f402946de22955a0ee
    16 Nov 04:32:09 [86644] send message NUL SYS Jegornet
    16 Nov 04:32:09 [86644] send message NUL ZYZ Yegor Gluhov
    16 Nov 04:32:09 [86644] send message NUL LOC Belgrade, Serbia
    16 Nov 04:32:09 [86644] send message NUL NDL 115200,TCP,BINKP,MO
    16 Nov 04:32:09 [86644] send message NUL TIME Mon, 16 Nov 2026 04:32:09 +0100
    16 Nov 04:32:09 [86644] send message NUL VER binkd/1.1a-115/Linux binkp/1.1
    16 Nov 04:32:09 [86644] rcvd msg NUL SYS FTNStats Census
    - 16 Nov 04:32:09 [86644] SYS FTNStats Census
    16 Nov 04:32:09 [86644] rcvd msg NUL ZYZ FTNStats Robot
    - 16 Nov 04:32:09 [86644] ZYZ FTNStats Robot
    16 Nov 04:32:09 [86644] rcvd msg NUL LOC Internet
    - 16 Nov 04:32:09 [86644] LOC Internet
    16 Nov 04:32:09 [86644] rcvd msg NUL VER ftn-stats/0.1.0 binkp/1.1
    - 16 Nov 04:32:09 [86644] VER ftn-stats/0.1.0 binkp/1.1
    16 Nov 04:32:09 [86644] remote uses binkp v.1.1
    16 Nov 04:32:09 [86644] rcvd msg ADR 77:77/77@FTNStats
    + 16 Nov 04:32:09 [86644] addr: 77:77/77@FTNStats (n/a or busy)
    ? 16 Nov 04:32:09 [86644] no AKAs in common domains or all AKAs are busy
    16 Nov 04:32:09 [86644] send message BSY No AKAs in common domains or all AKAs are busy
    + 16 Nov 04:32:09 [86644] done (from 77:77/77@FTNStats, failed, S/R: 0/0 (0/0 bytes))

    Yegor

    --- AmberEdit/linux 0.11.1
    * Origin: to err is human, but to really f.. things up you need AI (2:382/736)
  • From Wilfred van Velzen@2:280/464 to Dmitry Protasoff on Wednesday, November 18, 2026 10:24:35
    Hi Dmitry,

    On 2026-11-18 02:14:42, you wrote to me:

    Well it could be something like Dimitry

    [Sorry about misspelling your name! ;-)]

    It's actually Louis Northmore, 2:250/8.
    90% sure about that.

    Have you asked him?

    His domain name in the nodelist doesn't resolve to a starlink ip address...


    Bye, Wilfred.

    --- FMail-lnx64 2.3.4.1-B20260520
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Alexey Matrosov on Wednesday, November 18, 2026 10:28:25
    Hi Alexey,

    On 2026-11-18 06:29:27, you wrote to me:

    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. ;-)

    That's obviously true! :) Dmitry is doing a good thing, and he is doing it from a recognizable address within his system.

    Agreed...

    + 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.

    Oh. Yeah and we can't block the whole thing, so some known good system could
    also run on Musk' internet. So for example here they offer quite good prices
    for fixed-line internet.

    If you want to block all scanners (and such), you will have to block 0.0.0.0/0 and ::/0 ... ;-)

    Bye, Wilfred.

    --- FMail-lnx64 2.3.4.1-B20260520
    * Origin: FMail development HQ (2:280/464)
  • From Alexey Matrosov@2:203/910.1 to Wilfred van Velzen on Wednesday, November 18, 2026 11:06:55
    Hej Wilfred,

    Wilfred van Velzen wrote:

    + 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.

    Oh. Yeah and we can't block the whole thing, so some known good
    system could also run on Musk' internet. So for example here they
    offer quite good prices for fixed-line internet.

    If you want to block all scanners (and such), you will have to
    block 0.0.0.0/0 and ::/0 ... ;-)

    Nah that's for sure ;)

    Mvh,
    Alex.

    --- FidoMailMobile/0.3.2+111 (Android)
    * Origin: Rabarber > Skelleftea > Sweden (2:203/910.1)
  • From Ivan Zelenyi@2:50/86.1 to Alexey Matrosov on Wednesday, November 18, 2026 16:02:31
    Hello, Alexey!

    Alexey Matrosov wrote:

    If you want to block all scanners (and such), you will have to
    block 0.0.0.0/0 and ::/0 ... ;-)

    Nah that's for sure ;)

    New Slogan: "Save our Fidonet! Set block to 0.0.0.0!" ))

    With best regards,
    Ivan Zelenyi

    --- FidoMailMobile/0.3.2+111 (Android)
    * Origin: -UA9278SWL- Nizhnevartovsk Russia (2:50/86.1)
  • From Dmitry Protasoff@2:5001/100 to Wilfred van Velzen on Wednesday, November 18, 2026 11:44:02
    Hello Wilfred!

    In a message of 18 Nov 26 10:24, Wilfred wrote to Dmitry:

    Have you asked him?

    No, but I don't see a problem with anyone calling my node. It's like setting up a web server and having diarrhea every time someone unknown visits it.

    His domain name in the nodelist doesn't resolve to a starlink ip address...

    But he moved to new home and uses Starlink for outgoing connections.

    See you,
    dp.
    --- FidoMail v0.1.5-313-g440ace32
    * Origin: livin' on the edge (2:5001/100)
  • From Wilfred van Velzen@2:280/464 to Dmitry Protasoff on Wednesday, November 18, 2026 12:50:15
    Hi Dmitry,

    On 2026-11-18 11:44:02, you wrote to me:

    Have you asked him?

    No, but I don't see a problem with anyone calling my node. It's like setting
    up a web server and having diarrhea every time someone unknown visits it.

    I agree...

    His domain name in the nodelist doesn't resolve to a starlink ip
    address...

    But he moved to new home and uses Starlink for outgoing connections.

    You have inside information? ;-)


    Bye, Wilfred.

    --- FMail-lnx64 2.3.4.1-B20260520
    * Origin: FMail development HQ (2:280/464)
  • From Dmitry Protasoff@2:5001/100 to Wilfred van Velzen on Wednesday, November 18, 2026 13:17:12
    Hello Wilfred!

    In a message of 18 Nov 26 12:50, Wilfred wrote to Dmitry:

    But he moved to new home and uses Starlink for outgoing
    connections.

    You have inside information? ;-)

    I've checked his FidoNet, Facebook and other social media posts :)
    Actually, I've never known anything about this guy before yesterday.

    In fact, he did nothing wrong. There is a guy in R50 who has been sending me zip bombs through TOR exit nodes for some time (without any AI-slop!). I don't even see this as a real crime, more like a challenge to fix the scripts and software that manage such behaviour ;)

    See you,
    dp.
    --- FidoMail v0.1.5-313-g440ace32
    * Origin: livin' on the edge (2:5001/100)
  • From Alexey Fayans@2:5030/1997 to Dmitry Protasoff on Wednesday, November 18, 2026 16:23:12
    Hello Dmitry!

    On Wed, 18 Nov 2026 13:17 +0000, you wrote to Wilfred van Velzen:

    In fact, he did nothing wrong. There is a guy in R50 who has been
    sending me zip bombs through TOR exit nodes for some time (without any AI-slop!). I don't even see this as a real crime, more like a
    challenge to fix the scripts and software that manage such behaviour
    ;)

    Anyone who does otherwise should probably cut themselves from the internet permanently.


    ... Music Station BBS | https://bbs.bsrealm.net | telnet://bbs.bsrealm.net
    --- GoldED+/W32-MSVC 1.1.5-b20180707
    * Origin: Music Station | https://ms.bsrealm.net (2:5030/1997)
  • From Yegor Gluhov@2:382/736 to Alexey Fayans on Wednesday, November 18, 2026 14:45:59
    Hello Alexey!

    18 Nov 26 16:23, you wrote to Dmitry Protasoff:

    In fact, he did nothing wrong. There is a guy in R50 who has been
    sending me zip bombs through TOR exit nodes for some time (without any
    AI-slop!). I don't even see this as a real crime, more like a challenge
    to fix the scripts and software that manage such behaviour ;)
    Anyone who does otherwise should probably cut themselves from the
    internet permanently.

    ...and hook a modem up to a POTS line instead. Then throw a tantrum whenever some stranger dials in during ZMH.

    Yegor

    --- AmberEdit/linux 0.11.1
    * Origin: to err is human, but to really f.. things up you need AI (2:382/736)
  • From Dmitry Protasoff@2:5001/100 to Alexey Fayans on Wednesday, November 18, 2026 14:57:24
    Hello Alexey!

    In a message of 18 Nov 26 16:23, Alexey wrote to Dmitry:

    Anyone who does otherwise should probably cut themselves from the
    internet permanently.

    Exactly! It's like going on safari and complaining that lions could attack you.

    If the sysop isn't ready to take the risks, he could downgrade to a point and live happily ever after. Or become a BBS user. Even safer.

    See you,
    dp.
    --- FidoMail v0.1.5-313-g440ace32
    * Origin: livin' on the edge (2:5001/100)
  • From Dmitry Protasoff@2:5001/100 to Yegor Gluhov on Wednesday, November 18, 2026 15:44:34
    Hello Yegor!

    In a message of 18 Nov 26 14:45, Yegor wrote to Alexey:

    ...and hook a modem up to a POTS line instead. Then throw a tantrum whenever some stranger dials in during ZMH.

    There are so many BBSes in Z1 that they will be happy to get a new user. No problems with incoming connections at all!

    See you,
    dp.
    --- FidoMail v0.1.5-313-g440ace32
    * Origin: livin' on the edge (2:5001/100)
  • From Mike Powell@1:2320/107 to Wilfred van Velzen on Wednesday, November 18, 2026 16:43:32
    addr: 77:2/110@scinet

    FWIW, unless someone has revived it, scinet disappeared several years ago.

    Mike

    --- ScorpioWeb v0.39a (Linux/x86_64)
    * Origin: capitolcityonline.net * KY, USA (1:2320/107)
  • From Mike Powell@1:2320/107 to Wilfred van Velzen on Wednesday, November 18, 2026 16:46:20
    + 14 Nov 08:23:06 [28635] incoming session with
    2603:c020:c00f:4d7e:0:7dac:811f:801 - 14 Nov 08:23:06 [28635]
    SYS nodelist.fidonet.cc - 14 Nov 08:23:06 [28635] ZYZ Dmitry
    Protasoff - 14 Nov 08:23:06 [28635] LOC London, UK
    - 14 Nov 08:23:06 [28635] VER NodelistDB/1.0 binkp/1.1
    - 14 Nov 08:23:06 [28635] TIME 14 Nov 26 07:23 UTC
    + 14 Nov 08:23:06 [28635] addr: 2:5001/100.5001@fidonet
    + 14 Nov 08:23:06 [28635] done (from 2:5001/100.5001@fidonet,
    OK, S/R: 0/0 (0/0 bytes))
    14 Nov 08:23:06 [28635] session closed, quitting...


    That one hits my ifcico port two or three times a week. I don't mind it too much because his doing so actually helped me find a couple of issues on my end. As no one else connects here that way, it was accidentally helpful. ;)

    Mike

    --- ScorpioWeb v0.39a (Linux/x86_64)
    * Origin: capitolcityonline.net * KY, USA (1:2320/107)
  • From Mike Powell@1:2320/107 to Dmitry Protasoff on Wednesday, November 18, 2026 16:52:46
    Hello Nick!

    In a message of 17 Nov 26 21:25, Nick wrote to Dmitry:

    To which I will simply

    This is what you've wrote:

    "There are a couple of characters I suspect, but can't prove
    it."

    And I figured out who it was and found proof in like 10
    minutes. The rest is irrelevant. You're simply incompetent.

    I am pretty sure the person you figured out... FTNstats?... is not the same as the system(s) that Nick mentioned. Where FTNstats flies the same name each time, it looked like the system names on the hits Nick were getting are random, and at least one he mentioned sounded more like a law office than a BBS system name.

    So more like some AI bot than a person gathering network stats.

    Mike

    --- ScorpioWeb v0.39a (Linux/x86_64)
    * Origin: capitolcityonline.net * KY, USA (1:2320/107)
  • From Dmitry Protasoff@2:5001/100 to Mike Powell on Wednesday, November 18, 2026 17:13:25
    Hello Mike!

    In a message of 18 Nov 26 16:46, Mike wrote to Wilfred:

    That one hits my ifcico port two or three times a week. I don't
    mind it too much because his doing so actually helped me find a
    couple of issues on my end. As no one else connects here that way,
    it was accidentally helpful. ;)

    Well, I’m not hiding behind fake addresses and you can always contact me with any questions. The software is open source, and I’m ready to give anyone all the raw data so they don’t have to scan anything themselves. Or I can publish any report they like at https://nodelist.fidonet.cc/.


    See you,
    dp.
    --- FidoMail v0.1.5-326-gd0973d61
    * Origin: livin' on the edge (2:5001/100)
  • From Dmitry Protasoff@2:5001/100 to Mike Powell on Wednesday, November 18, 2026 20:18:03
    Hello Mike!

    In a message of 18 Nov 26 16:52, Mike wrote to Dmitry:

    I am pretty sure the person you figured out... FTNstats?... is not
    the same as the system(s) that Nick mentioned. Where FTNstats

    I am ready to help others with FTNstatsr, but since Nick decided to block transit mail from my node because I was not nice to him, he is on his own :)




    See you,
    dp.
    --- FidoMail v0.1.5-326-gd0973d61
    * Origin: livin' on the edge (2:5001/100)
  • From Nick Andre@1:229/426 to Dmitry Protasoff on Wednesday, November 18, 2026 15:31:56
    On 18 Nov 26 20:18:03, Dmitry Protasoff said the following to Mike Powell:

    I am pretty sure the person you figured out... FTNstats?... is not
    the same as the system(s) that Nick mentioned. Where FTNstats

    I am ready to help others with FTNstatsr, but since Nick decided to block transit mail from my node because I was not nice to him, he is on his own :

    Correct, I am not obligated to route mail for anyone not nice.

    You sure make a lot of effeminate noise over this and other nonsense, are you sure you're not related to Jas Hud or have Dutch ancestry?

    Nick

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Dmitry Protasoff@2:5001/100 to Nick Andre on Wednesday, November 18, 2026 21:37:20
    Hello Nick!

    In a message of 18 Nov 26 15:31, Nick wrote to Dmitry:

    You sure make a lot of effeminate noise over this and other
    nonsense, are you sure you're not related to Jas Hud or have Dutch ancestry?

    You mean - could I be you relative? Highly unlikely, because I don't have any extra chromosomes ;)

    In the meantime, 2:5001/100 is ready to accept any link, won't block any connections, and got native I2P and Tor endpoints with binkd enabled.

    It even has link self-registration and web access to manage subscriptions and search the largest FidoNet message archive in the world (almost 60 million and it will be much more soon).

    Join the Dark Side, Nick! We've got cookies! And Vodka!

    https://f100.5001.ru/

    See you,
    dp.
    --- FidoMail v0.1.5-326-gd0973d61
    * Origin: livin' on the edge (2:5001/100)
  • From Nick Andre@1:229/426 to Dmitry Protasoff on Wednesday, November 18, 2026 17:10:15
    On 18 Nov 26 21:37:20, Dmitry Protasoff said the following to Nick Andre:

    In the meantime, 2:5001/100 is ready to accept any link, won't block any connections, and got native I2P and Tor endpoints with binkd enabled.

    ... Except it will never host-route through my system.

    Join the Dark Side, Nick! We've got cookies! And Vodka!

    Yeah, figured you and Louis love to cosplay as stormtroopers. I'll pass.

    Nick

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Dmitry Protasoff@2:5001/100 to Nick Andre on Wednesday, November 18, 2026 22:37:15
    Hello Nick!

    In a message of 18 Nov 26 17:10, Nick wrote to Dmitry:

    ... Except it will never host-route through my system.

    Yeah, I know that your system is not reliable, it's not a secret.


    See you,
    dp.
    --- FidoMail v0.1.5-326-gd0973d61
    * Origin: livin' on the edge (2:5001/100)
  • From Nick Andre@1:229/426 to Dmitry Protasoff on Wednesday, November 18, 2026 17:52:22
    On 18 Nov 26 22:37:15, Dmitry Protasoff said the following to Nick Andre:

    ... Except it will never host-route through my system.

    Yeah, I know that your system is not reliable, it's not a secret.

    Correct, its not reliable for you.

    Sorry, I'm not an expert at conversing with the socially-retarded; maybe share your 60 million faggy stormtrooper fantasies with Wilfred or someone else.

    Nick

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Dmitry Protasoff@2:5001/100 to Nick Andre on Wednesday, November 18, 2026 23:38:40
    Hello Nick!

    In a message of 18 Nov 26 17:52, Nick wrote to Dmitry:

    Correct, its not reliable for you.

    For anyone :)

    Sorry, I'm not an expert at conversing

    You are hardly an expert even in filtering some weirdo with binkd, Nick :)

    And you were ready to pay your money for a feature in software written by some Russian guy which you now have to use, despite your problems with Russians!

    I can give you contacts of the original binkd author, Dima Maloff. But you don't have enough money to pay him for this task ;))))

    See you,
    dp.
    --- FidoMail v0.1.5-326-gd0973d61
    * Origin: livin' on the edge (2:5001/100)
  • From Nick Andre@1:229/426 to Dmitry Protasoff on Wednesday, November 18, 2026 18:45:51
    On 18 Nov 26 23:38:40, Dmitry Protasoff said the following to Nick Andre:

    You are hardly an expert even in filtering some weirdo with binkd, Nick :)

    Expert enough to filter Netmails from the stormtrooper weirdo at 2:5001/100.

    And you were ready to pay your money for a feature in software written by s Russian guy which you now have to use, despite your problems with Russians!

    And my polite offer still stands. The only one here making such a stink is the weirdo boasting of 60-million fantasies... unable to host-route through 1:1/0.

    Nick

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From T.J. Mcmillen@1:229/426 to Nick Andre on Wednesday, November 18, 2026 21:06:25
    Correct, I am not obligated to route mail for anyone not nice.

    Shit man, that's what happened to MRO .... no mail for him!

    I am ready to help others with FTNstatsr, but since Nick decided to block

    What is the point of this thing other than pinging ports to see what is open? And people cry over using SSH, and we have this?

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Dmitry Protasoff@2:5001/100 to Nick Andre on Thursday, November 19, 2026 02:13:50
    Hello Nick!

    In a message of 18 Nov 26 18:45, Nick wrote to Dmitry:

    Expert enough to filter Netmails from the stormtrooper weirdo at 2:5001/100.

    You are such a good filter, Nick! The best filter in FidoNet! Nick The Filter ;)

    Too bad for you that binkd was implemented for people who prefer connectivity to filtering.

    And my polite offer still stands.

    You mean, still no one wants your money? Expected! They smell like .... Because you are a good filter, Nick ;)

    Keep the filter strong! You'll need it! Enough for today :)

    See you,
    dp.

    --- FidoMail v0.1.5-336-g600fdfce
    * Origin: livin' on the edge (2:5001/100)
  • From Nick Andre@1:229/426 to Dmitry Protasoff on Wednesday, November 18, 2026 21:39:57
    On 19 Nov 26 02:13:50, Dmitry Protasoff said the following to Nick Andre:

    You mean, still no one wants your money? Expected! They smell like .... Because you are a good filter, Nick ;)

    You've made so much noise over something easily avoided; you could have routed your gay-robot crap through here all you wanted - Had you of made a polite introduction beforehand. You did not, so you got shitcanned. End of story.

    THATS whats funny, more than your nothing-burger replies now.

    Nick

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)
  • From Alex Galiyev@1:129/14.1 to Dmitry Protasoff on Wednesday, November 18, 2026 21:49:35
    Hello Dmitry!

    Thursday November 19 2026 02:13, you wrote to Nick Andre:

    One day, your terrorist regime may find itself cut off from the Global Internet.
    Enjoy your pathetic little hacker games while you still can.
    Your country depends on the very infrastructure it tries to attack.
    Keep that in mind before pretending you're some kind of genius. �ãáì­ï ¥¡ ­ ï.

    Alex

    --- GoldED+/W64-MSVC-unicode
    * Origin: Glory to Ukraine! Dump Trump! Dump Ward! (1:129/14.1)
  • From Dmitry Protasoff@2:5001/100 to Nick Andre on Thursday, November 19, 2026 03:10:04
    Hello Nick!

    In a message of 18 Nov 26 21:39, Nick wrote to Dmitry:

    got shitcanned. End of story.

    Nick, you can filter whatever you want - I don't give a damn.
    End of story.


    See you,
    dp.
    --- FidoMail v0.1.5-336-g600fdfce
    * Origin: livin' on the edge (2:5001/100)
  • From Dmitry Protasoff@2:5001/100 to Alex Galiyev on Thursday, November 19, 2026 03:12:30
    Hello Alex!

    In a message of 18 Nov 26 21:49, Alex wrote to Dmitry:

    One day, your terrorist regime may find itself cut off from the

    Looks like you are a Trump supporter and hate the UK. Poor soul.
    You better help Nick fix his binkd. He'll pay you a lot! ;)

    See you,
    dp.
    --- FidoMail v0.1.5-336-g600fdfce
    * Origin: livin' on the edge (2:5001/100)
  • From Nick Andre@1:229/426 to T.J. Mcmillen on Wednesday, November 18, 2026 22:45:03
    On 18 Nov 26 21:06, T.J. Mcmillen said the following to Nick Andre:

    What is the point of this thing other than pinging ports to see what is ope And people cry over using SSH, and we have this?

    Funny how I blocked his robot crap and coincidentally get spammed soon after, but "end of story"... he's now eating a nothing-burger while being blocked.

    Nick

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (1:229/426)