BBS:      TELESC.NET.BR
Assunto:  Re: Not working IPv4. Article as published in Fidonews
De:       Dan Clough
Data:     Mon, 4 May 2026 08:31:31 -0500
-----------------------------------------------------------
-=> Michiel van der Vlist wrote to Stephen Walsh <=-

 MV>> 3:770/1 for example has been unreachable via IPv4 for almost two
 MV>> months now.

 SW> That's a bit unfair. Paul has been in the process of moving, and that
 SW> is not something that happens over night. Even the best laid plans
 SW> sometimes fail.

 MvV> Of course, shit happens all the time. But this wasn't meant as an
 MvV> attack on Paul or any other sysop. 3:770/1 was just an example and the
 MvV> core of my article was not the fact that connection failures with IPv4
 MvV> happen, but the fact that they seem to go unnoticed for some time and
 MvV> everything just keeps working anyway. Via IPv6.

 MvV> I get my information from the site of Dmitry Protasoff:

 MvV> https://nodelist.fidonet.cc/analytics/ipv6-only

 MvV> Scroll down to the node in question and click on "history" on the
 MvV> right.

 MvV> I can not explain why you manage to make an IPv4 connect and Dmitry's
 MvV> system does not.

It seems that *MANY* (perhaps even ALL) people other than Dmitry can 
make an IPv4 connect...  Hmmmm, where could the problem be?



... Gone crazy, be back later, please leave message.
=== MultiMail/Linux v0.52
--- SBBSecho 3.37-Linux
 * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)

-----------------------------------------------------------
[Voltar]