>I know I'm going to sound all Web2.0 and stuff, but maybe a Wiki + a blog that announces new posts to the Wiki?
Actually, a Wiki with some documentation would be a great idea.
But it s the same answer I m just offering the domain name; somebody else has to set up the machine and service.
Bob
One is just a DNS entry, the other is a machine. :-)
Right (!!). I'll set up the DNS pointer - you set up the machine :-)
Seriously - let me know the IP and I'll add the DNS entry.
Bob
On 26 Jun 2012, at 20:56, Johnny Billquist wrote:
Some place that explains what HECnet is, how to join, have the bridge program (and other stuff linked), links to other pages relevant to HECnet (or DECnet), and whatnot...
But that requires that someone runs the service, and keeps it up to date and running...
I suppose I *could*, but if someone else feels a bit more driven, that would be good. I'm not good at web design, or user interfaces in general. I'm way more into the technical details of things...
I know I'm going to sound all Web2.0 and stuff, but maybe a Wiki + a blog that announces new posts to the Wiki?
That way people could collaborate on the material instead of leaving it up to one person.
Installing a basic Wordpress + Mediawiki site (at least using my hosting) is like 20 mins of work...
Sampsa
On 2012-06-26 19:46, Kari Uusim ki wrote:
On 26.6.2012 18:16, Bob Armstrong wrote:
I own the domain decnet.org I have for several years, but I
haven t really done anything with it. Is there any interest in using
it for HECnet somehow? We could, for example, give all the machines
that have TCP/IP connectivity name.decnet.org aliases. Or we could
set up mail forwarding for somebody at decnet.org
<mailto:somebody at decnet.org>. Or we could have a web page at
www.decnet.org <http://www.decnet.org>. Or maybe somebody can think of
something else. I m also willing to transfer the name if somebody can
promise to put it to good use. I don t want any money for it, but I
would like to see it get used.
Bob
Great idea!
Why not use it for connectivity to the outside world from HECnet? There
could be a gateway which translates the names and - if needed - DECnet
to TCP/IP and vice versa. DEC used to have an alias domain
(enet.dec.com) for the internal machines so that they could connect to
hosts outside the internal network.
I should point out that DNS is not the same as having a gateway. One is just a DNS entry, the other is a machine. :-)
That said, I wouldn't mind if we could come up with something useful for this. Having it point to somewhere where we can collect all resources in a better way would be nice.
Some place that explains what HECnet is, how to join, have the bridge program (and other stuff linked), links to other pages relevant to HECnet (or DECnet), and whatnot...
But that requires that someone runs the service, and keeps it up to date and running...
I suppose I *could*, but if someone else feels a bit more driven, that would be good. I'm not good at web design, or user interfaces in general. I'm way more into the technical details of things...
Johnny
On 26.6.2012 18:16, Bob Armstrong wrote:
I own the domain decnet.org I have for several years, but I
haven t really done anything with it. Is there any interest in using
it for HECnet somehow? We could, for example, give all the machines
that have TCP/IP connectivity name.decnet.org aliases. Or we could
set up mail forwarding for somebody at decnet.org
<mailto:somebody at decnet.org>. Or we could have a web page at
www.decnet.org <http://www.decnet.org>. Or maybe somebody can think of
something else. I m also willing to transfer the name if somebody can
promise to put it to good use. I don t want any money for it, but I
would like to see it get used.
Bob
Great idea!
Why not use it for connectivity to the outside world from HECnet? There could be a gateway which translates the names and - if needed - DECnet to TCP/IP and vice versa. DEC used to have an alias domain (enet.dec.com) for the internal machines so that they could connect to hosts outside the internal network.
Kari
I own the domain decnet.org I have for several years, but I haven t really done anything with it. Is there any interest in using it for HECnet somehow? We could, for example, give all the machines that have TCP/IP connectivity name.decnet.org aliases. Or we could set up mail forwarding for somebody at decnet.org. Or we could have a web page at www.decnet.org. Or maybe somebody can think of something else. I m also willing to transfer the name if somebody can promise to put it to good use. I don t want any money for it, but I would like to see it get used.
Bob
Igor
I d be happy to have LEGATO connect to you with a Multinet tunnel. Since you are going to operate as a Level 1 router, that means you will have to be in the same area as LEGATO. That s not a problem since there s plenty of address space available, and I ll just reserve you a block from 2.300 thru 2.309. Sounds like you only have three machines, so that should be plenty.
You ll need to register your node names with Johnny (just email them to this list) so he can add them to the master database.
Send me an email off list when you have Multinet set up on your end and I ll turn on the link.
Bob Armstrong
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Mirvaleev Igor (????????? ????? ????????????) Sent: Tuesday, June 26, 2012 1:15 AM To: hecnet at Update.UU.SE Subject: [HECnet] Connect to HECnet
Hello all!
I would like to connect my 3 machines to HECnet.
One of them i plan to configure as Level1 router and connect to HECnet using Multinet or TCPware under OpenVMS.
Is anybody, who use the same software, can connect my machines to its area?
Machines located in Moscow, my static IP is 81.200.30.73
Thanks,
Igor
Hello all!
I would like to connect my 3 machines to HECnet.
One of them i plan to configure as Level1 router and connect to HECnet using Multinet or TCPware under OpenVMS.
Is anybody, who use the same software, can connect my machines to its area?
Machines located in Moscow, my static IP is 81.200.30.73
Thanks,
Igor
No. Some mails from Hans was encoded in Base64. If you didn't see that,
then there is something going on at your side to hide it.
But I think Hans solved this.
Johnny helped me do some testing and it turns out that there was indeed
something going on at my side to hide it. My PMDF mailserver was silently
removing the redundant base64 encoding so I never got to see it which is
why I was so puzzled. Apologies for spreading my confusion to the list
without checking further.
Regards,
Peter Coghlan.
