anybody know what packages to add to install wireguard w/luci? 25.12.4 GL.iNet GL-MT6000
CONFIG_PACKAGE_luci-proto-wireguard=y
That should pull in the needed deps:
CONFIG_PACKAGE_kmod-wireguard=y
CONFIG_PACKAGE_wireguard-tools=y
kmod-wireguard
wireguard-tools
luci-proto-wireguard
Thanks! I will hang onto the build.
got "software not compatible" :<( when I added the 3 packages
There is a marked solution in this thread... did things work out or is the "software not compatible" issue still relevant? If so, can you give more details -- where did you see this message?? Any other information that might be useful?
read somewhere to use the factory gui - may need to select "advanced" . Not sure what to do with this
I would like not to have to rebuild my wireless config. Should I install attended sys upgrade???
Currently running: 21.02-SNAPSHOT - 0ecaf74 with luci
Kernel 5.4.328
Gl-inet flint2 MT-6000
It appears you are using firmware that is not from the official OpenWrt project.
When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.
You may find that the best options are:
- Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
- Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
- Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).
If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.
25.12.4 is supposed to be interchangable but I don't want to build everything from scratch.
Firmware, yes.
Configuration, no. You must rebuild your config if you move from GL-inet's vendor firmware to OpenWrt (or vice versa) because the GL-inet settings are not compatible with official OpenWrt.
That said, most configs are relatively simple to recreate and can often be done in like 10 minutes or so. Obviously if you have a very complex setup, it could take longer.
If you plan to stick with the GL-inet firmware, you need to use their support channels for help because their firmware is materially different than official OpenWrt. They have a user forum as well.
On the other hand, if you do migrate to official OpenWrt, we can help you here.
thank you. it says there is no meta-data, I must use force???
It would be helpful if you provided more context and details....
Was this meta-data issue seen when trying to flash a new firmware? What firmware image did you download? What exactly did you see when tried to update? (provide as much detail as you can)
It's rather difficult for us to help you figure this out if you do not provide the relevant details...
- What firmware image did you download? (complete filename)
- Where did you get the firmware file?
- what is the output (from the current firmware) of
ubus call system board
openwrt-25.12.4-mediatek-filogic-glinet_gl-mt6000-squashfs-factory_inc_wireguard.bin
got it from firmware selector
Using username "root".
Authenticating with public key "rsa-key-20260507"
BusyBox v1.33.2 (2026-03-30 06:07:52 UTC) built-in shell (ash)
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -| || | | || || |
|_____|| |||||___||| |____|
|| W I R E L E S S F R E E D O M
OpenWrt 21.02-SNAPSHOT,
root@Cisco:~# ubus call systemboard
Usage: ubus [] [arguments...]
Options:
-s : Set the unix domain socket to connect to
-t : Set the timeout (in seconds) for a command to complete
-S: Use simplified output (for scripts)
-v: More verbose output
-m : (for monitor): include a specific message type
(can be used more than once)
-M <r|t> (for monitor): only capture received or transmitted traffic
Commands:
- list [] List objects
- call [] Call an object method
- subscribe [...] Subscribe to object(s) notifications
- listen [...] Listen for events
- send [] Send an event
- wait_for [...] Wait for multiple objects to appear on ubus
- monitor Monitor ubus traffic
root@Cisco:~# ubus call system board
{
"kernel": "5.4.238",
"hostname": "Cisco",
"system": "ARMv8 Processor rev 4",
"model": "GL.iNet GL-MT6000",
"board_name": "glinet,gl-mt6000",
"release": {
"distribution": "OpenWrt",
"version": "21.02-SNAPSHOT",
"revision": "",
"target": "mediatek/mt7986",
"description": "OpenWrt 21.02-SNAPSHOT "
}
}
root@Cisco:~# ubus call system
Usage: ubus [] [arguments...]
Options:
-s : Set the unix domain socket to connect to
-t : Set the timeout (in seconds) for a command to complete
-S: Use simplified output (for scripts)
-v: More verbose output
-m : (for monitor): include a specific message type
(can be used more than once)
-M <r|t> (for monitor): only capture received or transmitted traffic
Commands:
- list [] List objects
- call [] Call an object method
- subscribe [...] Subscribe to object(s) notifications
- listen [...] Listen for events
- send [] Send an event
- wait_for [...] Wait for multiple objects to appear on ubus
- monitor Monitor ubus traffic
root@Cisco:~# ubus list
dnsmasq
dnsmasq.wgclient1
file
gl-clients
gl-session
hotplug.block
hotplug.carrier
hotplug.dhcp
hotplug.dhcpv6
hotplug.gl-tertf
hotplug.ieee80211
hotplug.iface
hotplug.kmwan
hotplug.neigh
hotplug.net
hotplug.ntp
hotplug.openvpn
hotplug.tftp
hotplug.tty
hotplug.usb
hotplug.usbmisc
hotplug.wireguard
iwinfo
log
luci
luci-rpc
mtk-wifi
network
network.device
network.interface
network.interface.guest
network.interface.lan
network.interface.loopback
network.interface.secondwan
network.interface.wan
network.interface.wgclient1
network.interface.wwan
network.rrdns
network.wireless
rc
repeater
rpc-sys
service
session
system
uci
You need the sysupgrade file, not the factory file.
Do I use the Gl gui or revert to luci?
The GUI is LuCI. There is the CLI if you want.... either one should work -- they call the same underlying process.