Velica real-world usage review

I have not found any detailed Velica reviews based on the actual experience of using the unit. There are few “unboxing”/“setup” style posts here and there, but no long term usage review. Without further ado, let’s start.

In the summer of 2021 I replaced my Convexa (B1300) mesh setup with two Velicas (B2200)…

TL;DR: Forget about OpenWRT (“flexibility”), forget about DFS (“high speed” in urban areas), hardware is decent but very very limited by the software and the software is locked airtight. This is a regular vendor-locked proprietary device, unlike the previous models. It works well, though. Of course, within the boundaries of the tiny walled garden GL.iNet allows you to play in, but sadly useless in many locations. Buy something cheaper instead or do not afraid to pay extra for DFS support.

Important things you need to know before considering Velica:

  1. There is NO DFS support, which means it can only use channel 36 (42 since all your neighbours using entire 80MHz, too)
  2. There is no OpenWRT exposed in the mesh mode on the sub-nodes and very limited control over the main node, too.
  3. Not a deal breaker unlike the previous two, but still important. There is no parity for web and mobile admin apps, you have to stick to one method of changing the settings.

DFS support is nowhere to be seen, well, it has been confirmed already, not much to add there. It is a glaring omission, buy Convexa instead, DFS is working there with minimal scripting. It is a real shame, because it kills WiFi mesh performance – imagine being able to have your backhaul connection using different frequencies from your client’s network. However, in reality if you are using Velica all your data is competing twice for the same frequency (in my flat there are a dozen APs all sitting on the same channel 36(42) and using 80MHz).

OpenWRT is a marketing gimmick, do not expect to be able to use any of the advanced capabilities especially in the mesh mode. Most of the settings are locked and will be overwritten if you change them manually (presumably by the mobile admin app?). In fact, in mesh mode you cannot even access the sub nodes anymore (it was working fine with Convexa). Again, compared to Convexa is it a huge step back. While not supported, I could tweak each node’s config via SSH on Convexa, something not possible with Velica.

The mobile app, well, maybe useful for attracting TikTokers (or, more seriously, simplyfying first time setup), but I wish GL.iNet invested more in the DFS support instead or at least unlocked proper SSH/UCI access. It’s hard to justify mobile app when they do not provide MVP with basic necessary features (DFS and OpenWRT). Keep in mind that certain settings can be accessed via web admin only, e.g. if you create VPN client config using web UI, you won’t be able to see in the app.

Do I still use it? No longer, it sits in the storage, waiting for the proper OpenWRT to be ported there. If it won’t happen soon, I have plan B. My friends need a better connection in their garden shed which is pretty much in the middle of nowhere. Sadly, this is the only use case I see for this promising-on-paper device.


Great review.
I love Glinet for what they did with Mango2, but right NOW they have to decide if they want to be a “power user” brand, or compete in plebs market. Cannot have both Glinet.

Hi @jbourne. I see you recommend Convexa over Velica because of DFS. So, I’m a long time GLinet router user (small units I use for travel as well as extending network in nooks/crannies around house).

Are you super satisfied with Convexa performance and coverage? How many Convexas can you put on single mesh network? I like the configurability of GLinet products… just want to be sure it’s up to snuff with other mesh solutions on the market because I have a boat load of devices across all of my family members.


It’s worth noting that the Convexa range is still currently based on 15.05 as well.

Convexa supports mesh as well. Mesh can be created without an app using the physical buttons which is both a blessing and a curse (it’s a bit of a convaluted process).

Other “advantages” of the Convexa series is:
3 Ethernet ports
USB port (which I really miss with the Velica as I used a memory stick as a video NAS)
You can SSH to each slave on the Convexa mesh which you can’t on the Velica mesh - I used to run transmission on one of my slave nodes)

The Velica does have better WiFi coverage in my experience however.

YMMV :slight_smile:

Hi @mxdevo,

@limbot posted a nice summary and I agree that for many users the physical ports are much more important compared to the potential wifi performance impact. Simply because ports are always there (or not) and wifi still depends on many factors. Also, neither one has official DFS support, it’s just possible to manually enable it with Covexa setup.

Speaking of the wifi, in my block of flats there could be up to a dozen of wifi stations on the default channel 36 (42). So moving to a different (which has to be DFS!) channel instantly improves throughput. Coverage is good for both Convexa and Velica in my case, but theoretically Velica may perform better.

@mxdevo oh sorry and Gl.inet normally tests their mesh with up to 5 nodes but that being said there’s been posts on the forum with people successfully running more.

Same, experience these routers have a ton of issues still, I ordered on presale* and almost a year later till broken*. Mesh on can be configured through the app, and is very touchy, and you’ll literally hours trying to get the mesh network up. Then other glitches where they won’t connects to an external WAN ip, will shutdown for no reason. My logs just kernel failure over and over. Contacted support 3 times now, 0 responses. :slight_smile:

Mmmm, interesting. While I mentioned above my thoughts about the “shortcomings” of the Velica versus Convexa, I am still running a 3 node Convexa mesh as my standard family setup I have never had any of the issues you mention around setup or connectivity.