[HECnet] LATCP confusion

So, in short, you want anyone who physically connects to your decserver, via a physical serial cable on one port, to be able to get a PPP session running on VMS? I think that should be doable. First of all, you need to set up the service on VMS, so that it is visible over LAT. Call it CHIMPYNET or anything else you want. Define which ports are associated with that service, and that's it from the LAT point of view. Then you need a PPP server to be listening on that port on the VMS machine, so that when someone connects, PPP traffic starts running. Hmm, that means that you don't want LOGINOUT to start. Not sure how you do that. But I'm sure someone who knows VMS can tell. Can't you request PPP to start running on your own terminal once you've logged in, by the way? If so, why not do it like that? You could even have a special PPP account, which started the service automatically on login. Someone else will have to help fill in the details here, since my VMS fu isn't really up to this in my head. (I know how to do this under RSX, but I also know that you can't totally accomplish this under RSX, since you can't define multiple services under RSX, and you probably want LAT service for more things than this.) The way I'd do it in RSX, which I think should work in VMS as well, would be to do it the other way, with reverse LAT. Basically, you do it like this: On your DECserver, define a service. Associate one or several ports with that service (probably one for this case). Make sure the port on the DECserver is correctly set up so that it can be opened from a host. On VMS, define a port as an outgoing (reverse LAT) port, for which you tell which service it should connect to (the service just defined in the DECserver). Set up PPP to be running on that port the whole time. PPP will now start trying to talk with anything connected to that port on the DECserver. No need to do any kind of connections or logins. Traffic will be going on the whole time. The same kind of deal you would be doing for a printer connected via a DECserver. Johnny Sampsa Laine wrote: Well I did say I was confused from the beginning :) I want to basically provide a PPP service on a serial port. This serial port happens to be on the DECserver, so I figured I would make a LAT service called CHIMPYNET on CHIMPY that provides the PPP service. Then anyone connected to the DECserver could just say CONNECT CHIMPYNET and be connected to the PPP service. Is this doable? Sampsa On 5 Oct 2009, at 00:11, Johnny Billquist wrote: You are totally mixing up things. Why don't you try to describe the whole path of what you are trying to do instead, and we work our way from there. The current setup is that if someone connect to LTA777:, the will be connected over LAT to the service CHIMPYNET. And the service CHIMPYNET seems to be defined as a service on the local machine, using port LTA777: Looks very circular to me... But I can be reading something wrong, since this is VMS, which I'm not as familiar with as RSX. With VMS I need to play around a bit to get things right usually. But without knowing what you really are trying to accomplish, it will be very hard to get things right. So. Start over, and start with describing what you want to accomplish, without even mentioning LAT, LATCP, or any specific details on that level. Describe it as if you had a serial port locally on the VMS machine, connected by a physical cable to another machine. Johnny Sampsa Laine wrote: Cool, that worked. But I'm still stuck :) What I'm trying to do is to attach a PPP service to this port, and then be able to connect to that from my DECserver. I've set up the PPP service: TCPIP SET INTERFACE PP1 /SERIAL_DEVICE=LTA777: /HOST=192.168.77.246 - /NETWORK_MASK=255.255.255.0 /DESTINATION=192.168.77.151 /COMPRESS=AUTO But doing a SET HOST/LAT CHIMPYNET does not work - any ideas where I'm going wrong? Some output: CHIMPYSYS$ lcp show service chimpynet Service Name: CHIMPYNET Service Type: Application Service Status: Available Connections: Enabled Service Password: Disabled Queueing: Enabled Service Ident: CHIMPY - OpenVMS 8.3 on AlphaServer 800 5/333 Service Ports: _LTA777: Node Name Status Rating Identification CHIMPY On 28 D CHIMPY - OpenVMS 8.3 on AlphaServer 800 5/333 CHIMPYSYS$ lcp show port lta777 Local Port Name: _LTA777: Local Port Type: Dedicated (Queued) Local Port State: Inactive Connected Link: Target Port Name: Actual Port Name: Target Node Name: Actual Node Name: Target Service Name: CHIMPYNET Actual Service Name: CHIMPYSYS$ set host/lat chimpynet %LAT-F-CONFAIL, connection to CHIMPYNET not established -LAT-F-LRJINUSE, port or service in use -LAT-I-END, control returned to node CHIMPY On 4 Oct 2009, at 20:50, Kari Uusim ki wrote: Sampsa Laine wrote: Guys, I'm trying to set up an incoming LAT service on CHIMPY called SAMPSACOM, i.e. I want to be able to connect to a service called SAMPSACOM over LAT and this connection is then routed to port LTA101: - I will have an app on CHIMPY that waits for connections on LTA101. I've done this: lcp:==mcr latcp lcp create port lta101: /dedicated lcp set port lta101: /dedicated /service=sampsacom Now what? If I try to connect to the port (via set host/dte) I get an error: %REM-E-PORTRXERR, port receive error -SYSTEM-F-HANGUP, data set hang-up It doesn't show up in SHOW SERVICES and SHOW PORTS says it's inactive: $lcp show ports * [....] _LTA101: Dedicated Inactive //SAMPSACOM Any help on how to proceed would be most welcome. Sampsa . First you should create the service $ MC LATCP CREA SERVI /APPL Then create the port $ MC LATCP CREA PORT /DEDI And then associate the port with your service $ MC LATCP SET PORT /DEDI /SERVI Then start your application which listens to the LAT port. Kari -- Johnny Billquist || "I'm on a bus || on a psychedelic trip email: bqt at softjar.se || Reading murder books pdp is alive! || tryin' to stay hip" - B. Idol -- Johnny Billquist || "I'm on a bus || on a psychedelic trip email: bqt at softjar.se || Reading murder books pdp is alive! || tryin' to stay hip" - B. Idol