Sampsa Laine wrote:
I'm starting to get concerned that HECnet is almost running TOO well, i.e. there's not much left to tweak :)
Where should we go from here? Setting up our own virtual X.25 PSDN tunnelled over IP maybe? Something crazy with SNA?
HECnet have been running fine for a long, long time by now. :-)
But there are definitely things to look at.
Ideally if would be very nice to implement an alternative to my bridge program which actually routes instead of bridging. But that would take a lot of work, and I definitely don't have time for that right now.
Ideally it should also be able to talk with the Cisco implementation in this case.
And of course, people could think about writing bridge programs for things like PHONE <-> talk, ftp gateways, and other stuff, if they feel like getting a project. There is much to play around with.
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
Set that up before you joined HECnet I'm guessing, and forgot it was in place when you did :)
Sampsa
On 21 Oct 2009, at 10:21, Christine Caulfield wrote:
On 21/10/09 10:07, Sampsa Laine wrote:
Does ROOSTA have a proxy setup for the SYSTEM user? When I DIR ROOSTA
from RHESUS (as SYSTEM), I seem to get your SYS$MANAGER: directory....
Eek!
I had *::* */def
I have now removed it!
Chrissie
On 21 Oct 2009, at 10:05, Christine Caulfield wrote:
On 21/10/09 00:26, Bob Armstrong wrote:
I took Sampsa's suggestion and put an INFO.TXT on CODA with a machine
readable section at the end that contains information about the local
nodes.
I already wrote a little DCL script that crawls the HECnet and
collects all
the INFO.TXT files that it can find (so far there are eight, counting
mine)
and if enough people adopt this format I'll write another little
script to
parse out the node information.
The format is pretty straight forward - you can just type out
CODA::INFO.TXT and see for yourself.
I've added an INFO.TXT to ROOSTA
Chrissie
On 21/10/09 10:07, Sampsa Laine wrote:
Does ROOSTA have a proxy setup for the SYSTEM user? When I DIR ROOSTA
from RHESUS (as SYSTEM), I seem to get your SYS$MANAGER: directory....
Eek!
I had *::* */def
I have now removed it!
Chrissie
On 21 Oct 2009, at 10:05, Christine Caulfield wrote:
On 21/10/09 00:26, Bob Armstrong wrote:
I took Sampsa's suggestion and put an INFO.TXT on CODA with a machine
readable section at the end that contains information about the local
nodes.
I already wrote a little DCL script that crawls the HECnet and
collects all
the INFO.TXT files that it can find (so far there are eight, counting
mine)
and if enough people adopt this format I'll write another little
script to
parse out the node information.
The format is pretty straight forward - you can just type out
CODA::INFO.TXT and see for yourself.
I've added an INFO.TXT to ROOSTA
Chrissie
Does ROOSTA have a proxy setup for the SYSTEM user? When I DIR ROOSTA from RHESUS (as SYSTEM), I seem to get your SYS$MANAGER: directory....
On 21 Oct 2009, at 10:05, Christine Caulfield wrote:
On 21/10/09 00:26, Bob Armstrong wrote:
I took Sampsa's suggestion and put an INFO.TXT on CODA with a machine
readable section at the end that contains information about the local nodes.
I already wrote a little DCL script that crawls the HECnet and collects all
the INFO.TXT files that it can find (so far there are eight, counting mine)
and if enough people adopt this format I'll write another little script to
parse out the node information.
The format is pretty straight forward - you can just type out
CODA::INFO.TXT and see for yourself.
I've added an INFO.TXT to ROOSTA
Chrissie
On 21/10/09 00:26, Bob Armstrong wrote:
I took Sampsa's suggestion and put an INFO.TXT on CODA with a machine
readable section at the end that contains information about the local nodes.
I already wrote a little DCL script that crawls the HECnet and collects all
the INFO.TXT files that it can find (so far there are eight, counting mine)
and if enough people adopt this format I'll write another little script to
parse out the node information.
The format is pretty straight forward - you can just type out
CODA::INFO.TXT and see for yourself.
I've added an INFO.TXT to ROOSTA
Chrissie
I can't connect to the FAL listener (terminology?) on BUBBLE from either RHESUS or CHIMPY - SET HOST works however..
Sampsa
On 21 Oct 2009, at 08:43, Mark Wickens wrote:
I now get the following error when I use the hecnetinfo script:
Node queried *|bubble|*
%TYPE-W-READERR, error reading BUBBLE::SYS$SPECIFIC:[FAL$SERVER]INFO.TXT;3
-RMS-F-SYS, QIO system service request failed
-SYSTEM-F-LINKEXIT, network partner exited
%TYPE-W-CLOSEIN, error closing BUBBLE::SYS$SPECIFIC:[FAL$SERVER]INFO.TXT;3 as input
-RMS-F-WBE, error on write behind
-SYSTEM-F-LINKABORT, network partner aborted logical link
------------------------------------------------------------------------
Is there something wrong with the file format? I can TYPE BUBBLE::INFO.TXT no problem.
$ dir/full bubble::info.txt
Directory BUBBLE::SYS$SPECIFIC:[FAL$SERVER]
INFO.TXT;3 File ID: None
Size: 3/9 Owner: [376,373]
Created: 21-OCT-2009 08:29:28.19
Revised: 21-OCT-2009 08:29:28.29 (1)
Expires: <None specified>
Backup: <No backup recorded>
Effective: <None specified>
Recording: <None specified>
File organization: Sequential
Shelved state: (remote)
Caching attribute: (remote)
File attributes: Allocation: 9, Extend: 0, Global buffer count: 0, Version limit: 0
Record format: Variable length, maximum 0 bytes, longest 135 bytes
Record attributes: Carriage return carriage control
RMS attributes: None
Journaling enabled: None
File protection: System:RWED, Owner:RWED, Group:RE, World:
Access Cntrl List: None
Client attributes: None
Total of 1 file, 3/9 blocks.
Yes, I'd second that and anyway, I've rewritten my INFO.TXT now ;)
Regards, Mark.
\
Sampsa Laine wrote:
Why? What would that accomplish that the pipe separated format doesn't except make things uglier? The reason I chose the pipe symbol is because this way we don't have to quote strings as people very seldomly use pipe symbols, but do use commas all the time...
On 21 Oct 2009, at 02:15, Steve Davidson wrote:
Let's try this again...
Any chance this could be in comma separated format? Put strings in
quotes if necessary.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Sampsa Laine
Sent: Tuesday, October 20, 2009 19:43
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] HECnet crawler and INFO.TXT
I've updated CHIMPY in the same format.
Sampsa
On 21 Oct 2009, at 00:26, Bob Armstrong wrote:
I took Sampsa's suggestion and put an INFO.TXT on CODA with a
machine
readable section at the end that contains information about the
local nodes.
I already wrote a little DCL script that crawls the HECnet and
collects all
the INFO.TXT files that it can find (so far there are eight,
counting mine)
and if enough people adopt this format I'll write another little
script to
parse out the node information.
The format is pretty straight forward - you can just type out
CODA::INFO.TXT and see for yourself.
Bob
Why? What would that accomplish that the pipe separated format doesn't except make things uglier? The reason I chose the pipe symbol is because this way we don't have to quote strings as people very seldomly use pipe symbols, but do use commas all the time...
On 21 Oct 2009, at 02:15, Steve Davidson wrote:
Let's try this again...
Any chance this could be in comma separated format? Put strings in
quotes if necessary.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Sampsa Laine
Sent: Tuesday, October 20, 2009 19:43
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] HECnet crawler and INFO.TXT
I've updated CHIMPY in the same format.
Sampsa
On 21 Oct 2009, at 00:26, Bob Armstrong wrote:
I took Sampsa's suggestion and put an INFO.TXT on CODA with a
machine
readable section at the end that contains information about the
local nodes.
I already wrote a little DCL script that crawls the HECnet and
collects all
the INFO.TXT files that it can find (so far there are eight,
counting mine)
and if enough people adopt this format I'll write another little
script to
parse out the node information.
The format is pretty straight forward - you can just type out
CODA::INFO.TXT and see for yourself.
Bob
Tina is up and running, I just telnet:ed in from another machine on the
same network. But I can't connect from home. I'll investigate further.
/P
Mark Abene wrote:
DNS wasn't my problem, I do resolve to the new address. But it still
cannot be telneted to. Unreachable. I suspect a routing issue on the
remote side, if in fact TINA is up.
-Mark
Pontus Pihlgren wrote:
On Mon, Oct 19, 2009 at 03:16:27PM -0400, Mark Abene wrote:
While we're on the subject, PAMINA is unreachable via telnet, and I
haven't been able to telnet into TINA in almost 2 weeks. Any idea
what's been happening at update? I miss TINA's othello. :)
TINA has moved to 130.238.12.208 (from 130.238.8.42). The DNS entries
should be updated by now. I guess Bj rn forgon to tell hecnet at update :)
/Pontus
Thanks,
Mark
Johnny Billquist wrote:
Oh, you want updates? :-)
Let's see...
FNATTE have been decomissioned for good, I think.
PONDUS is now an 11/93 with 4 MB.
PAMINA is also KLH-10
Johnny
Bob Armstrong wrote:
Where is PDXVAX still noted as a 4000/VLC?
Well, on my list for one.
http://www.sparetimegizmos.com/Downloads/DCN%20Node%20List.pdf
Nobody sent me any corrections ...
Bob
