Make a chain (Port forwarding) of local open ssh ports and open after on a new port

so that the traffic first routes to port 1080 than to 1081

Doesn't make sense. That port 1081 is on your local system. But the whole point of sending traffic to port 1080 is to forward it to a remote system (server A) instead of handling it locally. And there's no port 1081 on server A.

The way you describe – with both ports on the local system – it would have to be routed back from server A to your local system before it could go through port 1081... and that would be no different from just routing through port 1081 in the first place, since you're making the SSH connection directly to server B anyway, and server A doesn't contribute anything.

Instead, if you really want to form a chain, then the connection to server B needs to be initiated from server A, with the second -D port listening on server A's "localhost", not your local machine's.

There are two different ways to achieve it:

• The first method still runs both ssh clients locally, but proxies the whole SSH connection to server B through server A. This is convenient if your version of OpenSSH has the -J option, but the longer you make the chain, the more nested tunnel overhead it creates.

  There's only one step:

  ssh -J server_a -D 1080 server_b

  If you want to go through three systems, it's still one step, just repeat the -J some_server as needed:

  ssh -J server_a -J server_b -D 1080 server_c

  The equivalent parameter for ~/.ssh/config is ProxyJump.

• The same method without the -J option, this would involve either using -o ProxyCommand= or maybe manually set up -L chains: first to server A using -L 1022:serverB:22, then to localhost:1022 using -D 1080.

  Variant B of the first method:

  1. On the local system,

     ssh -o ProxyCommand="ssh -W %h:%p server_A" -D 1080 server_B

  To extend this to 3 or more servers, it would be easiest to define the ProxyCommand through ~/.ssh/config as the full command would get messy.

  Variant C of the first method:

  1. On the local system,

     ssh -L 5022:server_B:22 server_A

  2. On the local system,

     ssh -p 5022 -D 1080 localhost

  To extend this to 3 or more servers, repeat a similar -L instead of the -D. That is, the connection to server A creates a -L listener towards server B; the connection to server B (at localhost) creates another -L listener towards server C; and finally the connection to server C creates a -D listener.

• The second method doesn't cause as much overhead (since it chains tunnels rather than nesting them), but it requires planning backwards: first the connection from server A to server B (which creates a -D 1080 SOCKS listener on server A), then the connection from local system to server A (which doesn't create a new SOCKS listener, instead it uses -L to forward a local port 'raw' to the remote SOCKS port).

  1. From local machine, ssh -L 1080:localhost:5080 to server A.
  2. From server A, ssh -D 5080 to server B.

  To extend this to 3 or more servers, basically repeat the same ssh -L ... every time (just chaining the ports from A to B, from B to C).

  1. From local machine, ssh -L 1080:localhost:5080 to server A.
  2. From server A, ssh -L 5080:localhost:5080 to server B.
  3. From server B, ssh -D 5080 to server C.