Johnny Billquist wrote:
However, at the moment PONDUS is turned off. I'm in the US for three
weeks, and figured that I might spear my wife the hum of PONDUS when I'm
not around. :-)
Whereabouts? Is there a chance of a get-together?
Peace... Sridhar
Johnny,
That's the weird thing, my bridge link to you is up and I can see e.g. CTAKAH fine - just none of your systems...
Sampsa
On 12 Jun 2010, at 00:02, Johnny Billquist wrote:
Please do.
As a side note, if psilo.update.uu.se is down, then nothing of the bridged network will work, since that is the true hub of things.
MIM and PONDUS can both be working perfectly fine, but without psilo they can't even talk to each other.
However, at the moment PONDUS is turned off. I'm in the US for three weeks, and figured that I might spear my wife the hum of PONDUS when I'm not around. :-)
All that said, I can't seem to get contact with psilo either right now, so it do seem to be some general network problems somewhere.
Johnny
Pontus Pihlgren wrote:
Hmm, there seems to be some issues with our network in general.. I'll se what I can do.
On Fri, Jun 11, 2010 at 11:31:40PM +0100, Sampsa Laine wrote:
Is MIM down? I can't see it (or PONDUS)..
Sampsa
Please do.
As a side note, if psilo.update.uu.se is down, then nothing of the bridged network will work, since that is the true hub of things.
MIM and PONDUS can both be working perfectly fine, but without psilo they can't even talk to each other.
However, at the moment PONDUS is turned off. I'm in the US for three weeks, and figured that I might spear my wife the hum of PONDUS when I'm not around. :-)
All that said, I can't seem to get contact with psilo either right now, so it do seem to be some general network problems somewhere.
Johnny
Pontus Pihlgren wrote:
Hmm, there seems to be some issues with our network in general.. I'll se what I can do.
On Fri, Jun 11, 2010 at 11:31:40PM +0100, Sampsa Laine wrote:
Is MIM down? I can't see it (or PONDUS)..
Sampsa
Hmm, there seems to be some issues with our network in general.. I'll se
what I can do.
On Fri, Jun 11, 2010 at 11:31:40PM +0100, Sampsa Laine wrote:
Is MIM down? I can't see it (or PONDUS)..
Sampsa
On Thu, 2010-06-10 at 19:29 -0600, Johnny Billquist wrote:
It might be that someone have already done so. It might be worth
searching through old DECUS libraries...
... and that's always fun!
The irony of history.
LAT and DECservers were invented so that machines no longer would need to have local ports.
Now you are using LAT and DECservers to access machine local ports. :-)
Yes. I know what you mean, and what you want to do. However, DEC did definitely not envisage that. Their intention was the exact opposite.
All that said, it is mostly doable under VMS, but it requires that you write some software yourself.
It might be that someone have already done so. It might be worth searching through old DECUS libraries...
Johnny
Sampsa Laine wrote:
No I see how my way of doing it might seem backwards, I mean why share a modem from a host machine when terminal servers were invented for doing it?
Doesn't mean it wouldn't be a nice feature to have :)
Sampsa
On 11 Jun 2010, at 01:36, Johnny Billquist wrote:
What pays to remember is that once you had LAT and DECservers, you didn't use serial ports on your VAX anymore, especially not on a site where you had several VAXen. You *obviously* had DECservers if you were using LAT, and you *obviously* wanted to put the modem on the DECserver if you had one, and *especially* if you wanted to access the modem from several machines.
So yes, it's an obvious idea, and it had an obvious answer. It's just you who are trying to do things backwards... :-)
Johnny
No I see how my way of doing it might seem backwards, I mean why share a modem from a host machine when terminal servers were invented for doing it?
Doesn't mean it wouldn't be a nice feature to have :)
Sampsa
On 11 Jun 2010, at 01:36, Johnny Billquist wrote:
What pays to remember is that once you had LAT and DECservers, you didn't use serial ports on your VAX anymore, especially not on a site where you had several VAXen. You *obviously* had DECservers if you were using LAT, and you *obviously* wanted to put the modem on the DECserver if you had one, and *especially* if you wanted to access the modem from several machines.
So yes, it's an obvious idea, and it had an obvious answer. It's just you who are trying to do things backwards... :-)
Johnny
Sampsa Laine wrote:
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?
What pays to remember is that once you had LAT and DECservers, you didn't use serial ports on your VAX anymore, especially not on a site where you had several VAXen. You *obviously* had DECservers if you were using LAT, and you *obviously* wanted to put the modem on the DECserver if you had one, and *especially* if you wanted to access the modem from several machines.
So yes, it's an obvious idea, and it had an obvious answer. It's just you who are trying to do things backwards... :-)
Johnny
Sampsa Laine 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?
I've done some commenting on this before, but as I'm running through my backlog I figured I might as well answer this again.
lcp set port lta1337: /service=b4bbs
will not cause service b4bbs to connect to port lta1337:, but if you run a terminal emulation program on the VMS machine, and connect to lta1337:, you will in fact be connected to the b4bbs service.
lcp set port lta1337/port=tna1
is an incomplete setup for doing a similar thing.
Both are for configuring reverse lat setups.
When you create a reverse lat setup, you create a local terminal (in this case lta1337:). When someone on the VMS box opens this device, they will be connected to whatever you have setup this port to talk to.
There are two different ways of going about the setting up. You can:
1) Specify a specific server and port
2) Specify a LAT service
Your first "attempt" specifies only the port, but not the server. Thus, if someone would have tried to connect after that had been specified, the connection would fail, since no server had been specified and thus the reverse LAT wouldn't have an idea on where to actually connect to.
However, your second specification makes that void anyway, since you instead specify a service that should be connected to.
In addition to all this, you also create a service called b4bbs, which is something others can connect to, and when they do, LOGINOUT will start on that port, to make it possible for the user to log in. Notice that there is no real, obvious correspondance between your lta1337: setup, and the b4bbs service, apart from the fact that if someone were to connect to lta1337:, they should be connected as with a loopback to the same machine, and presented a login session (assuming that the ethernet packets gets properly looped here, which I'm a bit unsure about).
Johnny
