On 2021-11-22 16:00, Paul Koning wrote:
On Nov 21, 2021, at 6:24 PM, Johnny Billquist
<bqt at softjar.se> wrote:
Any Multinet links to Mim.Update.UU.SE are going to have to move. There will be two
alternatives:
.
HECnet-1-1023.Stupi.NET is a PyDECnet router which I intend to be a major hub for
HECnet. Located in Stockholm with good network capacity.
.
Mim.Stupi.NET, which is just the same machine, and can accept the same links.
I'm confused. Those two host names resolve to different addresses.
Mim.stupi.net
seems to be up (it answers pings); hecnet-1023 does not answer ping. So if I have an
existing (Multinet) link to mim, which of these two should it move to?
Pay attention, Paul. :-)
hecnet-1-1023.stupi.net, not hecnet-1023...
But anyway, I think Peter explicitly locked hecnet-1-1023 down so that
it won't answer ping, or most other things. But the Multinet links
should work.
And I have configured much of that PyDECnet instance up so that it
accepts connections with the same parameters as people were using to Mim.
So try just pointing at it, and see if it doesn't just work.
If not, let me know, and we'll sort it out.
And I explicitly asked that
Mim.Stupi.NET not have any kind of
filtering, since I have found that to be a very good debugging tool for
my TCP/IP, not to mention that I do like being able to play around with
different protocols and services.
(And RSX isn't much of a security risk to start with in todays internet...)
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol