30 Aug
2018
30 Aug
'18
12:04 a.m.
On Wed, Aug 29, 2018, at 10:25 AM, Grant Taylor via TUHS wrote:
On 08/29/2018 07:46 AM, William Pechter wrote:
Hmm. I hate to bring this up, but I've been using the name RetroNET as well.
I've had the domain retronet.net registered for ages, and was about to launch a small
pilot project with a handful of 3B2 emulators running SVR3, with the hope for many more
interconnected systems.
That said, maybe we could pool our efforts? I'd be happy to share the domain name
with this effort, since it's precisely in line with what I'd like to see.
-Seth
--
Seth Morabito
Poulsbo, WA
web(a)loomcom.com
Also... If you run on the internet remember
documented security exploits
are decades old. I recommend no open ports except for ssh if it will
build and maybe UUCP.
I'm working on a Retro Computing Networking project with a few other
people and I think it would be a benefit for things like running 4.3 BSD
and other old OSs in a relatively safe environment.
I'm bringing this up on TUSH for two reasons:
1) I think THUS members could benefit from RetroNet
2) I (we) would very much appreciate any suggestions or desires that
the THUS community would like to see in such a network.
The idea behind RetroNet is two fold:
1) Create a network of interconnected VPNs between interested parties.
2) Provide ISP like services over said interconnections.
Our hopes are for RetroNet to be able to provide a sandbox / small pool
/ isolated network where members can interconnect with each other (if
they want to) similar to the Internet, but with much less exposure. (We
are planing on RetroNet not having direct Internet connectivity.) We
are also hoping and planing to be able to carry any Ethernet based
traffic between sites, routed or not.
I (we) would be very interested in any input that THUS members might be
able to provide. Particularly what you might like to see in such a network.