migration from v4 to v5

[TakamiChie]

migration from v4 to v5

[agebrock]

Hi @TakamiChie

The configuration is almost the same , just grouped a bit different.

• dstHost, dstPort goes to the => forwarding options. (in your case srcAddr and srcPort are most likely the same)
• host, port, username, password are ssh server related +> sshoptions.
• and localHost and localPort is where your localTCP Server is listening => serverOptions.
• keepAlive => tunnelOptions (autoClose:false)

Please let me know if that helps . We will update the Readme soon.

[TakamiChie]

Thanks for the reply.
I wrote the following program in accordance with your point.

const { createTunnel } = require('tunnel-ssh');

const tunnelOptions = {
  autoClose:false
};
const serverOptions = {
  host: localHost, port: localPort
};
const sshOptions = {
  host: host, port: port,
  username: username, password: password,
}
const forwardOptions = {
  srcAddr:host, srcPort:port,
  dstAddr:dstHost, dstPort:dstPort
}
let [[serv, conn], error] = await createTunnel(tunnelOptions, serverOptions, sshOptions, forwardOptions);

However, the following error is displayed when the createTunnel() method is executed.

(node:9252) UnhandledPromiseRejectionWarning: Error: listen EADDRINUSE: address already in use [localHost]:[localPort]
    at Server.setupListenHandle [as _listen2] (node:net:1372:16)
    at listenInCluster (node:net:1420:12)
    at doListen (node:net:1559:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:84:21)

Am I misunderstanding your point?

[agebrock]

actually your config looks right. The error indicates that something on the port : localPort is already listening.
As a hint how to find out what is listening you can check the following site maybe it will help you :
https://stackoverflow.com/questions/4075287/node-express-eaddrinuse-address-already-in-use-kill-server

FYI in the 5.0.5 version that error is catchable, this will not solve your issue you can just handle it different.

[TakamiChie]

Sorry for the late contact.

When the code was simplified as much as possible and the process was executed, the server and client objects were obtained as intended.

We look forward to continuing to update the Readme.

[agebrock]

👍 We are trying our best :-)