TunnlTo Premium Beta

[brendanosborne]

The beta is currently closed. A new version will be released in December. Subscribe to this threads notifications if you'd like to try the next version of the beta.

[1aTa]

Awesome!

First bug report for you :)

When I try to register a new account using my email I'm getting the following error:

Firebase: Error (auth/network-request-failed).

[brendanosborne]

Okay, thanks. I think I know what is causing it.

[1aTa]

Yeah it doesn't progress to the main app screen after payment is completed, it just sits on the buy subscription page. When I logged out and then logged back in it took me straight to the main app screen.

I've noticed that you can no longer import a profile over the top of an existing profile, it just creates a new profile with the same name. Is that by design?

I also had quite a few profiles with a hyphen or minus symbol in the name which means that they can't be saved until the hyphens are removed. It seems spaces are allowed although I don't think the hint text specifically states that they are.

Do you have any plans to support adapter mode and the latest version of WireSock with the driver and library updates?

[brendanosborne]

I've noticed that you can no longer import a profile over the top of an existing profile, it just creates a new profile with the same name. Is that by design?

I could add a check for existing names and append a 2, 3, 4 etc. to the name.

I also had quite a few profiles with a hyphen or minus symbol in the name which means that they can't be saved until the hyphens are removed. It seems spaces are allowed although I don't think the hint text specifically states that they are.

Hyphens should be fine... I'll check into this.

Do you have any plans to support adapter mode and the latest version of WireSock with the driver and library updates?

Yes, but due to some technical limitations, the app will have to run in Admin mode to use the adaptor mode.

[edwardch]

BTW I've noticed that when I right click > connect > tunnel in the taskbar, it doesn't connect. I have to open the app and click connect for it to work.

When I open the app after the failed connection, the error message is:

Error starting tunnel
invalid args idToken for command enable_wiresock: invalid type: null, expected a string

[brendanosborne]

Thanks @edwardch I know what is causing that and will fix it in the next version.

[brendanosborne]

Quick update... I decided to do a big refactor to facilitate implementing Wiresock in service mode. I'm also preparing the app for migration to Tauri v2. Hope to have a new version of the beta out next week!

[jettycake]

Where can I access this beta to be able to test it?

Some concerns with the mention of an account to use the application. How exactly is this working?

[brendanosborne]

I am working on a new version which will have some major improvements so please mark this thread for notifications and I'll put out and update when it's available.

The authentication system uses Firebase.

[novakin]

Hello @brendanosborne
Sounds so promising, looking forward to the update to test it! Do you have any idea regarding the pricing model ? Subscription or one time payment ?

[brendanosborne]

Hi, it will likely be a yearly subscription which will include access to any updates.

[Shaynehou]

Error code:
Error starting tunnel
x
invalid args idToken for command enable_wiresock: invalid type: null, expected a string

[brendanosborne]

Thanks for the feedback. This will be resolved in the next release.

[brendanosborne]

Hi Everyone, I just want to provide a quick update.

After some feedback and issues from the first premium beta, I've done quite a large refactor of the code to make it more robust. It is getting close to a place where the next version can be released.

Here are some of the changes that are underway:

• Utilizing Wiresock as a service rather than a standalone process which will provide many benefits.
• Updating to the Tauri 2.0 framework which will provide a higher level of security and access to future security updates.
• Laying the foundation for utilizing the official Wireguard client as an alternative to Wiresock on tunnels where application level spit tunnel is not required.
• Adding some highly requested features such as Wiresock Virtual Adapter Mode (-lac launch parameter)

While the previous versions of TunnlTo were more of a proof of concept, the app is now far more robust. Overall it is a massive upgrade from the previous versions and I'm looking forward to having a solid foundation to build out more features.

I hope to have a new beta test version out by the end of the month. Please follow this thread for updates!

[brendanosborne]

A few people have been asking about pricing and payment models so I'll explain where I'm at with that.

