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
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?
Johnny
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
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 :)
--
Regards, Rok
Rok,
Were you able to verify that the new address works? If I test this then
I will actually need one of the remote addresses to change. This is not
something I wish to ask of the two sites that currently make use of
dynamic-DNS. What I may do is setup one of my other machines with
Multinet and then move it to another of the static addresses here to see
what happens. That will take a bit more effort so it may have to wait
until the weekend.
Also, I can't remember if I wrote MultiWatch for V5.2, or V5.3 - it's
been in use that long... This could explain the difference. I just
don't remember. Maybe, Fred remembers - his site was the reason for the
procedure in the first place. Fred???
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Rok Vidmar
Sent: Thursday, December 22, 2011 11:07 AM
To: hecnet at update.uu.se
Subject: Re: [HECnet] Multinet Tunnel Links defined
I wonder if what I saw was VAX specific??? ...
No way for me to test now. As a bonus I found out that
$ multinet set/decnet/remote=new_IP_NAME/device=TCPAn:/connect
work as well as
$ multinet set/decnet/remote=new_IP_ADDR/device=TCPAn:/connect
--
Regards, Rok
I wonder if what I saw was VAX specific??? ...
No way for me to test now. As a bonus I found out that
$ multinet set/decnet/remote=new_IP_NAME/device=TCPAn:/connect
work as well as
$ multinet set/decnet/remote=new_IP_ADDR/device=TCPAn:/connect
--
Regards, Rok
Rok,
I wonder if what I saw was VAX specific??? I will try this later this evening so it has minimal impact.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Rok Vidmar
Sent: Thursday, December 22, 2011 10:03 AM
To: hecnet at update.uu.se
Subject: Re: [HECnet] Multinet Tunnel Links defined
$ ncp set circ TCP-0-n sta off>> $ multinet set/decnet/remote=new_IP_addr/device=TCPAn:/connect>> $ ncp set circuit TCP-0-n state on cost 9 hello timer 300>
If I remember right Multinet caches the IP address and
does not flush it. Let's not forget that Process Software
does not support anything but a reboot!
My method works for me. Tested with MultiNet V5.3 on
FreeAXP OpenVMS V8.4.
--
Regards, Rok
$ ncp set circ TCP-0-n sta off>> $ multinet set/decnet/remote=new_IP_addr/device=TCPAn:/connect>> $ ncp set circuit TCP-0-n state on cost 9 hello timer 300>
If I remember right Multinet caches the IP address and
does not flush it. Let's not forget that Process Software
does not support anything but a reboot!
My method works for me. Tested with MultiNet V5.3 on
FreeAXP OpenVMS V8.4.
--
Regards, Rok
