Hi,
Sorry, this issue affects VPN functionality in op24-v4.8.0, R&D have found the reason, will improve asap and release new firmware.
9 Likes
Why didn't they test the firmware before releasing it?
Hi,
Sorry, the testing resources are tight and there may not be a complete test. At present since multiple R&D tasks (demands, issues) overlap, this situation will improve in the future.
A new firmware which improves this issue will be released in the next two days.
3 Likes
Opo-24 4.8 is going to be worth the wait
2 Likes
A basic test should de done. It's a beta firmware and not an alpha.
You just need a device with most of the features enabled, update it from the previous version, try to access the internet and check if the features are enabled.
5 Likes
Why would you not pull the bad firmware from the site ?
2 Likes
This firmware is not so bad. Basic functions and WiFi are working well here. I do not use a VPN for the moment.
Guys lets not finger pointing. Is an issue and will be solved. @bruce if you have the permissions please pull it from download and add the 4.7.5 so the users can fix the routers with the buggy firmware
4 Likes
the only issue i noticed the repeater function has some issues, but I think this issue is longer present because it happens on multiple gl sdk versions.
@bruce could you report this post to the devs to look into?
I think I hit a certain edge case, but I think it can easily happen on different brand routers with OEM firmware and experimental wifi 7 where they allow all these protocols as part for wifi7 even though they don't use roaming or radius vlans, it is possible they still use vlan 1 internal with radius.
I don't understand what they do with 4.8.0, where is normal VPN routing policy functional like in old FW to use custom ip list for vpn? What is joke is this?
The beta 4.7.5 op24 is on the download page
1 Like
Add a Tunnel in Client section first, then return to VPN dashboard and enable the tunnel, you'll have even more options than before in customizing the policies, it's actually pretty amazing.
1 Like
I only received this message when I was in the client tab, attached the image, rebooted and it still appears
1 Like
Its beta not final. Beta is extended testing where you catch things you cant do internally.
1 Like
Its beta so you expect bugs. Thats the whole point.
That said, on a Beryl AX, its designed as a travel router so id suggest VPN client functionality is a core feature of that. Most people are going to use it for that.
3 Likes
It's beta, not alfa 
Nobody expects a broken internet connection in a beta version.
4 Likes
You expect certain features to not work. A broken vpn with certain protocols is not a "broken internet connection". Its the type of fault you only uncover at beta once it gets rolled out to much much larger ranges of configurations and usage variations.
If you want fully tested, complete firmware, use stable not beta.
We expect this on their SNAPSHOT firmwares. Not on Beta.
1 Like
Beta does not mean bug free. Its beta for a reason. Bugs get introduced, obscure bugs start showing through, the occasional careless commit has unforeseen consequences, as do typos. Which is likely what this is from looking at the log.
If you want stable and fully tested, dont use Beta. Use stable. Beta is guaranteed to have issues. Its supposed to. Its extended testing.
1 Like
Sorry, there are a lot of posts in thread, maybe missed it.
OK, I will check this.
1 Like