Well that makes me happy :)
I just wish there was a way of doing this "properly", i.e. with VMS ...
Sampsa
On 9 Jun 2010, at 01:54, Steve Davidson wrote:
Works for me!
Made it all the way to CHIMPY, logged in, and logged out.
-Steve
Maybe those modems were connected to a DECserver?
Anyway, can you see the B4BBS LAT service I've created? I'd much
appreciate if you could do a test connection to see it actually works
from outside as well.
Sampsa
On 9 Jun 2010, at 01:45, Steve Davidson wrote:
Actually,
The QAR system (bug reporting system for field tests) did have
outbound modems.
What we did to connect to a customer system was LAT to the QAR
system and then
connect with kermit (maybe) to the customer. You had to have an
account on the
QAR system to be able to access the modem pool.
-Steve
On 9 Jun 2010, at 01:27, Gregg Levine wrote:
Hello!
I see.
A good question. Now that I know that it is someone physical where
you
are, I am fresh out of ideas.
This MUST be doable, it's such an obvious idea :)
Let's say back in the day I had a modem connected to one of my VMS
boxes, would not sharing it over LAT be pretty obvious?
Sampsa
Works for me!
Made it all the way to CHIMPY, logged in, and logged out.
-Steve
Maybe those modems were connected to a DECserver?
Anyway, can you see the B4BBS LAT service I've created? I'd much
appreciate if you could do a test connection to see it actually works
from outside as well.
Sampsa
On 9 Jun 2010, at 01:45, Steve Davidson wrote:
Actually,
The QAR system (bug reporting system for field tests) did have
outbound modems.
What we did to connect to a customer system was LAT to the QAR
system and then
connect with kermit (maybe) to the customer. You had to have an
account on the
QAR system to be able to access the modem pool.
-Steve
On 9 Jun 2010, at 01:27, Gregg Levine wrote:
Hello!
I see.
A good question. Now that I know that it is someone physical where
you
are, I am fresh out of ideas.
This MUST be doable, it's such an obvious idea :)
Let's say back in the day I had a modem connected to one of my VMS
boxes, would not sharing it over LAT be pretty obvious?
Sampsa
No such luck on modems being connected to a DECserver.
Hold on... let me check... I be right back...
Steve
Maybe those modems were connected to a DECserver?
Anyway, can you see the B4BBS LAT service I've created? I'd much
appreciate if you could do a test connection to see it actually works
from outside as well.
Sampsa
On 9 Jun 2010, at 01:45, Steve Davidson wrote:
Actually,
The QAR system (bug reporting system for field tests) did have
outbound modems.
What we did to connect to a customer system was LAT to the QAR
system and then
connect with kermit (maybe) to the customer. You had to have an
account on the
QAR system to be able to access the modem pool.
-Steve
On 9 Jun 2010, at 01:27, Gregg Levine wrote:
Hello!
I see.
A good question. Now that I know that it is someone physical where
you
are, I am fresh out of ideas.
This MUST be doable, it's such an obvious idea :)
Let's say back in the day I had a modem connected to one of my VMS
boxes, would not sharing it over LAT be pretty obvious?
Sampsa
Maybe those modems were connected to a DECserver?
Anyway, can you see the B4BBS LAT service I've created? I'd much appreciate if you could do a test connection to see it actually works from outside as well.
Sampsa
On 9 Jun 2010, at 01:45, Steve Davidson wrote:
Actually,
The QAR system (bug reporting system for field tests) did have outbound modems.
What we did to connect to a customer system was LAT to the QAR system and then
connect with kermit (maybe) to the customer. You had to have an account on the
QAR system to be able to access the modem pool.
-Steve
On 9 Jun 2010, at 01:27, Gregg Levine wrote:
Hello!
I see.
A good question. Now that I know that it is someone physical where you
are, I am fresh out of ideas.
This MUST be doable, it's such an obvious idea :)
Let's say back in the day I had a modem connected to one of my VMS
boxes, would not sharing it over LAT be pretty obvious?
Sampsa
Actually,
The QAR system (bug reporting system for field tests) did have outbound modems.
What we did to connect to a customer system was LAT to the QAR system and then
connect with kermit (maybe) to the customer. You had to have an account on the
QAR system to be able to access the modem pool.
-Steve
On 9 Jun 2010, at 01:27, Gregg Levine wrote:
Hello!
I see.
A good question. Now that I know that it is someone physical where you
are, I am fresh out of ideas.
This MUST be doable, it's such an obvious idea :)
Let's say back in the day I had a modem connected to one of my VMS
boxes, would not sharing it over LAT be pretty obvious?
Sampsa
Hmm, I guess, but it needn't be a modem, some other serial device one would like to share over LAT.
In any case, I figured out a way of doing it with latd on my Linux box - not ideal, but better than nothing.
Maybe someone can figure out how to do this using VMS, I'm stumped though.
Sampsa
On 9 Jun 2010, at 01:40, Steve Davidson wrote:
Actually no. This is because no one would be responsible for the long
distance calls/abuse.
-Steve
On 9 Jun 2010, at 01:27, Gregg Levine wrote:
Hello!
I see.
A good question. Now that I know that it is someone physical where you
are, I am fresh out of ideas.
This MUST be doable, it's such an obvious idea :)
Let's say back in the day I had a modem connected to one of my VMS
boxes, would not sharing it over LAT be pretty obvious?
Sampsa
Actually no. This is because no one would be responsible for the long
distance calls/abuse.
-Steve
On 9 Jun 2010, at 01:27, Gregg Levine wrote:
Hello!
I see.
A good question. Now that I know that it is someone physical where you
are, I am fresh out of ideas.
This MUST be doable, it's such an obvious idea :)
Let's say back in the day I had a modem connected to one of my VMS
boxes, would not sharing it over LAT be pretty obvious?
Sampsa
On 9 Jun 2010, at 01:27, Gregg Levine wrote:
Hello!
I see.
A good question. Now that I know that it is someone physical where you
are, I am fresh out of ideas.
This MUST be doable, it's such an obvious idea :)
Let's say back in the day I had a modem connected to one of my VMS boxes, would not sharing it over LAT be pretty obvious?
Sampsa
On Tue, Jun 8, 2010 at 8:25 PM, Sampsa Laine <sampsa at mac.com> wrote:
Gregg,
In this instance I'm testing this on a physical Itanium box running the
OpenVMS 8.4 field test :)
I suppose my question can be generalised as this:
How do I set up a LAT service to share a terminal port from a VMS
system over LAT, in the same way as one would set up reverse LAT on a
DECserver (i.e. create a service that connects to a specified physical
port)?
The steps I followed in this particular case are listed below.
Sampsa
On 9 Jun 2010, at 01:22, Gregg Levine wrote:
On Tue, Jun 8, 2010 at 7:43 PM, Sampsa Laine <sampsa at mac.com> wrote:
Guys,
I want to create a LAT service connected to a virtual terminal port
(created
using TELNET/CREATE) and then when users connect to this service they get
redirected over telnet to the destination.
This is what I tried:
lcp:==$sys$system:latcp
TELNET/CREATE B4BBS 23 1
lcp create port lta1337/application
lcp set port lta1337/port=tna1
lcp create service b4bbs
lcp set port lta1337: /service=b4bbs
However when I connect to the service b4bbs I am not redirected to the
TNA1
telnet connection, but just get the normal log in screen of the host I
created the service on.
Where am I going wrong here?
Sampsa
Hello!
First things first, what are we running here? Also is it running
physical or virtual? That is, did you install the chosen OS into
SIMH/(that) or onto (that), where the phrase means what you chose.
Please do me a favour, and list the steps you followed to create the
contraption in question.
Incidentally Sampsa there's nothing outside your flat today except all
of London.
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
Hello!
I see.
A good question. Now that I know that it is someone physical where you
are, I am fresh out of ideas.
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
Gregg,
In this instance I'm testing this on a physical Itanium box running the OpenVMS 8.4 field test :)
I suppose my question can be generalised as this:
How do I set up a LAT service to share a terminal port from a VMS system over LAT, in the same way as one would set up reverse LAT on a DECserver (i.e. create a service that connects to a specified physical port)?
The steps I followed in this particular case are listed below.
Sampsa
On 9 Jun 2010, at 01:22, Gregg Levine wrote:
On Tue, Jun 8, 2010 at 7:43 PM, Sampsa Laine <sampsa at mac.com> wrote:
Guys,
I want to create a LAT service connected to a virtual terminal port (created
using TELNET/CREATE) and then when users connect to this service they get
redirected over telnet to the destination.
This is what I tried:
lcp:==$sys$system:latcp
TELNET/CREATE B4BBS 23 1
lcp create port lta1337/application
lcp set port lta1337/port=tna1
lcp create service b4bbs
lcp set port lta1337: /service=b4bbs
However when I connect to the service b4bbs I am not redirected to the TNA1
telnet connection, but just get the normal log in screen of the host I
created the service on.
Where am I going wrong here?
Sampsa
Hello!
First things first, what are we running here? Also is it running
physical or virtual? That is, did you install the chosen OS into
SIMH/(that) or onto (that), where the phrase means what you chose.
Please do me a favour, and list the steps you followed to create the
contraption in question.
Incidentally Sampsa there's nothing outside your flat today except all
of London.
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
