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.
20261117 03:30:21 [56428] incoming from 192.42.116.16 (34424)
20261117 03:34:05 [6392] incoming session with 143.20.185.77
addr: 77:2/110@scinet
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.
+ 16 Nov 04:31:38 [15159] incoming session with customer.lndngbr1.isp.starlink.com [9.246.113.252]
A simple yes/no answer will suffice... willing to do Paypal $$ if the
former.
Short, simple answer. Probably not but you could...
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 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.
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.
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.
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.
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 listedI'm not annoyed by them, because it's so infrequent. But it would be
detection and conditional abortsession in qico.
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
addr: 77:2/110@scinet
This shut down yonks ago.
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"
Nowadays there are some bots polling your system from a weirdI see those probes from 77:77/77 too. Not really a problem, but I've
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.
set up a session password for it :D
And then I have this condition in my qico config:Thanks! I'll put that to my qico too!
"if address 77:77/* : abortsession Session refused"
(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.
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
I see those probes from 77:77/77 too. Not really a problem, but I've
set up a session password for it :D
(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 aYou can't really tell anything from the logs who the owner is. But
real FTN sysop.
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 ourWhat kind of scenarios are you talking about?
systems are ready for those kind of scenarios.
There is another example, a couple of month ago I got a call withThat's a Russian IP address. The provider could probably track it down
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
if they were forced to, so that someone isn't really trying to hide
his identity...
binkp/1.0 05 Oct 26 01:49:33 binkp[279306]: time: 23:48:33,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.
unknown
05 Oct 26 01:49:33 binkp[279306]: we have: 0b mail, 0b filesI checked my logs, but there are no connections from a 94.19.*
05 Oct 26 01:49:33 binkp[279306]: options: Binkp/Plain
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. ;-)
(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?..
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 ;)
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.
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?).
likely someone involved with Fidonet, then not.
Yeah, that could be someone familiar with FTN. But what's the purpose of su polls?..
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 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
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.
Yeah, that could be someone familiar with FTN. But what's theWell it could be something like Dimitry is doing (but not published
purpose of such polls?..
yet). Dimitry is giving back the data to Fidonet in a nice form on his website. ;-)
Yep, I also had only one incoming connection from that ip.+ 16 Nov 04:31:38 [15159] incoming session with customer.lndngbr1.isp.starlink.com [9.246.113.252]
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?).
Starlink: That's satelite connections from Elon Musks company. So very likely dynamic.
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.I see those probes from 77:77/77 too. Not really a problem, but I'veWhat does that accomplish? You don't have matching Zone numbers, so the
set up a session password for it :D
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.
But this is qico, not related to this echo.
Well it could be something like Dimitry
It's actually Louis Northmore, 2:250/8.
90% sure about that.
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.
+ 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.
+ 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 ... ;-)
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 ;)
Have you asked him?
His domain name in the nodelist doesn't resolve to a starlink ip address...
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.
But he moved to new home and uses Starlink for outgoing
connections.
You have inside information? ;-)
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
;)
In fact, he did nothing wrong. There is a guy in R50 who has beenAnyone who does otherwise should probably cut themselves from the
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 ;)
internet permanently.
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.
addr: 77:2/110@scinet
+ 14 Nov 08:23:06 [28635] incoming session with2603: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...
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.
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. ;)
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 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 :
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?
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.
Join the Dark Side, Nick! We've got cookies! And Vodka!
... Except it will never host-route through my system.
... 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
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 s Russian guy which you now have to use, despite your problems with Russians!
Correct, I am not obligated to route mail for anyone not nice.
I am ready to help others with FTNstatsr, but since Nick decided to block
Expert enough to filter Netmails from the stormtrooper weirdo at 2:5001/100.
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 ;)
got shitcanned. End of story.
One day, your terrorist regime may find itself cut off from the
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?
| Sysop: | KrAAB |
|---|---|
| Location: | Donna, TX |
| Users: | 4 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 170:32:59 |
| Calls: | 57,180 |
| Files: | 3,971 |
| D/L today: |
26 files (9,999K bytes) |
| Messages: | 61,523 |