Host,466,Nikolaev_Net,Nikolaev_Ukraine,Yury_Roschupkin,-Unpublished-,300,MO,CM
, IBN,IFC,INA:procsys.ddns.mksat.net
Yuri left Fido three years ago.
Host,466,Nikolaev_Net,Nikolaev_Ukraine,Yury_Roschupkin,-Unpublished-,300,
M O,CM , IBN,IFC,INA:procsys.ddns.mksat.net
Yuri left Fido three years ago.
So why wasn't he replaced already?
Or net 466 removed?
There are 3 Pvt nodes, but without a functioning Host/Hub, they can't receive netmail, so they don't exist in Fidonet.
Yuri left Fido three years ago.
So why wasn't he replaced already? Or net 466 removed?
2:466/0 procsys.ddns.mksat.net - Error: Cannot getaddrinfo - Name or service not known
2:466/4 fido.snake.mk.ua:24554 2a01:4f8:c17:5f5b::2 Error:
Connection refused
2:466/4 fido.snake.mk.ua:24554 88.99.13.226 Error: Connection
refused
2:466/50 procsys.ddns.mksat.net - Error: Cannot getaddrinfo - Name
or service not known
2:466/65 procsys.ddns.mksat.net - Error: Cannot getaddrinfo - Name
or service not known
2:466/81 fqc.pp.ua:24554 217.77.220.48 Error: Connection timed out
There are 3 Pvt nodes, but without a functioning Host/Hub, they can't receive netmail, so they don't exist in Fidonet.
So why wasn't he replaced already?
As far as I know, no.
Or net 466 removed?
This is a very good question. I also think that the nodelist should
not contain so much dead wood. However, this is not the only such
network.
Not completely. Last year in september, there was still 1 node online:
2:466/4 fido.snake.mk.ua:24554 88.99.13.226 Ok.
Hi Michiel,
On 2025-05-23 12:25:49, you wrote to me:
That can be investigated:
Nodelist for Friday, May 23, 2025 -- Day number 143 parsed, 44
IP-nodes processed (0.009 sec)
So, lots of errors. And Nets 467 and 469 nets are also gone (except
for 1 remaining IBN node in each). Also net 4614 is gone.
That's up to the nodes in Region 46, and/or the ZC2.
Not completely. Last year in september, there was still 1 node
online:
2:466/4 fido.snake.mk.ua:24554 88.99.13.226 Ok.
I think so too, but I have no say in the matter. ;-)
If there is garbage in the nodelist it affects us all. So we all have a rig to comment.
There are 3 Pvt nodes, but without a functioning Host/Hub, they can't
receive netmail, so they don't exist in Fidonet.
Hi Michiel!
Friday May 23 2025 12:25, you wrote to Wilfred van Velzen:
There are 3 Pvt nodes, but without a functioning Host/Hub, they
can't receive netmail, so they don't exist in Fidonet.
Yes.
Most of all.
No. There is no better sysop for this position now.
Not completely. Last year in september, there was still 1 node online:
2:466/4 fido.snake.mk.ua:24554 88.99.13.226 Ok.
There are 3 Pvt nodes, but without a functioning Host/Hub, they
can't receive netmail, so they don't exist in Fidonet.
Yes.
Most of all.
No. There is no better sysop for this position now.
Stas Mishchenkov wrote to Michiel van der Vlist <=-
MvdV> If there is indeed no one who can clean up the Region then that
Mvdv> is a sad situation...
No one can be better than the current R46C. Why he doesn't do this, you need to ask him. This is a deeply technically literate person who has
done and continues to do a lot for the development of FidoNet.
MvdV> If there is indeed no one who can clean up the Region then that
Mvdv> is a sad situation...
No one can be better than the current R46C. Why he doesn't do this, you
need to ask him. This is a deeply technically literate person who has
done and continues to do a lot for the development of FidoNet.
Except his basic job as an RC...
2:466/4 fido.snake.mk.ua:24554 88.99.13.226 Ok.
[03:21:05 brorabbit logs]$ whois 88.99.13.226|grep -i country
country: DE
country: DE
country: DE
[03:22:57 brorabbit logs]$ ping fido.snake.mk.ua
PING fido.snake.mk.ua(fido.snake.mk.ua (2a01:4f8:c17:5f5b::2)) 56 data bytes
64 bytes from fido.snake.mk.ua (2a01:4f8:c17:5f5b::2): icmp_seq=1 ttl=49 time=102 ms 64 bytes from fido.snake.mk.ua (2a01:4f8:c17:5f5b::2): icmp_seq=2
ttl=49 time=184 ms
[03:24:32 brorabbit logs]$ ping -c 4 88.99.13.226
PING 88.99.13.226 (88.99.13.226) 56(84) bytes of data.
64 bytes from 88.99.13.226: icmp_seq=1 ttl=51 time=77.1 ms
64 bytes from 88.99.13.226: icmp_seq=2 ttl=51 time=75.7 ms
64 bytes from 88.99.13.226: icmp_seq=3 ttl=51 time=75.9 ms
64 bytes from 88.99.13.226: icmp_seq=4 ttl=51 time=74.9 ms
What does war have to do with it? If the RC itself is not on the
combat, then it should be able to monitor the relevance of the
nodelist.
There is no one there who could do this job better.
Yes.
The nodelist is the base of Fidonet connectivity.
Most of all.
Yes. Among other things, dead souls in the nodelist can influence the results of various types of voting.
No. There is no better sysop for this position now.
Because I was an R46C myself.
Yes.
No one can be better than the current R46C. Why he doesn't do this,
you need to ask him.
This is a deeply technically literate person who has done and
continues to do a lot for the development of FidoNet.
No one can be better than the current R46C. Why he doesn't do
this, you need to ask him. This is a deeply technically literate
person who has done and continues to do a lot for the
development of FidoNet.
Except his basic job as an RC...
Perhaps he has some reasons for this.
2:466/4 fido.snake.mk.ua:24554 88.99.13.226 Ok.
[03:21:05 brorabbit logs]$ whois 88.99.13.226|grep -i country
country: DE
country: DE
country: DE
It's an ip range of Hetzner, a well known hoster.
So the website is still up, but has an expired (lets encrypt)
certificate. (Bad sign)
When I look at the website there is a login page for fidonet points.
So there is some live, but the system seems abandoned by the sysop.
Stas Mishchenkov wrote to Dan Clough <=-
MvdV> If there is indeed no one who can clean up the Region then that
Mvdv> is a sad situation...
No one can be better than the current R46C. Why he doesn't do this, you
need to ask him. This is a deeply technically literate person who has
done and continues to do a lot for the development of FidoNet.
Except his basic job as an RC...
Perhaps he has some reasons for this.
No one can be better than the current R46C. Why he doesn't do
this, you need to ask him. This is a deeply technically literate
person who has done and continues to do a lot for the
development of FidoNet.
Except his basic job as an RC...
Perhaps he has some reasons for this.
Nope. Not if it's been going on for 3+ years as stated in this
thread. No reason can account for that. Should have been fired by
the ZC by now.
Michiel van der Vlist wrote to Dan Clough <=-
No one can be better than the current R46C. Why he doesn't do
this, you need to ask him. This is a deeply technically literate
person who has done and continues to do a lot for the
development of FidoNet.
Except his basic job as an RC...
Perhaps he has some reasons for this.
Nope. Not if it's been going on for 3+ years as stated in this
thread. No reason can account for that. Should have been fired by
the ZC by now.
Easy to say from your POV but what if no one willing+capable+acceptable can be found?
2:466/4 fido.snake.mk.ua:24554 88.99.13.226 Ok.
[03:21:05 brorabbit logs]$ whois 88.99.13.226|grep -i country
country: DE
country: DE
country: DE
It's an ip range of Hetzner, a well known hoster.
[03:22:57 brorabbit logs]$ ping fido.snake.mk.ua
Ping doesn't say much. This is more interesting:
# nmap -A fido.snake.mk.ua
So the website is still up, but has an expired (lets encrypt) certificate. (Bad sign)
When I look at the website there is a login page for fidonet points.
So there is some live, but the system seems abandoned by the sysop.
What does war have to do with it? If the RC itself is not on the
combat, then it should be able to monitor the relevance of the
nodelist.
There is no one there who could do this job better.
Yes.
Nope. Not if it's been going on for 3+ years as stated in this
thread. No reason can account for that. Should have been fired
by the ZC by now.
Easy to say from your POV but what if no one
willing+capable+acceptable can be found?
That's ridiculous. In 3 years? Then a neighboring RC takes on the
nodes, which in this case might be 1-2 actually functioning. Pretty
easy solution, eh?
What does war have to do with it? If the RC itself is not on the
combat, then it should be able to monitor the relevance of the
nodelist.
Do You understand that you are explaining this to a person who is not
far from the front line? ;)
Unfortunately, this is exactly the case.
There is no one there who could do this job better.
It need to be sure that it is indeed a dead network, and not just that
you have no connection to it.
Yes.
So what? ;) We have that we have.
The nodelist is the base of Fidonet connectivity.
No one can be better than the current R46C. Why he doesn't do this,
you need to ask him.
This is a deeply technically literate person who has done and
continues to do a lot for the development of FidoNet.
No one can be better than the current R46C. Why he doesn't do
this, you need to ask him. This is a deeply technically literate
person who has done and continues to do a lot for the
development of FidoNet.
Except his basic job as an RC...
Perhaps he has some reasons for this.
Easy to say from your POV but what if no one
willing+capable+acceptable
can be found?
That's ridiculous. In 3 years? Then a neighboring RC takes on the
nodes, which in this case might be 1-2 actually functioning. Pretty
easy solution, eh?
That's ridiculous. In 3 years? Then a neighboring RC takes on the
nodes, which in this case might be 1-2 actually functioning. Pretty
easy solution, eh?
Unfortunately, this is exactly the case.
There is no one there who could do this job better.
It need to be sure that it is indeed a dead network, and not just that
you have no connection to it.
Yes.
So what? ;) We have that we have.
Michiel van der Vlist wrote to Dan Clough <=-
Nope. Not if it's been going on for 3+ years as stated in this
thread. No reason can account for that. Should have been fired
by the ZC by now.
Easy to say from your POV but what if no one
willing+capable+acceptable can be found?
That's ridiculous. In 3 years? Then a neighboring RC takes on the
nodes, which in this case might be 1-2 actually functioning. Pretty
easy solution, eh?
In a country at war, divided by war, there are no easy solutions. Claiming problems are easy and can be fixed in 24 hours, that is what
is ridiculous. Any "neighbouring RC" would be unacceptable for too many because he/she is perceived to be on the wrong side of the fence.
Stas Mishchenkov wrote to Dan Clough <=-
Easy to say from your POV but what if no one
willing+capable+acceptable
can be found?
That's ridiculous. In 3 years? Then a neighboring RC takes on the
nodes, which in this case might be 1-2 actually functioning. Pretty
easy solution, eh?
When Pavel returned to this position, the first thing he did was the nodelist updating. Why this is not being continued now, you should ask him. Highly likely, there are reasons for that.
The nodelist is the base of Fidonet connectivity.
Yes.
This had happened often before.
Yes, but there are not many of them left.
He has own opinion on this matter and he has already published it.
This is a deeply technically literate person who has done and
continues to do a lot for the development of FidoNet.
binkp.net also.
Try gul@gul.kiev.ua
No.
Except his basic job as an RC...
Perhaps he has some reasons for this.
I don't think so. It will lead to the liquidation of the region.
A much bigger problem is that if a region is disassembled, a
significant number of nodes will be simply turned off by sysops.
This is a strictly technically reasonable decision.
Konstantin Kuzov 2:5019/40 is the host master of g0x.ru. I use the
domain name for free. This is dynamic DNS. It is very well automated
and updates take effect on other DNSes within a minute. Why should I refuse it?
It can't be an option for me. We have a PSTN out only node in our
network to which I must to deliver mail.
Yes. I must.
In other side it is a good case to bring into accordance
the nodelist with FPD
It need to be sure that it is indeed a dead network, and not
just that you have no connection to it.
Did you know how to be be sure under conditions of partial IP address blocking?
It strongly needed. Any node is essential.
Propose the safe way.
In a country at war, divided by war, there are no easy
solutions. Claiming problems are easy and can be fixed in 24
hours, that is what is ridiculous. Any "neighbouring RC" would
be unacceptable for too many because he/she is perceived to be
on the wrong side of the fence.
Not sure where you're getting "within 24 hours", because I didn't say that.
But 3+ years?
Are these sysops and/or RCs/NCs on the front lines firing rifles?
Probably not.
It could/should have been fixed in 3 years, regardless. NC467 would
seem to be the obvious solution to take over 466. Not that difficult.
Michiel van der Vlist wrote to Dan Clough <=-
In a country at war, divided by war, there are no easy
solutions. Claiming problems are easy and can be fixed in 24
hours, that is what is ridiculous. Any "neighbouring RC" would
be unacceptable for too many because he/she is perceived to be
on the wrong side of the fence.
Not sure where you're getting "within 24 hours", because I didn't say that.
No, you didn't say that. I was parafrasing from someone else in your country who claims to be able to solve major war related problems in 24 hours.
But 3+ years?
Yes, that is far too long.
Are these sysops and/or RCs/NCs on the front lines firing rifles?
Probably not.
Not on the front, but cities in Ukraine are constanly bombed. People
are constantly running to he shelters. Actually the whole country is
more or less a war zone...
It could/should have been fixed in 3 years, regardless. NC467 would
seem to be the obvious solution to take over 466. Not that difficult.
You can't judge that from a distance by just looking at the nodelist. Odessa is partly bombed to smithereens. While the system of NC467 seems to be up and running, the sysop may be in no position to take responsibility for another net. Only those in the field can judge that.
Besides, net 466 does not need another NC. It is dead as a doornail. It just needs to be removed.
You can't judge that from a distance by just looking at the
nodelist. Odessa is partly bombed to smithereens. While the
system of NC467 seems to be up and running, the sysop may be in
no position to take responsibility for another net. Only those
in the field can judge that.
No argument, but "those in the field" don't seem to give a fuck.
Besides, net 466 does not need another NC. It is dead as a
doornail. It just needs to be removed.
Agreed. There's the correct solution. Now to just get somebody with
the balls enough to make that happen. Hmmmm.....
This is a strictly technically reasonable decision.
Konstantin Kuzov 2:5019/40 is the host master of g0x.ru. I use the
domain name for free. This is dynamic DNS. It is very well automated
and updates take effect on other DNSes within a minute. Why should I
refuse it?
It can't be an option for me. We have a PSTN out only node in our
network to which I must to deliver mail.
Yes. I must.
In other side it is a good case to bring into accordance
the nodelist with FPD
It need to be sure that it is indeed a dead network, and not
just that you have no connection to it.
Did you know how to be be sure under conditions of partial IP address
blocking?
It strongly needed. Any node is essential.
Propose the safe way.
The nodelist is the base of Fidonet connectivity.
Yes.
This had happened often before.
Yes, but there are not many of them left.
He has own opinion on this matter and he has already published it.
This is a deeply technically literate person who has done and
continues to do a lot for the development of FidoNet.
binkp.net also.
Try gul@gul.kiev.ua
No.
Except his basic job as an RC...
Perhaps he has some reasons for this.
I don't think so. It will lead to the liquidation of the region.
A much bigger problem is that if a region is disassembled, a
significant number of nodes will be simply turned off by sysops.
| Sysop: | Fercho |
|---|---|
| Lugar: | La Plata, Buenos Aires |
| Usuarios: | 30 |
| Nodos: | 10 (0 / 10) |
| Uptime: | 28:17:00 |
| Llamadas: | 123 |
| Archivoss: | 15,607 |
| Mensajes: | 37,809 |
Novedades:
Servidor de Quake 3 Arena Online! - Conectate a ferchobbs.ddns.net, puerto 27960 y vence con tu equipo!