Skip to content
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.

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

Missing magical word * in "Port Forwarding" #102

Closed
bigboyq opened this issue Nov 12, 2020 · 14 comments
Closed

Missing magical word * in "Port Forwarding" #102

bigboyq opened this issue Nov 12, 2020 · 14 comments
Assignees
Labels
🐛 bug Something isn't working

Comments

@bigboyq
Copy link

bigboyq commented Nov 12, 2020

I am happy to see the VPN feature from the version 14.6
But quite incovient for me, as I used tunnel as a bastion, instead of VPN.
As I have at least 10 machines to connect through the bastion tunnel.
Under this new feature, I must set up at least 10 tunnels to forward connections.
In the past, just magical word "" should resolve the problem.
I am happy to have system VPN features instead of in-app feature, but please keep the magical word "
" enabled.
If VPN feature supported, magical word "*" keep also, would be quite convient for every users.

@isontheline
Copy link
Owner

Hello @bigboyq 👋

Magical word * have been only removed from documentation not from the code itself.

Do you experience any problem with the dynamic port forwarding (aka bastion?)

@bigboyq
Copy link
Author

bigboyq commented Nov 12, 2020

Yup, I have downloaded TF version, and make up connection through tunnel successful, with the configuration "*"
I could see VPN logo on top of screen, but every connection I made, no matter in-app or out-app, all through the default wifi or celluar, no as expected through the tunnel

@isontheline isontheline self-assigned this Nov 12, 2020
@isontheline isontheline added the 🐛 bug Something isn't working label Nov 12, 2020
@isontheline isontheline added this to the 14.7 - Tractor milestone Nov 12, 2020
@isontheline
Copy link
Owner

Thank you a lot for your quick feedback!

So I will fix it as soon as possible.

I will come back to you shortly I think.

Have a nice day ☀️

@isontheline
Copy link
Owner

Perhaps you could download an older version (before 14.6) in order to use bastion again while I'm working on a fix.

@bigboyq
Copy link
Author

bigboyq commented Nov 12, 2020

That's ok, it seems that you have reproduced the problem, happy to see you online

@isontheline
Copy link
Owner

isontheline commented Nov 12, 2020

@isontheline isontheline added this to In progress in Tunnel / VPN-Over-SSH Nov 12, 2020
@isontheline
Copy link
Owner

@bigboyq TestFlight update will be available tomorrow

Have a nice day ☀️

@isontheline
Copy link
Owner

image

Always waiting for review... I'm impatient 😇

@isontheline
Copy link
Owner

Apple are you watching me?

image

@bigboyq Could you try this beta release please?

@bigboyq
Copy link
Author

bigboyq commented Nov 14, 2020

Sorry, just wake up, I am living in EST-8
Have tested.
As the implementation is legacy, in-app test passed, work properly, out-app test failed, as all traffic implemented inside app, not through vpn.

@isontheline
Copy link
Owner

isontheline commented Nov 14, 2020

Hello @bigboyq, thanks for your feedback!

The magical word * can only be used inside the app yet.

I will implement outside app traffic later (in another issue, in another milestone) as a lot of work is required.

If you need outside traffic to pass through the port forwarding, please enable the tunnel and then please use :

  • Socks V4 server : 127.0.0.1
  • Socks V4 port : 1985

Your outside apps need socks support of course.

@isontheline
Copy link
Owner

@bigboyq Have you used "Web" connections in the past?

@bigboyq
Copy link
Author

bigboyq commented Nov 14, 2020

I have seen the Web connection in the past, but don't know how to use, no documentation as good as now :)
If I am your product manager, I would suggest:

  1. in-app tunnel should be a native feature
  2. out-app tunnel(iOS VPN style) could be a in-app-purchase, and more work could be done, just as route table, route list, local port mapping should be a route rule. magical word maybe the default rule, hoho

I think much more users should be interested in this feature, as using SSH server is much easier than buildindg any other VPN server.

@isontheline
Copy link
Owner

I think much more users should be interested in this feature, as using SSH server is much easier than buildindg any other VPN server.

I agree!

I have added issue #104 in order to track progress of VPN Over SSH outside WebSSH.

Thank you again for your feedback @bigboyq

@isontheline isontheline moved this from In progress to Done in Tunnel / VPN-Over-SSH Nov 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working
Projects
No open projects
Development

No branches or pull requests

2 participants