• The beta period will be free. Beta testers who provide valuable feedback will receive a discount code after the beta phase.
• Post-beta, I plan to implement a yearly subscription model with an initial price of $39 USD. This price is tentative as the feature set for the first non-beta release is still being finalized.

The rationale behind a subscription model, rather than a one-time payment, is that I intend to work full-time on this project, consistently adding new features and improvements. I anticipate the app will rapidly evolve and I don't want to dedicate time supporting older versions.

Modern software complexity necessitates constant updates, particularly for security. For instance, the Tauri framework (on which TunnlTo is built) recently had a major release from v1 to v2, and the migration is time-consuming. Eventually, Tauri v1 will no longer receive security updates and bug fixes, and I don't want users stuck on an outdated, unsafe version of TunnlTo.

While it's possible to avoid using Tauri, React, Tailwind, and dependencies (and believe me, I try!), the reality is these tools allow for faster iteration and higher quality UI and features. This is the trade-off.

Ideally, I aim to offer a free tier with the functionality available in the open-source version, while providing additional premium features for power users. But I don't have all the answers yet and expect that things like this will become obvious as the product matures.

Happy to hear any constructive feedback!

[WhyClove]

I have done quite a bit of reading and I understand this feature is something wiresock must do but if that's a thing now, and you were to implement it, would this be under the free open source option or the paid tier?

The feature is running multiple tunnels at the same time.

Just something I'd like to mention

• please non IPV4/6 responses here. It was possible in V1 and some VPNs provide their input in a domain name

  

• I don't know if this really matters, but one of my configs makes use of

  100.126.121.60/32 which you can't do here

Thank you for making this very useful software 😄

[brendanosborne]

Thanks for the feedback.

Simultaneous Tunnels
I've got the Simultaneous Tunnels feature request list over here. It has been requested quite a bit and I'd personally like to have it for my uses. It's very much a Wiresock level implementation though. It's still in the feature request stage so unfortunatly I don't have any details on timeline or whether it'll be free or paid tier.

Domain based routing
I may have a way of doing this and need to discuss with the Wiresock dev. It's on the todo list and another one I'm personally keen on implementing.

/32 in local interface address
I'll update the documentation to state the /32 is not required.

[WhyClove]

That's great to hear,

just some more feedback:

• Should show the accounts + settings option

• should show tunnel import option (am aware this is already known) which also could be improved if it detects a duplicate and handles it smartly or prompts user to give it a new name.

• I get you are 100% likely planning to create an export tool for each tunnel, but maybe update your planned feature list so that's more clear? Also, maybe a mass export option?

• Could also play sound if the connection for some reason dies

[brendanosborne]

Hi Everyone, quick update as I'll be out of town for a week.

The next beta release will be the end of November / early December. Here are some of the highlights:

• The next version is a HUGE improvement over the previous version under the hood
• Wiresock will now be running in service mode
• Wiresock Virtual Adapter mode!
• Latest Wiresock version
• The latest version of Tauri - more efficient and secure.
• No more local storage (woohoo!) that causes weird issues
• Persistent tunnel logs between app restarts
• Improved log display
• Fixed and improved systray menu

Improved logs UI:

Some new settings:

[HitItAll]

This project is great and I think it's important to have competition in the market, but I have to say unless I'm missing something I can't quite understand why this project would be superior to the WireSock UI?
The only thing that is obvious to me is the improved UI experience, so is there a list of features that are (or are expected to be) implemented that are not present in the WireSock UI project?

Cheers

[brendanosborne]

I'm not sure what Vadim's plans are for WireSockUI. He's been pretty busy with other projects and we haven't discussed it in a while. I'll have a list of features available when the build is closer to release, but ultimately I would suggest trying both and evaluating what suits your requirements.

[bach1590]

