Correction:
Make that 13:56:27.29 Eastern (18:56:27.29 UTC).
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of hvlems at zonnet.nl
Sent: Thursday, December 22, 2011 4:23 PM
To: hecnet at Update.UU.SE
Subject: [HECnet] area 44
NIKKEL just lost its system disk. OZON is now the area router.
Did someone see at what time NIKKEL went south, and area 44 with it?
Hans
Hans,
The operator log on SG1:: said 19:15.13 (UTC). Does that sound about
right???
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of hvlems at zonnet.nl
Sent: Thursday, December 22, 2011 4:23 PM
To: hecnet at Update.UU.SE
Subject: [HECnet] area 44
NIKKEL just lost its system disk. OZON is now the area router.
Did someone see at what time NIKKEL went south, and area 44 with it?
Hans
It's NOT nice to shake VAX 2000's, even though it probably needed it!
:-)
Well, I really only wanted to shake the RD54, but it's way too much trouble
to take it out and put it back in again so I hope CHEKOV will forgive me :-)
Regards,
Peter Coghlan.
BTP::PETER
On Thu, 22 Dec 2011 18:36:52 +0100, you wrote:
Speaking of Multinet and DECnet-over-IP. I just got this crazy idea to
implement DECnet-over-IP tunneling in RSX, and it would be fun to be
compatible.
Have anyone analyzed, or read any documentation on how the tunneling is
done? TCP or UDP? Any additional headers or data in the stream in
addition to the encapsulated DECnet packets?
IIRC, you can find a daemon to interface with Multinet tunnels into the
Linux DECnet tools package. That should be a good starting point where to
discover what would be needed to write a new RSX interface, at least in
terms of packet structures and such. :)
HTH,
G.
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Peter Coghlan
Sent: Thursday, December 22, 2011 12:06 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Multinet Tunnel Links defined
Were you able to verify that the new address works? ...
Yes, with
$ mul sho/nosym
and I turned TCPAn on itself and circuit displayed correct node on
the other end :)
--
I can also confirm that this works. I'm well used to changing Multinet
interface ip addresses and other Multinet parameters on production
systems
without rebooting so I was interested to try it. (The only reason I've
ever
found for a reboot is to ensure the startup files have been reconfigured
correctly. I suspect this is why Process recommend it. If I liked
rebooting
things, I'd get a PC)
I set up a DECnet-over-IP link between CEIRE and CHEKOV and turned off
the
SVA-0 circuit on CHEKOV. I made sure that the only DECnet connectivity
was
over the IP link. Then I changed CHEKOVs ip address, reconfigured
DECnet-over-IP and re-established the link. I was then able to SET HOST
across the link. No reboot required.
It took me a while because CHEKOV, my VAX 2000 would not co-operate.
However,
after a good shaking, the RD54 spun up and it booted.
Regards,
Peter Coghlan.
BTP::PETER
It's NOT nice to shake VAX 2000's, even though it probably needed it!
:-)
If no one else does I can once I finish getting things setup.
-brian
On Dec 22, 2011, at 12:45, Johnny Billquist <bqt at softjar.se> wrote:
On 2011-12-22 18.42, Marc Chametzky wrote:
Have anyone analyzed, or read any documentation on how the tunneling
is done? TCP or UDP? Any additional headers or data in the stream in
addition to the encapsulated DECnet packets?
The only thing I know (from configuring my firewall) is that they are
UDP packets on port 700. I haven't looked to see what's inside the
packets, though.
Interesting. Could anyone grab a bunch of frames with tcpdump and send to me?
Johnny
On 2011-12-22 18.42, Marc Chametzky wrote:
Have anyone analyzed, or read any documentation on how the tunneling
is done? TCP or UDP? Any additional headers or data in the stream in
addition to the encapsulated DECnet packets?
The only thing I know (from configuring my firewall) is that they are
UDP packets on port 700. I haven't looked to see what's inside the
packets, though.
Interesting. Could anyone grab a bunch of frames with tcpdump and send to me?
Johnny
Have anyone analyzed, or read any documentation on how the tunneling is done? TCP or UDP? Any additional headers or data in the stream in addition to the encapsulated DECnet packets?
The only thing I know (from configuring my firewall) is that they are UDP packets on port 700. I haven't looked to see what's inside the packets, though.
--Marc
