Hello,
i need a little help with my setup.
I want to forwarding a service in my local network (192.168.1.3:80) to my internet server via meerkat.
Setup:
I Want to Reach: 192.168.1.3
Port: 80
As If Were On: This Mac
Available At: InternetServer
Port: 8080
When i try to launch the webbrowser on my internet-server with: http://127.0.0.1:8080 the page cannot be displayed.
The same setup with a windows pc work perfect. (Remote: 8080:192.168.1.3:80).
Is in meerkat a limitation?
Everything you've mentioned sounds like it should work. At this point, I would recommend that you right-click the tunnel in Meerkat, select "Copy Command", and paste the resulting command into Terminal to try.
Just to clarify, when you are tunneling from Windows, you are still accessing the LAN service on the remote server via 127.0.0.1? Or a public IP?
Also, not that it should matter, but what kind of server is the endpoint (where you're setting up 8080)?
Hmm, not sure right off why it is failing. But it's definitely the SSH under Meerkat that's doing it.
Can you try adding -v, then -vv, then -vvv, etc., to the command line try? That will provide more info, like the Windows desktop is.
If you feel more comfortable, feel free to email me instead to work through these issues as they seem specific to your server.
This part of the command looks suspect:
-R 8080:192.168.1.3:xx.xx.xx.xx
It should be of the form "-R ip_address:hostname:port" and should not have two IP addresses in it.
Can you email me at contact-at-codesorcery-dot-net with a screenshot from the tunnel edit window?
Some anonymizing proxy servers may forward data packets with header lines such as HTTP_VIA, HTTP_X_FORWARDED_FOR, or HTTP_FORWARDED, which may reveal the IP address of the client. Other anonymizing proxy servers, known as elite or high anonymity proxies, only include the REMOTE_ADDR header with the IP address of the proxy server, making it appear that the proxy server is the client. A website could still suspect a proxy is being used if the client sends packets which include a cookie from a previous visit that did not use the high anonymity proxy server. Clearing cookies, and possibly the cache, would solve this problem.



Thx for you answer. And sorry for my bad english.
The endpoint is a windows server 2003 with freeSSHd.
The Terminal output:
~ MyMac$ /usr/bin/ssh -p 2222 -l megara -N -o ConnectTimeout=5 -o TCPKeepAlive=yes -o NumberOfPasswordPrompts=1 -o ControlMaster=no -o PreferredAuthentications=password,keyboard-interactive -R 8080:192.168.1.3:80 xx.xx.xx.xx
user@xx.xx.xx.xx's password:
Warning: remote port forwarding failed for listen port 8080
But why does that fails?
Then from my mac with parallels desktop Windows with MyEnTunnel & plink.exe:
[19:11:25 02/17] Launching: plink.exe xx.xx.xx.xx -N -ssh -2 -P 2222 -l "user" -R 8080:192.168.1.3:80 -v
[19:11:25 02/17] Launching executable
[19:11:25 02/17] plink.exe: Looking up host "xx.xx.xx.xx"
[19:11:25 02/17] plink.exe: Connecting to xx.xx.xx.xx port 2222
[19:11:25 02/17] plink.exe: Server version: SSH-2.0-WeOnlyDo 2.1.3
[19:11:25 02/17] plink.exe: We claim version: SSH-2.0-PuTTY_Release_0.60
[19:11:25 02/17] plink.exe: Using SSH protocol version 2
[19:11:25 02/17] plink.exe: Using Diffie-Hellman with standard group "group14"
[19:11:25 02/17] plink.exe: Doing Diffie-Hellman key exchange with hash SHA-1
[19:11:26 02/17] plink.exe: Host key fingerprint is:
[19:11:26 02/17] plink.exe: ssh-rsa 1024 c4:44:d4:6c:cd:22:d4:9f:8c:35:e3:8b:c7:43:77:fa
[19:11:26 02/17] plink.exe: Initialised AES-256 CBC client->server encryption
[19:11:26 02/17] plink.exe: Initialised HMAC-SHA1 client->server MAC algorithm
[19:11:26 02/17] plink.exe: Initialised AES-256 CBC server->client encryption
[19:11:26 02/17] plink.exe: Initialised HMAC-SHA1 server->client MAC algorithm
[19:11:26 02/17] plink.exe: megara@83.169.11.10's password:
[19:11:26 02/17] Sending password
[19:11:26 02/17] plink.exe: Using username "user".
[19:11:26 02/17] plink.exe: Sent password
[19:11:26 02/17] plink.exe: Access granted
[19:11:26 02/17] plink.exe: Requesting remote port 8080 forward to 192.168.1.3:80
[19:11:26 02/17] plink.exe: Remote port forwarding from 8080 enabled
[19:11:36 02/17] Connection is stable