I tried wiresock, and i had problems with it, I connected successfully and remained connected but i would somehow lose internet without beign disconnected after 5 minutes. Vadim did a lot of troubleshooting steps with me, including pcap logs, but we couldn't find out the issue - Since your project is based on Wiresock I wonder if I am likely to same the issue. I am on windows. I ran it as a service.

[cyberluke]

Where is the beta page or buy button or whatever? No links anywhere.

[brendanosborne]

The beta is currently closed. A new beta version will be available for testing in December.

[bach1590]

I subscribed to the thread notifications as asked and hope I can try the next premium beta to be relased in December. If there is anything else I need to do please let me know, thank you.

I did have a question though. I am wondering if your app addresses the following problem with the Wireguard client on windows. Basically the problem I have as it is also faced by others, is that when using the wireguard app, local connection to one's own network is not possible, and even when when one works around that, it creates ip leaks (I believe dns leaks). Of course VPNs wih proprietary software that have wireguard don't face this issue, but if you use the 'original' wireguard client this issue exists. I confirmed for example with AirVPN, they have no work around for this issue on windows.

Please see this, for example - people have tried again and again, but allowing local area connection, while possible, leads to leaks:
https://airvpn.org/forums/topic/56474-wireguard-local-network-access-and-dns/
https://airvpn.org/forums/topic/55801-wireguard-access-local-network/

[brendanosborne]

Yep that's all you need to do. I'll put a post in this thread once its available.

To route local IP's through your default connection (not via VPN), you can use this config:

• Allowed IP's: 0.0.0.0/0
• Disallowed IP's: 192.168.0.0/24 (as an example - you would need to put your own local IP addresses individually or as a range)

In regards to DNS leaks:

Rules

• If set, becomes the DNS for all applications (including any applications not configured to route through the tunnel).
• If left blank, the system’s default DNS server will be used.
• Use a comma to separate multiple DNS servers.

[phoenix1of1]

Absolutely stoked for the chance to try the premium beta so I've subbed to the thread.
On another note, just in-case it is something that may be relevant, I've had an issue around the non-beta version retaining configs.
I can add a new config to TunnelTo but if I were to remove that config and add in a "clean" version, something that wasn't amended within TunnelTo, the config reverts back to the non-clean version.

For example, disallowed apps and IP addresses retain previous settings. I removed the TunnelTo.conf from ~AppData/Roaming/TunnelTo and then restarted the TunnelTo client but it will still propagate the fields with the old superfluous information.

It's worth mentioning all the same.

Looking forward to the December signup.

[toby9999]

Getting close to Christmas... and a new beta invite?? ;-)

Oh well, guess not. Decided just to uninstall this (due to weird bugs) and go with the wiresock version instead.

[brendanosborne]

Hi Everyone,

Happy new hear and I hope you had a good Christmas!

Prior to Christmas I had some urgent family matters which stalled development. Then Christmas came around, and what do you know, it's now 2025 😅

I'm now back at it full throttle and trying to make up lost time. The app is really coming along nicely. I'm really looking forward to showing it off soon!

[edwardch]

Happy Christmas and new year!
I hope that all is ok with the family.

Looking forward to the updates 👀

[DrSkyfaR]

Im really exited too See the new Version, our NGO is waiting for the new Client.

We Hope you Had a nice Christmas and also a beautiful good New year.

With Kind regards USG :)

If you need anything, or WE should Test Something please let us know.

We are also ready provide some financial Support to Bring the Client Version Up. :)

[versohner]

Hi! Does your app support AmneziaWG or only WireGuard?

[e-t-l]

I don't know the answer to this, but I'm curious, doesn't AmneziaVPN already support per-app split tunneling? Why use Tunnlto?

[versohner]

It does, but on a PC this app turned out to be more convenient. Tunneling rules work more correctly
AmneziaVPN has many graphical bugs. It takes a long time to start, about 3 minutes
Important:

1. This is about PCs, not smartphones
2. I am writing this from a country where providers block VPNs using DPI