21 Feb
2023
21 Feb
'23
12:38 a.m.
Hi.
On 2023-02-21 00:21, Keith Halewood wrote:
Hi,
I’ve just noticed that nodes 29.600-699 had been allocated to someone
and they’ve since disappeared from the HECnet node database… or possibly
I imagined the whole thing… except for the fact that I had an inbound
multinet circuit for nodes in that range. I’ve just removed thecircuit
and the firewall ACL for incoming on TCP port 9604. The circuit hadn’t
been used in some time.
29.600 - 699 have never been defined on my side. But, that said, there
is nothing preventing that it might have been defined locally by you in
the past, and then that got lost when copying over a new version from my db.
In no other particular order of peers:
29.400-403 (Ales Petan) has been gone a while.
29.450-469 (Trevor Warwick) similarly.
46.1-9 (Douglas Hall) has been gone for quite a long time.
Not heard anything from any of them in a while, and no idea what they
might be up to. But then again, most people/machines on HECnet are
usually not up.
52.* (Brian Hechinger) has been down for a few weeks…
and has changed
incoming IP address once or twice too.
Brian is definitely still active in general. Maybe some internet issues
with his ISP?
I’m not complaining, just wondering. Known areas are
going darkat a
rate greater than 0 too.
At the moment, it's a bit on the lower side, but as noted above,
majority of nodes and areas are usually not online. It would indeed be
fun with more activity, but every user has his own priorities and
constraints. So I'm just happy to see that we are operational, and there
is some activity.
Oh, and ANKE (1.1023) went >BANG< a few days
ago.
Yeah. I know. :-(
Waiting for Peter to restore my access to the host of that, so I can
kick it. I suspect I managed to trigger some kind of bug in PyDECnet
when talking NICE to it...
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt(a)softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol