GLiNet BE3600 router and OpenVPN configuration for LuCI

Routers VPN, DNS, Leaks
1

I recently bought the newest GLiNet router [Slate 7 (GL-BE3600)] as i wanted to take advantage of many configuration features that normally are not accessible via routers that come their tied-controlled OS. My BE3600 is running on 4.8.1 and firmware version [OpenWrt 23.05-SNAPSHOT / LuCI Master git-25.231.52382-62e675d] BE3600 has two UI interfaces the regular one and LuCI which allows for more granular control. My use case is: I need to use OpenVPN client (tap mode) and the main UI default to tap-s2s everytime i upload my fully working .ovpn config file. I want to use just regular OpenVPN tap mode client that can connect to OpenVPN tap server (which is my rpi5) The problem is that when i go to LuCI UI, I don’t see VPN in the menu, nothing to configure OpenVPN which I was hoping it would allow me to setup standard OpenVPN tap not tap-s2s. In LuCI > System > Software i already searched for available luci-app-openvpn package which i installed [luci-app-openvpn git-24.316.15780-3601c2a ~12.63 KiB LuCI Support for OpenVPN]

  1. What does this package actually do? The name indicates it is OpenVPN support in LuCI but how, if the functionality is not added to the LuCI menu.
  2. Did anybody try to install it and does VPN show up on your end in LuCI?
  3. I know OpenVPN can be configured via CLI (i did this on my RPI5) but when i do that in BE3600 CLI and go to LuCI it says tap0 interface extension not supported.
2

Hi,

Thank you for your feedback.

It appears there is an issue with the BE3600 LuCI interface that prevents the VPN → OpenVPN in menu from displaying correctly. We have reported this to our development team for further investigation and a possible fix in a future release.

image
image589×124 8.15 KB

In the meantime, you can access the OpenVPN configuration page directly using the URL below. Please note to replace the IP address and port with those used in your setup:

http://192.168.8.1:8080/cgi-bin/luci/admin/vpn/openvpn

image
image1098×733 30.4 KB

4

Thank you for your quick response. This is good news that this was confirmed as bug. Do you know if this bug in GLiNet software 4.8.1 would be fixed in 4.8.2 and when you think the next release would be. Will the fix make it to 4.8.2?

5

This issue appears to be related to LuCI and the underlying QSDK, which are not directly maintained by our team. We first need to assess whether it is something we can resolve internally. If not, we will need to report the issue to Qualcomm for analysis and a potential fix.

At this time, no estimated timeline is available, as it depends on the outcome of this assessment and any required third-party involvement.

2026-01-09 Update:
We have fixed this issue in the snapshot builds .
The stable version will merge this fix in the next release.