1

SSH RemoteForward notify client on failure

view story
linux-howto

http://serverfault.com – I am using SSH to forward a port on a remote machine (Client) to another machine (Server) using (~/.ssh/config) Host Client: Hostname {ip} ... RemoteForward localhost:{port} localhost:{port} The problem is that even when there is not one listening on the Server, the client can connect successfully to localhost:port. The only indication of the failure is a message on the server: connect_to localhost port {port}: failed. Is there a way to forward this error to the client and terminate the connection? (HowTos)

u85500's picture
Submitted by u85500 on 02/03/2013

Stories similar to SSH RemoteForward notify client on failure

This is a low priority, but I suspect it may be demonstrating an even bigger problem.

Here is the problem. When I try to launch the game client from the Pioneers server or connect to a local server from the client itself the client fails. I ran from the command line and here are the results.

ai port is 5556 20:56:48 - Type of computer player: greedy

I'm wondering if/how I can realize the following setup. It doesn't seem to fit the standard ssh port forwarding model.

I have a client machine A. I have a server application running on machine A, which listens on port X. However, machine A is behind a common IP-address (shared by many users) so it can't receive incoming connections to port X from the internet.

I have a web server running on port 8080. I'd like to visit it via port 80, so I did this:

iptables -t nat -A PREROUTING -p tcp -m tcp --dport 80 -j REDIRECT --to-port 8080

it works if i access the server from other machines using

http://ipoftheserver/

but it doesn't work if I access the server from the same machine using

http://localhost/

why is that?

thanks in advance.

I have to use httptunnel to bypass firewall filtering of my ISP. I'm using this command on server side:

hts -F localhost:22 80

to forward my http port requests on ssh port. but httptunnels default live time is too short. it'll die after 5 minutes. I tried -M option to keep it live more. but it seams on client side with htc command, it's not helpful that much.

Reverse SSH tunnel 2 years 45 weeks ago

Does anyone know if it is possible to make the remote port in a reverse SSH tunnel listen on the regular network interface of the SSH server, and not just the loopback adapter on the remote system? The client is putty on a Windows machine, server is Ubuntu based (but can go with another OS if needed).

VNC through SSH with Windoze 3 years 18 weeks ago

Ok, I've been shaking my head these last few days trying to VNC into my Linux machine from my Windoze 7 machine using SSH. Here is what I've currently done so far:

I have SSH configured using port 8567, and have opened the tcp port 8567 in my firewall. I am able to ssh into the linux machine using putty on windoze, and do anything on the command line just fine.

simple port redirect 3 years 13 weeks ago

Hi,

I want to do a simple port redirect, i.e. whatever comes trough whatever interface on port AAAA will get redirected to port BBBB

I thought that

iptables -t nat -I PREROUTING --source 0/0 --destination 0/0 -p tcp --dport AAAA -j REDIRECT --to-ports BBBB

however it doesn't work, e.g. nc -v -w2 -z localhost AAAA gives:

ssh connection to vm refused 15 weeks 1 day ago

Host os - archlinux, guest - minix3(virtualbox).

When you have a Windows machine (server or home edition) which is running 2 servers, and they are both listening on port 4000, however none have had a request to connect?

What happens when a client attempts to connect?

Or is 2 things listening on the same port on the same machine not even a possible scenario?