Look at frwd #26

New Issue

GiteaMirror · 2025-11-10T13:53:04-06:00

GiteaMirror commented

2025-11-10 13:53:04 -06:00

Originally created by @Eun on GitHub (Feb 8, 2022).

I started with frwd (aka forward) before I found your list.
However, still finished it, maybe you want to take a look at it:
https://github.com/Eun/frwd

Originally created by @Eun on GitHub (Feb 8, 2022). I started with frwd (aka forward) before I found your list. However, still finished it, maybe you want to take a look at it: https://github.com/Eun/frwd

GiteaMirror commented

2025-11-10 13:53:04 -06:00

@anderspitman commented on GitHub (Feb 11, 2022):

Hey @Eun, thanks for the contribution! I've gotten a bit more choosy about what I add to the list, since it's getting harder to differentiate between the many options. Are there any particular features of frwd that you feel sets it apart from other solutions?

@anderspitman commented on GitHub (Feb 11, 2022): Hey @Eun, thanks for the contribution! I've gotten a bit more choosy about what I add to the list, since it's getting harder to differentiate between the many options. Are there any particular features of frwd that you feel sets it apart from other solutions?

GiteaMirror commented

2025-11-10 13:53:04 -06:00

@Eun commented on GitHub (Feb 12, 2022):

Hello Anders!
No worries, I am not mad if you don’t add it to the list since there are
already mature solutions on the list.

Just some quick info about frwd:
First of it is easy to setup: just specify a domain you own (& want to use)
and your ssh public key, that’s it.

The features are:
• Supports HTTPS, HTTP & TCP protocol.
• Automatic TLS certificates for HTTPS
• Multiple active tunnels at the same time.
• port based subdomains
• uses standard SSH client

It basically lets you choose which port it should allocate on the server
and use for forwarding it to your local machine.

e.g forward your local port 8000 to remote port 1234 and you will get

http://1234.example.com
https://1234.example.com

And example.com will also listen on tcp port 1234, therefore you also get

http://example.com:1234 and
tcp://example.com:1234

The TCP feature lets you forward any non http traffic.

I hope this helps. ☺️

@Eun commented on GitHub (Feb 12, 2022): Hello Anders! No worries, I am not mad if you don’t add it to the list since there are already mature solutions on the list. Just some quick info about frwd: First of it is easy to setup: just specify a domain you own (& want to use) and your ssh public key, that’s it. The features are: • Supports HTTPS, HTTP & TCP protocol. • Automatic TLS certificates for HTTPS • Multiple active tunnels at the same time. • port based subdomains • uses standard SSH client It basically lets you choose which port it should allocate on the server and use for forwarding it to your local machine. e.g forward your local port 8000 to remote port 1234 and you will get http://1234.example.com https://1234.example.com And example.com will also listen on tcp port 1234, therefore you also get http://example.com:1234 and tcp://example.com:1234 The TCP feature lets you forward any non http traffic. I hope this helps. ☺️

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-tunneling#26