Upgrading GL.iNet Brume / GL-MV1000(W) to version 4.2.1

Upgrading GL.iNet Brume / GL-MV1000(W) to version 4.2.1

2023, Mar 25    

Microsoft Teams disconnects the tethered network… Why?

The tethering connection on the GL.iNet Brume router is consistently dropped after a short period of time when using Microsoft Teams, often at inconvenient moments. I have determined that this behavior is not due to coincidence but rather a direct result of using Teams. Swapping out machines and operating systems didn’t help. Also changing over to the web Teams client wasn’t a workaround to the problem.

Proactively investigate the potential of upgrading the router software is the first course of action.

OpenWRT is a popular open-source operating system for routers and other networking devices. It provides a customizable and flexible platform for configuring and managing network settings, as well as advanced features such as VPN support, firewall rules, and bandwidth monitoring.

Like any software, OpenWRT is constantly evolving and improving. Developers release new versions of the operating system regularly to fix bugs, improve performance, and add new features. When you encounter issues with your router, upgrading to a newer version of OpenWRT can often help to resolve the problem.

Yes, updating the router software to a newer version of OpenWRT was the solution to the problem . In general, updating the software or firmware of your router is a common troubleshooting step to fix issues and improve overall performance. It’s important to keep the router software up-to-date with the latest patches, bug fixes, and security updates to ensure optimal functionality and security of your network.

In my case the router is end-of-life so we need to be a little more creative, read below the details.


It is always a good practice to stay up to date with firmware and software updates. In my situation, there was an additional motivation for me to look for a newer firmware.

The newer Brume2 GL-MT2500 of GL.iNet routers sports OpenWRT 21.02 software while my current router runs OpenWRT 19.07.x software.

Let’s try to update the firmware to a newer version, totally ignoring the router’s end-of-life status and support level. If updating the firmware doesn’t work, I’ll order the sleek Brume 2 / GL-MT2500.

While utilizing Microsoft Teams at my ‘tiny office’, the internet connection would frequently drop out. As there was no direct internet connectivity available at the office, I opted to purchase a compact and versatile router, specifically the GL.iNet GL-MV1000, and tethered it to my smartphone. Initially, this solution appeared to work well, but over time the internet connection began to drop out intermittently, possibly due to having Teams active and its updates. Eventually, the situation worsened to the point where it became too frustrating for me to tolerate. Diving deeper into the symptoms a solutions was found.

The culprit

After spending some time investigating the issue by going through logs, analyzing network dumps, and searching the internet, I came across a post on the OpenWRT forum titled ‘MS-TEAMS breaks NCM in trunk. Debugging help needed’. This post caught my attention as it described the same behavior that I was experiencing.

Microsoft Teams was causing my portable router to drop the tethering connection consistently after a short period of time. Even prior to troubleshooting this issue, I found that using Teams was not a very enjoyable experience for me, to put it mildly.

Finding the firmware

While browsing for the OpenWRT site for alternative firmwares and attempting to install the options provided I discovered that non of them could update the router from 3.125 to newer 4.2.1.

However, when I switched to the snapshot type of firmware, to my surprise, the updated firmware version (4.2.1) was available.

Download the 4.2.1 firmware for the Brume GL-MV1000 / GL-MV1000W from here:

This file is for local upgrade in web Admin Panel and Uboot.

Updating the firmware

Although the updater offered the option to keep my current configuration after the update, it did not work as intended in my case. As a result, I had to manually configure the settings in the new firmware.

However, I discovered that creating a backup of the original 4.2.1 installation allowed me to modify the configuration files and then easily import the backup, saving me the hassle of having to repeatedly navigate through the graphical user interface.

Bob’s your uncle!