Subj : Re: FidoNews submission
To : Bj�rn Felten
From : Dan Clough
Date : Fri May 30 2025 08:05 am
-=> Bj�rn Felten wrote to Dan Clough <=-
BF>> Yes, Massa Gimme-Gimme. I will, of course, immediately see if I can
BF>> give your Very Important Traffic on a depreciated network protocol,
BF>> such as IPv4, higher priority.
DC> It's a world-wide standard, in widespread use.
BF> It was.
Yes, and it still is, whether you like it or not.
BF> A standard from 1981, when the web was more than a decade
BF> from being introduced and worldwide (sic) internet adoption was still
BF> another decade away.
None of that has anything to do with the subject at hand. Classic
deflection attempt by somebody who's "out of ammo".
To remind you - we're talking about how your system doesn't answer binkp
connection attempts. If your system doesn't accept IPv4 connections,
you should be indicating that with your nodelist entry.
DC> Also, I wasn't asking for
DC> higher priority, just that your system match what it advertises as it's
DC> capabilities. CM/IBN/INA. There aren't any "busy signals".
BF> What signals were they then? If you had quoted the errors you
BF> received, it might have helped you identify the problem.
The "error" reported was "Unable to connect to el.jackoff.se" . That's
it. Your system doesn't answer incoming connection attempts.
DC> Why would it affect them at all? Are you using some kind of deprecated
DC> hardware, or something?
BF> You have no idea about my system, so why even try to tell me how to
BF> operate it?
Another non-answer. The question is (again): Why does your system not
accept incoming calls, as advertised?
DC> Strange how your system(s) are so unreliable.
BF> Not to any of my paying clients or free-of-charge important Fidonet
BF> friends, as far as I know. Yes, I know that there still are some IPv4
BF> problems, but it does not seem to be a problem for all of them since
BF> they all use IPv6; therefore, my IPv6 theory. If you have any other
BF> explanation, I'm all ears.
I have the explanation. Your system doesn't support incoming IPv4
connections, and yet, your nodelist entry doesn't specify that. Either
fix your hardware, or update your nodelist entry. Simple, eh?
... So easy, a child could do it. Child sold separately.
=== MultiMail/Linux v0.52
--- SBBSecho 3.25-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
