Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • This looks like what I need, but when I add those two options in sshd_config and restart sshd, it stops accepting any incoming connections include tunnels. Maybe need to add "userspecified" ports in config? Commented Dec 27, 2017 at 17:14
  • @J.Doe my mistake, clientspecified, (not userspecified)... just a word (means client ssh-user will specify on which interface will server listen) Commented Dec 27, 2017 at 23:07
  • Now it refuses to forward port 22 to local 2222 (and vice versa), but do it without "gatewayports clientspecified". Just print "remote forward failure" on tunnel creation, but forwards port 80 without any questions. Commented Dec 28, 2017 at 9:36
  • @J.Doe hm, yes 22 and 2222 should be switched, because serverB already listen on ssh (22) port, if 80 works well, then any other should work too, if it is free (no app listen on it on public-B side) Commented Dec 29, 2017 at 21:03
  • It's all my errors, noit works without any problem. Thanks. Commented Dec 30, 2017 at 11:01