[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[LDM #BJQ-992922]: LDM over SSH tunnel?

Eric,

> I’ve seen a couple mentions on the mailing list that others have tunneled LDM 
> over SSH, but have had little luck over the past few days finding the right 
> command to do so. Here’s a couple samples…
> 
> XXX@XXX:~$ sudo ssh -i aws.pem -N -L 388:localhost:388 address@hidden

I don't know what the "aws.pem" argument is for or what the -N option does but, 
otherwise, this command looks ok.

> bind: Cannot assign requested address
> channel_setup_fwd_listener: cannot listen to port: 388

Some other process must be listening on port 388. The netstat(1) utility should 
be able to tell you what it is.

Note that, unless you use the "--enable-port=<port>" option of the configure(1) 
script, the LDM itself will listen on port 388.

> Could not request local forwarding.
> ^CKilled by signal 2.
> 
> XXX@XXX:~$ sudo ssh -i aws.pem -N -R 388:localhost:388 address@hidden
> Warning: remote port forwarding failed for listen port 388
> ^CKilled by signal 2.
> 
> The need for this arose because, at least temporarily, I’d like to process 
> some data on AWS and insert it into the queue of my regular LDM server 
> (xxx.xxx.xxx.edu) that is seen by others, including the Unidata IDD. I don’t 
> want to have to bother the campus firewall custodians with another IP+port 
> exception for this temporary setup.

You should really get your firewall custodians to open port 388 for outgoing 
connections.

> My specific configuration runs the ldm-docker container on AWS. The AWS 
> instance has SSH open and I can access it from the XXX server on campus.
> 
> Is this known to be impossible, or if not, is there a best practice for this 
> sort of thing?

Not that I'm aware of.

Regards,
Steve Emmerson

Ticket Details
===================
Ticket ID: BJQ-992922
Department: Support LDM
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.