Hi,
Unfortunately, there is still no estimated release date for the B3000 firmware, and it may take some additional time before it becomes available.
Hi,
Did the GL’B3000 Marble reach EOL? or a newer firmware release is still being worked on?
Hi,
The GL-B3000 has not reached the EOL, and a newer firmware release remains planned.
We understand your concern—the gap since the last update has been much longer than expected. However, we do not yet have a confirmed target version or release date, and we do not want to provide an estimate that may prove unreliable. We will share confirmed release information in this topic when it becomes available.
Thank you for bearing with us.
I have to say that I am becoming increasingly frustrated and disappointed with how this topic has been handled.
I first reported the significant WAN speed degradation caused by enabling the OpenVPN server on the GL-B3000 back in October 2025. After further testing and investigation, GL.iNet confirmed on October 22 that the issue had been reproduced and would be forwarded to R&D. On November 13, I was told that the team was planning a fix.
Since then, months have passed, and we are still waiting for a solution or even a concrete release timeline.
I have also been told privately by a staff member that R&D had been informed and that a beta firmware incorporating the accumulated B3000 updates would be released. I appreciate the communication, but at this point, assurances that something is being worked on are no longer enough. We need tangible progress.
What makes this particularly disappointing is that this is not a request for a new feature or an enhancement. It is a reproducible performance issue affecting a core networking function, which was reported, investigated, and confirmed by GL.iNet almost a year ago. A router should not suffer such a significant reduction in WAN throughput simply because the OpenVPN server is enabled, particularly when hardware acceleration is enabled.
I understand that software development takes time, that bugs can be difficult to resolve, and that release dates should not be promised without confidence. However, there is a difference between taking the time necessary to deliver a proper fix and leaving customers waiting for months without meaningful updates or a clear indication of progress.
The latest response confirms that the GL-B3000 has not reached end of life and that a firmware update is still planned, but there is still no target version or release date. Frankly, after this much time, that is not very reassuring.
I chose the GL-B3000 expecting reliable performance and ongoing firmware support. I appreciate the staff members who have taken the time to investigate and respond, but customer patience should not be mistaken for acceptance of indefinite delays.
After nearly a year, I believe it is reasonable to expect more than an acknowledgement that the issue exists. We deserve a clear status update and a realistic expectation of when this problem will finally be resolved.
Finally, I want to make it clear that this is not intended to put pressure on anyone personally or offend anyone at GL.iNet. It is simply an honest expression of frustration from a customer who understands that software development, debugging, testing, and support all take time and resources. I appreciate the work involved in delivering reliable firmware, but I also believe that customers should be able to express their concerns when an issue remains unresolved for such a long time. My intention is not to blame anyone, but to highlight the situation and hopefully help move things forward.
Thank you for following up and sharing your concerns. We understand your frustration with the long wait for a resolution to the OpenVPN performance issue.
We have recently begun a new round of firmware updates across several models. This includes v4.3.30 for the MT300N-V2, which has already been released, and v4.3.30 for the AR300M, which is currently undergoing internal testing.
The GL-B3000 is also included in this round of updates. Its next release may remain on the v4.5 branch to reduce the additional development and testing work involved in moving to a newer branch.