Xbase++
Xbase++
SSH Tunnel with Dynamic Port Forwarding
See more SSH Examples
Demonstrates how to start a background thread that runs a portable SSH tunnel w/ dynamic port forwarding that the foreground thread can use for establishing connections through an SSH tunnel.Chilkat Xbase++ Downloads
LOCAL nSuccess
LOCAL oTunnel
LOCAL cSshHostname
LOCAL nSshPort
LOCAL cUrl
LOCAL oHttp
LOCAL cHtml
LOCAL nWaitForThreadExit
nSuccess := 0
// This example assumes the Chilkat API to have been previously unlocked.
// See Global Unlock Sample for sample code.
nSuccess := 0
oTunnel := CreateObject("Chilkat.SshTunnel")
cSshHostname := "sftp.example.com"
nSshPort := 22
// Connect to an SSH server and establish the SSH tunnel:
nSuccess := oTunnel:Connect(cSshHostname, nSshPort)
IF (nSuccess != 1)
? oTunnel:LastErrorText
oTunnel:destroy()
RETURN
ENDIF
// Authenticate with the SSH server via a login/password
// or with a public key.
// This example demonstrates SSH password authentication.
nSuccess := oTunnel:AuthenticatePw("mySshLogin", "mySshPassword")
IF (nSuccess != 1)
? oTunnel:LastErrorText
oTunnel:destroy()
RETURN
ENDIF
// Indicate that the background SSH tunnel thread will behave as a SOCKS proxy server
// with dynamic port forwarding:
oTunnel:DynamicPortForwarding := 1
// We may optionally require that connecting clients authenticate with our SOCKS proxy server.
// To do this, set an inbound username/password. Any connecting clients would be required to
// use SOCKS5 with the correct username/password.
// If no inbound username/password is set, then our SOCKS proxy server will accept both
// SOCKS4 and SOCKS5 unauthenticated connections.
oTunnel:InboundSocksUsername := "chilkat123"
oTunnel:InboundSocksPassword := "password123"
// Start the listen/accept thread to begin accepting SOCKS proxy client connections.
// Listen on port 1080.
nSuccess := oTunnel:BeginAccepting(1080)
IF (nSuccess != 1)
? oTunnel:LastErrorText
oTunnel:destroy()
RETURN
ENDIF
// Now that a background thread is running a SOCKS proxy server that forwards connections
// through an SSH tunnel, it is possible to use any Chilkat implemented protocol that is SOCKS capable,
// such as HTTP, POP3, SMTP, IMAP, FTP, etc. The protocol may use SSL/TLS because the SSL/TLS
// will be passed through the SSH tunnel to the end-destination. Also, any number of simultaneous
// connections may be routed through the SSH tunnel.
// For this example, let's do a simple HTTPS request:
cUrl := "https://www.ethereum.org/"
oHttp := CreateObject("Chilkat.Http")
// Indicate that the HTTP object is to use our portable SOCKS proxy/SSH tunnel running in our background thread.
oHttp:SocksHostname := "localhost"
oHttp:SocksPort := 1080
oHttp:SocksVersion := 5
oHttp:SocksUsername := "chilkat123"
oHttp:SocksPassword := "password123"
oHttp:SendCookies := 1
oHttp:SaveCookies := 1
oHttp:CookieDir := "memory"
// Do the HTTPS page fetch (through the SSH tunnel)
cHtml := oHttp:QuickGetStr(cUrl)
IF (oHttp:LastMethodSuccess != 1)
? oHttp:LastErrorText
oTunnel:destroy()
oHttp:destroy()
RETURN
ENDIF
// Stop the background listen/accept thread:
nWaitForThreadExit := 1
nSuccess := oTunnel:StopAccepting(nWaitForThreadExit)
IF (nSuccess != 1)
? oTunnel:LastErrorText
oTunnel:destroy()
oHttp:destroy()
RETURN
ENDIF
// Close the SSH tunnel (would also kick any remaining connected clients).
nSuccess := oTunnel:CloseTunnel(nWaitForThreadExit)
IF (nSuccess != 1)
? oTunnel:LastErrorText
oTunnel:destroy()
oHttp:destroy()
RETURN
ENDIF
oTunnel:destroy()
oHttp:destroy()