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*

9
  • Ok, seems like I need something like $ ssh -L *:8080:deviceIP:80 user@localhost # run on awsonly that I don't have 'deviceIP' but instead a reverse tunnel on port '15872' to get access to the host in the restricted network.... so how do I need to modify this accordingly? Plus what do you mean by It's probably not the best way ? Is there a better way you know of? Commented Nov 7, 2018 at 13:06
  • 1
    @cerr About "It's probably not the best way", see my edited answer. Commented Nov 7, 2018 at 13:17
  • 2
    @cerr Your network topology is not entirely clear to me. Are you actually trying to connect your host (A) to a non-directly reachable remote host (C) by establishing 2 different tunnels to a publicly available host (B)? As in "A -ssh> B <ssh- C"? If so, I'm sorry, I misunderstood your question - and I will update my answer. Commented Nov 7, 2018 at 13:22
  • Yes pretty much, what I have is (A being my private computer, B the public reachable aws instance, C the Linux host in the restricted network, D the device I would like to reach in the restricted network). What I have going fine is A-ssh>B-reverse ssh>C. What I would like to add: A-http8080>B-reverse ssh>C-http80>D. Commented Nov 7, 2018 at 13:45
  • 1
    @cerr See edited answer. Commented Nov 7, 2018 at 14:49