Skip to content

Added how to connect in a reverse way and/or via a repeater #274

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bk138 merged 3 commits into from
Mar 12, 2025
Merged

Added how to connect in a reverse way and/or via a repeater #274

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
49ca5de
Added how to connect in a reverse way and/or via a repeater
lwcorp Mar 11, 2025
47a21ca
Rephrased about UPnP
lwcorp Mar 11, 2025
3c32f5a
Rephrased Reverse VNC without a screenshot
lwcorp Mar 12, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 10 additions & 4 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,8 +31,8 @@ If you have a general question, it's best to [ask in the community chat](https:/
in case you want to access the server using MacOS's built-in Screen Sharing app.
* Ability to specify the port used.
* Start of background service on device boot.
* Reverse VNC.
* Ability to connect to a UltraVNC-style Mode-2 repeater.
* [Reverse VNC](#reverse-vnc).
* Ability to [connect to a UltraVNC-style Mode-2 repeater](#reverse-vnc).
* Functionality to provide default configuration via a JSON file.
* Zeroconf/Bonjour publishing for VNC server auto-discovery.
* Per-client mouse pointers on the controlled device.
Expand All @@ -55,9 +55,15 @@ If you have a general question, it's best to [ask in the community chat](https:/
* **End** acts as Power button
* **Escape** acts as Back button

### For accepting connections from outside
### How to connect?
#### Reverse VNC
Leaving ports always open is considered risky, and either way most users don't even know how to open them in their routers. You can thus leave the VNC port **blank** and instead connect to either a **listening viewer** or a **repeater**:

1. You should allow [Port Forwarding](https://en.wikipedia.org/wiki/Port_forwarding) in your router's Firewall settings. Login to your router's settings (usually open 192.168.1.1 in your browser, some routers have password written on them).
![image](https://github.com/user-attachments/assets/aa2f9cc2-87d0-438e-9604-c8f9e8db97c3)
Copy link
Owner

@bk138 bk138 Mar 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please remove that link as it might go dead if you remove your fork :-)

Copy link
Contributor Author

@lwcorp lwcorp Mar 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which link?

Copy link
Owner

@bk138 bk138 Mar 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image :-)

Copy link
Contributor Author

@lwcorp lwcorp Mar 11, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The URL structure user-attachments/assets/ suggests the attachment is associated with a GitHub user account, not a specific repository, issue, pull request, etc. or in this case fork.

So I assume the only chance it'll get deleted is if my entire username gets deleted, which is far less common than a fork deletion. But...GitHub in known in general for never deleting attachments under any circumstances. Not enough? Then I've just created a new account, took a screenshot of this PR, then deleted the entire username. And guess what? The screenshot still remains.

Nevertheless, to cover it 100%, I've just asked officially about it and used references and the aforementioned proof of concept.
But if despite all this you're still worried, you can download and then re-upload the attachment into this pull request's code, so it'll be linked to your username. But then again, what happens if one day you decide to let someone else be admin and delete your username? ;-) This is exactly why I think GitHub never deletes attachments.

Copy link
Owner

@bk138 bk138 Mar 12, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I prefer to not have a detailed discussion about this. The repo should be self-contained. Please just remove the link :-)


#### Direct VNC
If you prefer automatically accepting connections from outside:
1. You should allow [Port Forwarding](https://en.wikipedia.org/wiki/Port_forwarding) in your router's Firewall settings. Either find a [UPnP](https://en.wikipedia.org/wiki/Universal_Plug_and_Play) supported app to open ports dynamically or log in to your router's settings (usually open 192.168.1.1 in your browser, some routers have password written on them).
2. Find Port Forwarding, usually it's somewhere in **Network - Firewall - Port Forwards**.
3. Create a new rule, this is an example from OpenWRT firmware.

Expand Down