# Page Not Found

The URL `oscp-notes-include-active-directory-2023/port-forwarding-and-tunneling/plink-for-windows` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Plink for windows](https://hackervegas001.gitbook.io/hackervegas001/oscp-notes/port-forwarding-and-tunneling/plink-for-windows.md)
- [Netsh for windows](https://hackervegas001.gitbook.io/hackervegas001/oscp-notes/port-forwarding-and-tunneling/netsh-for-windows.md)
- [Port Forwarding with Rinetd tool](https://hackervegas001.gitbook.io/hackervegas001/oscp-notes/port-forwarding-and-tunneling/port-forwarding-with-rinetd-tool.md)
- [Chisel (http Tunneling)](https://hackervegas001.gitbook.io/hackervegas001/oscp-notes/port-forwarding-and-tunneling/chisel-http-tunneling.md)
- [Port forwarding and Tunneling](https://hackervegas001.gitbook.io/hackervegas001/oscp-notes/port-forwarding-and-tunneling.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://hackervegas001.gitbook.io/hackervegas001/oscp-notes/port-forwarding-and-tunneling/plink-for-windows.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://hackervegas001.gitbook.io/hackervegas001/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://hackervegas001.gitbook.io/hackervegas001/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/hackervegas001/oscp-notes/port-forwarding-and-tunneling/plink-for-windows.md`).

You may also use `Accept: text/markdown` header for content negotiation.