Hi
Seems that MT1300 stopped being developed half year ago. Newest release is from Aug 2024. Are there any plans for new releases?
Hello,
There will be a plan for MT1300 v4.7.x newer version will be released.
Please wait a moment, it will be released in the next few months.
1 Like
@bruce I mentioned in this thread: Will Wireguard client automatically switch servers? - #4 by bruce
about the 4.8 firmware and it's ability to switch VPN locations when down. You mentioned it's coming to the 4.8 firmware when it's release, how come the mt1300 isn't getting bumped to 4.8 or is it planned?
Tldr - will the original beryl (mt1300) support the "VPN down" switching too?
1 Like
The MT1300 needs to evaluate the hardware performance, and it is not confirmed whether it can support v4.8.
I get that not everything maybe possible to port over to v4.8 but maybe even if we can include the possibility of switching clients when down will be a massive thing, I can't see that being more of a burden on the hardware.
Or if needed a different version number for the beryl but with the added "client switching when down feature"
I'll submit it to PM to evaluate this. Thank you.
Given the features you mentioned, multi VPN tunnel failover is a very performance-consuming feature, since itself building one VPN tunnel also is consuming much performance.
Thanks, I appreciate it will be evaluated. Maybe I am being very naive with regards to the failover. I just assumed some simple uptime ping, tunnel up/down for the VPN tunnel would be an easy way to see if the tunnel had failed and then it just connects to the next config file...no more processing power needed as it just uses a different config to connect again...
On my pfsense router I managed to make a failover for the wireguard configs and it basically checked the tunnel was up constantly, if the tunnel went down it then just connected to the second profile.
1 Like
I can give some predictions.
In GL firmware v4.8, the multi VPN tunnels are online and actived at the same time, and to detect all tunnels in real time.
This means that the above tunnels can be switched at any time what you need.
It does not like "auto switch to the next one profile in order when detecting the current profile abnormal".
Therefore, this will consume more performance resources.
Assuming the failover is using the same multiple online clients / configs (VPN tunnels) in order to switch then I'm not sure if that's a good approach. The main benefit of using a VPN router is so that we can also bypass client device limits. For example, you might only be allowed 5 client / device connections via your VPN provider. I use my VPN router to bypass such limits, I can just have one config / device (the router) running but then put all my clients (more than 5 for example) behind the VPN tunnel. Using your suggested approach we would surely be using another config which would then look like another device / client.
Using a tunnel UP / DOWN approach would give the same outcome but would also mean that only one connection is ever used, giving us an extra config to use elsewhere. Also because the connection would only be active once the previous tunnel failed we would still be using the same amount of processing power which would mean more devices should be supported.
Sorry, after verified again, v4.8 also has this function. Including the multi tunnel and single tunnel with multi profiles auto switch.
1 Like
Hi,
The new VPN policy will have two ways to implement failover:
-
You can configure two tunnels with the same matching policy, but use different configuration files and have different priorities. When everything is normal, the data will use the VPN tunnel with the higher priority. Only when the higher priority tunnel is down will the lower priority tunnel be used for communication.
-
When establishing a VPN tunnel, there will be an option called "Automatically select configuration file". When this option is turned on, existing configuration files will be tried one by one until an available configuration is found to establish a connection.
I don't know if mt1300 will have it, but v4.8 will be like this
2 Likes