A small port-forwarding utility
Find a file
2024-04-13 14:59:19 -07:00
.github/workflows Maybe release for aarch64? Who can say. 2024-04-13 14:59:19 -07:00
.vscode I'm not sure I ever actually got these to work? 2022-10-26 07:12:59 -07:00
src Supply the error message when connect fails 2024-02-29 13:16:16 -08:00
.gitignore Enumerate all of the listening processes and their ports 2022-10-04 18:13:57 +00:00
Cargo.lock Bump the version in the crate 2024-03-01 06:15:56 -08:00
Cargo.toml Bump the version in the crate 2024-03-01 06:15:56 -08:00
config.toml Starting configuration, probably doesn't work 2022-10-18 11:28:56 -07:00
LICENSE Fill out Cargo.toml and also LICENSE 2022-10-26 07:11:38 -07:00
README.md Make notes about the future 2023-08-28 09:25:46 -07:00
rustfmt.toml Try to make the UI better when unconnected 2022-10-16 08:55:30 -07:00
test.py Protocol version, async pump, start some testing 2022-12-16 13:57:52 -08:00

fwd

A port-forwarding utility.

Here's how it works:

  1. Get the latest release of fwd
  2. You install fwd on the server somewhere in your $PATH (like /usr/bin/)
  3. You install fwd on the client (like your laptop)
  4. You run fwd on the client to connect to the server, like so:
doty@my.laptop$ fwd some.server

fwd will connect to some.server via ssh, and then show you a screen listing all of the ports that the server is listening on locally. Use the up and down arrow keys (or j/k) to select the port you're interested in and press e to toggle forwarding of that port. Now, connections to that port locally will be forwarded to the remote server.

If the port is something that might be interesting to a web browser, you can press <ENTER> with the port selected to open a browser pointed at that port.

If something is going wrong, pressing l will toggle logs that might explain it.

Press q to quit.

Future Improvements:

  • Clipboard integration: send something from the remote end of the pipe to the host's clipboard. (Sometimes you really want to copy some big buffer from the remote side and your terminal just can't make that work.)

  • Client heartbeats: I frequently wind up in a situation where the pipe is stalled: not broken but nothing is getting through. (This happens with my coder.com pipes all the time.)