2 Oct
2015
2 Oct
'15
2:49 a.m.
For those with Multinet links to LEGATO, it now has a new IP -
75.54.216.98. However as always you don't need to remember the IP; you can
just do an nslookup on decnet.jfcl.com and that'll be the right answer.
Please update the link on your end.
It looks like the link to FRUGAL is already up - I'm not sure how Fred
managed that trick, but good for him!
Bob
2 Oct
2 Oct
2:14 p.m.
On Thu, 1 Oct 2015, Robert Armstrong wrote:
? For those with Multinet links to LEGATO, it now has a new IP ?
75.54.216.98.?? However as always you don?t need to remember the IP; you can
just do an nslookup on decnet.jfcl.com and that?ll be the right answer.
I am going to file this message just in case the link falls over, however
- the relevant line from decnet-circuits.com shows the old IP with the
undocumented use tcp trick still enabled.
multinet set/decnet/remote=64.142.52.93 /device=tcpc0:/connect/tcp=listen
However, ncp says the circuit is up:
TCP-2-0 on 2.1 (LEGATO)
I've made NO changes and just saw Bob's message this morning.
There's no chance it could be lying, could it?
Fred
3:18 p.m.
multinet set/decnet/remote=64.142.52.93
/device=tcpc0:/connect/tcp=listen
This just occurred to me - you know what it is?? Since it's TCP and your
end is passive (i.e. "listen") then LEGATO is initiating the connection.
Your end doesn't care what my IP is. For UDP, both ends would need to know
the correct IP of the other end.
Hmm... I didn't realize that would happen, but it's good to know.
It might actually work if you don't specify /REMOTE at all - if you're
ambitious, you could try and see. In any case, that old IP is wrong and you
should change it somehow.
Bob
3:39 p.m.
On Fri, 2 Oct 2015, Robert Armstrong wrote:
This just occurred to me - you know what it is??
Since it's TCP and your
end is passive (i.e. "listen") then LEGATO is initiating the connection.
Your end doesn't care what my IP is. For UDP, both ends would need to know
the correct IP of the other end.
Gotcha, makes sense.
That thought occurred to me also after I sent the initial reply.
ambitious, you could try and see. In any case, that
old IP is wrong and you
should change it somehow.
I will change it now but am going to leave FRUGAL alone as far as reboots
go.
Fred
8:54 p.m.
On 2 Oct 2015, at 14:39, Fred <fcoffey at misernet.net> wrote:
On Fri, 2 Oct 2015, Robert Armstrong wrote:
Fred, could you try keeping the host, LEGATO and install etc, it's our mail
in/out gateway?
This just occurred to me - you know what it is??
Since it's TCP and your
end is passive (i.e. "listen") then LEGATO is initiating the connection.
Your end doesn't care what my IP is. For UDP, both ends would need to know
the correct IP of the other end.
Gotcha, makes sense.
That thought occurred to me also after I sent the initial reply.
ambitious, you could try and see. In any case,
that old IP is wrong and you
should change it somehow.
I will change it now but am going to leave FRUGAL alone as far as reboots go.
Fred
8:59 p.m.
On Fri, 2 Oct 2015, Sampsa Laine wrote:
Fred, could you try keeping the host, LEGATO and
install etc, it's our
mail in/out gateway?
%DCL-MEM-BAD, bad memory
VMS-F-PDGERS, pudding between the ears
:)
I read your message more than once and could not understand what you were
trying to convery. Bob owns LEGATO - I do not. We were just discussing
the multinet link between our two sites.
Fred
9 p.m.
I was told that LEGATO is..
On 2 Oct 2015, at 19:54, Sampsa Laine <sampsa at mac.com> wrote:
On 2 Oct 2015, at 14:39, Fred <fcoffey at misernet.net> wrote:
On Fri, 2 Oct 2015, Robert Armstrong wrote:
Fred, could you try keeping the host, LEGATO and install etc, it's our mail
in/out gateway?
This just occurred to me - you know what it is??
Since it's TCP and your
end is passive (i.e. "listen") then LEGATO is initiating the connection.
Your end doesn't care what my IP is. For UDP, both ends would need to know
the correct IP of the other end.
Gotcha, makes sense.
That thought occurred to me also after I sent the initial reply.
ambitious, you could try and see. In any case,
that old IP is wrong and you
should change it somehow.
I will change it now but am going to leave FRUGAL alone as far as reboots go.
Fred
9:06 p.m.
For those with Multinet links to LEGATO, it now has
a new IP -
75.54.216.98.
Request # 20; Show Known Circuits Summary Completed
Circuit State Loopback Adjacent
Name Node
QNA-0 On 59.60 (R29GWA)
QNA-0 59.10 (SOL)
QNA-1 On
TCP-0-0 On 2.1 (LEGATO)
I have a bunch of other IP's in there that has no_one on the other
side, and I forgot...
$!decnet-config: circuit-name TCP-0-1
$!decnet-config: destination-ip-address TCP-0-1 188.220.63.6
$!decnet-config: cost TCP-0-1 5
$!decnet-config: hello-timer TCP-0-1 300
$!
$!decnet-config: circuit-name TCP-0-2
$!decnet-config: destination-ip-address TCP-0-2 69.21.253.158
$!decnet-config: cost TCP-0-2 5
$!decnet-config: hello-timer TCP-0-2 300
$!
$!decnet-config: circuit-name TCP-0-3
$!decnet-config: destination-ip-address TCP-0-3 80.6.148.150
$!decnet-config: cost TCP-0-3 5
$!decnet-config: hello-timer TCP-0-3 300
--P
9:12 p.m.
So is anyone else run a mailserver that transates address like this
user@@chimpy.decnet.org
Sampsa
On 2 Oct 2015, at 20:06, Peter Lothberg <roll at Stupi.SE> wrote:
For those
with Multinet links to LEGATO, it now has a new IP -
75.54.216.98.
Request # 20; Show Known Circuits Summary Completed
Circuit State Loopback Adjacent
Name Node
QNA-0 On 59.60 (R29GWA)
QNA-0 59.10 (SOL)
QNA-1 On
TCP-0-0 On 2.1 (LEGATO)
I have a bunch of other IP's in there that has no_one on the other
side, and I forgot...
$!decnet-config: circuit-name TCP-0-1
$!decnet-config: destination-ip-address TCP-0-1 188.220.63.6
$!decnet-config: cost TCP-0-1 5
$!decnet-config: hello-timer TCP-0-1 300
$!
$!decnet-config: circuit-name TCP-0-2
$!decnet-config: destination-ip-address TCP-0-2 69.21.253.158
$!decnet-config: cost TCP-0-2 5
$!decnet-config: hello-timer TCP-0-2 300
$!
$!decnet-config: circuit-name TCP-0-3
$!decnet-config: destination-ip-address TCP-0-3 80.6.148.150
$!decnet-config: cost TCP-0-3 5
$!decnet-config: hello-timer TCP-0-3 300
--P
3154
days inactive
3154
days old
8 comments
4 participants
participants (4)
-
bob＠jfcl.com -
fcoffey＠misernet.net -
roll＠Stupi.SE -
sampsa＠mac.com