Timeline for How to redirect website in restricted network through ssh tunnel
Current License: CC BY-SA 4.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 24, 2021 at 9:31 | history | edited | fra-san | CC BY-SA 4.0 |
Grammar, more accurate wording, better positioning of code blocks
|
| Nov 12, 2018 at 23:25 | vote | accept | stdcerr | ||
| Nov 12, 2018 at 22:41 | comment | added | fra-san |
Which tcpdump commands did you try? I don't think host-C would see any port 15872. Given my command (2), I think it would see packets from host-B:22 (since I didn't explicitly set a port for connecting to host-B) going to its dynamically allocated port connected to host-B.
|
|
| Nov 12, 2018 at 19:28 | comment | added | stdcerr |
This doesn't quite work for me. I do a tcpdump on host-B and see the 8080 requests coming in from host-A but doing a tcpdump on host-C for port 15872 I don't see anything coming in...
|
|
| Nov 7, 2018 at 14:57 | history | edited | fra-san | CC BY-SA 4.0 |
added 58 characters in body
|
| Nov 7, 2018 at 14:49 | comment | added | fra-san | @cerr See edited answer. | |
| Nov 7, 2018 at 14:49 | history | edited | fra-san | CC BY-SA 4.0 |
deleted 613 characters in body
|
| Nov 7, 2018 at 14:17 | comment | added | stdcerr |
I use autossh on C (exec command on C) to establish a reverse ssh tunnel connection on a particular PORT to B, I then connect from B by ssh user@localhost -p PORT
|
|
| Nov 7, 2018 at 14:08 | comment | added | fra-san |
@cerr Are you establishing a connection from C to B (i.e. executing a ssh command on the Linux host C) or the other way round?
|
|
| Nov 7, 2018 at 13:45 | comment | added | stdcerr |
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.
|
|
| Nov 7, 2018 at 13:22 | comment | added | fra-san | @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. | |
| Nov 7, 2018 at 13:17 | comment | added | fra-san | @cerr About "It's probably not the best way", see my edited answer. | |
| Nov 7, 2018 at 13:15 | history | edited | fra-san | CC BY-SA 4.0 |
added 260 characters in body
|
| Nov 7, 2018 at 13:06 | comment | added | stdcerr |
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?
|
|
| Nov 7, 2018 at 10:10 | history | edited | fra-san | CC BY-SA 4.0 |
added 6 characters in body
|
| Nov 7, 2018 at 10:03 | history | answered | fra-san | CC BY-SA 4.0 |