Just a new entry/exit world record for the nodelist;
Entered May 8th
Down June 12th
Dropped June 17th
Get them back in is one thing, getting then to stay is another...Meanwhile, the Fidonet old boys club will lean back in their chairs with a smug smile on thir face and think "that person didn't deserve to be here anyway!"
Listing him on the 8th of May was premature. He actually did not
answer incoming calls until the 14th. So his stay lasted less than
a month... In the meantime an overactive nodelist police deputy's attempts to poll him before he was ready caused his firewall to
block the deputy's IP number. The firewall was configured to do so
when an attempt to connect to a non existant was made. The sysop
in question was unaware that he already was in the nodelist. When
he found out about this premature action, he was not amused... As
I said, getting them back is one thing, getting them to stay is
another. The median life time of re-entering sysops is under a
year. One may expect deviations either way. A life time of less
than a month is remarkable but not so extreme as to be unexpected.
This returnee obviously did not like what he found after his
return. My guess is that the bad start didn't help either. It
happens.
Then the next day they'll type messages like "WhY iS fIdOnEt DyInG?!" on th cheeto-stained keyboards.
Meanwhile, the Fidonet old boys club will lean back in their chairs with
a smug smile on thir face and think "that person didn't deserve to be
here anyway!"
Then the next day they'll type messages like "WhY iS fIdOnEt DyInG?!" on their cheeto-stained keyboards.
On 17 Jun 21 15:09:44, Mike Miller said the following to Michiel Van
Der Vlist:
Then the next day they'll type messages like "WhY iS fIdOnEt
DyInG?!" on th cheeto-stained keyboards.
Not Cheeto's - they use the no-name brand. "Cheezy puffs"
Sad but true. Urban had it technically implemented, looked at the content and the fights and decided to be removed from the nodelist by now.
His routing generator was ported and refined during that time,
We've survived top-bullies such as Ron Dwight, Henk Wolsink, Bob
Seaborn, Ross Cassel, the Jansen-guy from the Netherlands and his
wobbly friend,
He confirms, that he was in Antwerp
He cannot remember if he spoke with you or not
He never approached anyone about commercial fidonet, ...
So, there must be a mixup. Probably with Jens Mller. 2:24/24
Listing him on the 8th of May was premature. He actually did not
answer incoming calls until the 14th.
That's your perspective,
your IP was blacklisted there due to your poll-tests. My connection
with him was earlier, but yes, the nodelist entry was a little bit premature.
In the meantime an overactive nodelist police deputy's attempts
to poll him before he was ready caused his firewall to block the
deputy's IP number. The firewall was configured to do so when an
attempt to connect to a non existant was made.
He has fail2ban active. Connecting to a non existing service causes blockage. A very long blockage. A too long blockage in my opinion.
The sysop in question was unaware that he already was in the
nodelist.
"Unaware" is a hard word for knowing that work is in progres on both sides.
When he found out about this premature action, he was not
amused...
I made the nodelist entry shortly before his system was up and
running, but i knew the progres of his work. Yes, it was not perfect
from my side, but that did not cause the blockage. I've even notified
you about the situation and asked to not test his system already. Unfortunatly, my words were not heard, so i had to arrange an
unblocking later.
Urban's system was pollig here perfectly before the nodelist entry was created.
This returnee obviously did not like what he found after his
return.
That's true.
Not Cheeto's - they use the no-name brand. "Cheezy puffs"
I love Cheesy Poofs, you love Cheesy Poofs. If we didn't eat Cheesy Poofs w be ....
Just a new entry/exit world record for the nodelist;
Entered May 8th
Down June 12th
Dropped June 17th
Listing him on the 8th of May was premature. He actually did not
answer incoming calls until the 14th.
In the meantime an overactive nodelist police deputy's attempts to
poll him before he was ready caused his firewall to block the deputy's
IP number. The firewall was configured to do so when an attempt to
connect to a non existant was made.
The sysop in question was unaware
that he already was in the nodelist.
When he found out about this premature action, he was not amused...
This returnee obviously did not like what he found after his return.
My guess is that the bad start didn't help either.
It happens.
And that's about fidonet anyway: Connecting people. So it worked :-)
Sad but true. Urban had it technically implemented, looked at theThat's nonsense. There's nowhere near the level of people around
content and the fights and decided to be removed from the nodelist
by now.
anymore to have quality fights.
The infamous 'routing generator' ... at least you have a sense of
humor.
The only thing I know Urban from is Eurocon IV in Antwerp.
He flew first class from Switzerland to Belgium, bragged about talking
to the Prime Minister (the Prime Minister has the usage of a
government business jet BTW, doesn't fly commercial), he went with unsuspecting sysops to classy restaurants, offered some guys money so their system could be used commercially and they came to see me with a heavy breathing voice "What do you think of this?" (I wasn't ZC at
that time 1990) ... he made me the same offer and wined and dined me
as well before I got the picture...
That's how I know him ,,, that's why I know he's not a stayer ...
He flew first class from Switzerland to Belgium, bragged about talking
to the Prime Minister (the Prime Minister has the usage of a
government business jet BTW, doesn't fly commercial), he went with unsuspecting sysops to classy restaurants, offered some guys money so their system could be used commercially and they came to see me with a heavy breathing voice "What do you think of this?" (I wasn't ZC at
that time 1990) ... he made me the same offer and wined and dined me
as well before I got the picture...
That's how I know him ,,, that's why I know he's not a stayer ...
But could he accept incoming calls? I guess not. Because you polling
him would have caused YOUR IP number to have been blocked as well.
Unless he had already configurted an acception for you in his
firewall.
fail2ban works analysing the log files and if it finds failed sessions
it just blocks the ip/net/whatever for minutes/hours/weeks/etc.
So... A failed connect, no matter what the reason, leads to a
blockade which in turn leads to more failed connects.
Exactly. I think that conecpt is crap.
So... A failed connect, no matter what the reason, leads to a
blockade which in turn leads to more failed connects. That does not
sound like an effective strategy to optimize connectivity. To put it
mildly. Especially in Fdionet where mailers do a number of retries
before they take a break. Some mailers never really give up
completeley unless the sysop intervenes.
Hmmm....
it depends on what you define as a failed connection.
for example this[..]
test is not a failed connection in my opinion:
- 30 May 09:05:54 [22516] SYS Nieuw Schnoord IPv6 test node
- 30 May 09:05:54 [22516] ZYZ Michiel van der Vlist
+ 30 May 09:05:54 [22516] Remote supports GZ mode
+ 30 May 09:05:54 [22516] done (from 2:280/5556@fidonet, OK, S/R: 0/0
(0/0 bytes))
so it depends on what you are defining in fail2ban :)
Obviously my IP WAS blocked. So I can not but conclude that he did not accept incoming calls when he was first listed.
So... A failed connect, no matter what the reason, leads to a blockade which in turn leads to more failed connects.
That does not sound like an effective strategy to optimize
connectivity. To put it mildly.
Especially in Fdionet where mailers do a number of retries before they take a break. Some mailers never really give up completeley unless the sysop intervenes.
Hello Matthias,
On Saturday June 19 2021 22:44, you wrote to me:
But could he accept incoming calls? I guess not. Because you
polling him would have caused YOUR IP number to have been
blocked as well. Unless he had already configurted an acception
for you in his firewall.
He was accepting incoming calls. Your IP was blocked and manually
unblocked on my request.
I did not say it was your fault, i only explaned the situation
back then.
Your explanation does no add up. You told me I was blocked because his ban2fail detects an attempt to connect to a non existant service. But
if he accepted incoming calls - as you now say - the service was
present and there should have been no resulting block on an attempt to connect.
Obviously my IP WAS blocked. So I can not but conclude that he did
not
accept incoming calls when he was first listed.
Hello Daniel,
On Sunday June 20 2021 16:35, you wrote to me:
fail2ban works analysing the log files and if it finds failed
sessions it just blocks the ip/net/whatever for
minutes/hours/weeks/etc.
So... A failed connect, no matter what the reason, leads to a blockade which in turn leads to more failed connects. That does not sound like
an effective strategy to optimize connectivity. To put it mildly. Especially in Fdionet where mailers do a number of retries before they take a break. Some mailers never really give up completeley unless the sysop intervenes.
Hmmm....
Matthias,
Sad but true. Urban had it technically implemented, looked at the conten and the fights and decided to be removed from the nodelist by now.
That's nonsense. There's nowhere near the level of people around anymore to have quality fights.
Some people may also misinterprete direct talk with little room for interpretation as aggressive.
We've survived top-bullies such as Ron Dwight, Henk Wolsink, Bob Seaborn, Ro Cassel, the Jansen-guy from the Netherlands and his wobbly friend, the Itali police, a lengthy court case, etc, etc, ...
Written words here are not fights, someone expressing an opinion you don't agree with ... live with it ... <Next> key.
\%/@rd
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 409 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 59:53:58 |
| Calls: | 8,572 |
| Calls today: | 2 |
| Files: | 13,225 |
| Messages: | 5,930,061 |