Meet Brume 2!

Thank you but we are the long promised firmware updates for the existing devices other than the ones that are undergoing beta testing?

3 Likes

I do not think it is good business practice just to bring out new devices, due to shortages of old chips, when they do not work well from Day 1 and still have many bugs to be resolved. Although this strategy appears to work in the short term, both old customers and the new customers may end up becoming non-customers.

Manufacturers in all industries commonly substitute parts for various reasons (availability, price, reliability, efficiency, etc.), while keeping the core design and functions and without referring to them as ā€œnew productsā€. However, there is temptation among some manufacturers to start adding new features and enhancements at the same time to market them as ā€œnew productsā€. In smaller companies, this tends to contribute to new bugs in new products and divert away limited resources on old bugs in old products.

I do not work for and I do not have formal association with GL.iNet

6 Likes

We promise to update the firmware but pls forgive me that sometimes it may be slow.

3 Likes

I think there is more going on with the introduction of new devices than just shortages of old chips. I agree that there should be continued support of devices for a reasonable time, and that end of production should not mean EOL.

But I actually like this effort to continue to upgrade specs. Just in the travel router space, Iā€™m seeing dramatic improvements in ISP speeds such that 100/100 is now prevalent, where just a few years ago 25/1 was the norm (just now Iā€™m in a place with 500/300 service!. So my Mango is outclassed here.) The progression from Mango to Slate to Beryl to Slate Plus to Slate AXT seems something to be encouraged, just as phones are driving higher core count, lower power chips. I think this strategy of pairing closed source/open source drivers to OpenWRT with a very accessible GL-iNet overlay is fairly productive and Iā€™m pleased to see that there is as much open and active work going on (by both the user community and GL-iNet) to identify and address bugs.

7 Likes

There are often more than a single factor when creating new products and they have likely been in the design/development pipeline for some time already. GL.iNet themselves have referenced chip availability as the main reason.

Regardless of the decision factors, I agree overall that introducing new technology features and enhancements are good, even necessary and inevitable. However, the main point is about being able to not have bugs in the new products and to fix the bugs in the old products on a timely basis.

5 Likes

I can understand why you are upset. But on the other hand I am pretty sure, if Iā€™ve had a problem with any kind of standard setup, and this behavior can be reproduced, the GL.iNet team will take a look and if anyhow possible solve it.
I also understand, that the Team can not do magic against non-standard-implementations and people with a real interest to keep VPN out (like hotels).

And I donā€™t write this, because I am a naive person. I write this from experience. Iā€™ve hat a longer case, in which we even send a router from one side of the world to the other. And shortly after a lot of issues in 4.0 are ā€˜magicallyā€™ solved. And here I also understand that GL.iNet can not buy every router on the world wide market. Here is a little testing up to us (the users).
I am thankful for this forum to place my demands.

I was nice, now it is up to you, GL.iNet! I want a 50 gram router, that produces no heat without a fan, has a 2km 5GHz WLAN coverage at a minimum speed of 600Mbit/s and it should not consume more power than 500mA. Release next week would be nice :slight_smile:

4 Likes

No upset from me at all ! I personally do not have significant problems with GL.iNet products and have tried to assist other people to solve their problems, many of which are pretty standard and just require some explaining.

There are both positive and negative posts on this forum and, for any product, there will always be lovers and haters depending on their own expectations and circumstances. I am offering my own feedback on GL.iNetā€™s direction and it is up to them what to do with it.

6 Likes

I think that you are completely missing the point here. No one is against technological advancement or wanting to stifle product development by any stretch of the imagination. We are all here after all because we like our gadgets and enjoy new tech. We are all also quite happy to be used as beta users after spending good money on their products to try and help improve these products. I am, however concerned about the companyā€™s commitment to their customers (although you donā€™t seem to think that repeat customers are important but I have bought a total of 32 GL.iNet routers (with 5 of the models already gone EOL) for myself, family and friends) or to their products. How many tech manufacturers have you seen releasing a beta products before their previous one is even out of beta? GL.iNet appear to be quickly and easily forgetful of their previous products as soon as a new one is hyped up for release! Their flagship RECENT router ā€œthe FLINTā€ for example has had its last stable firmware version released back in May with version 3.214 and with all development stalled there whilst the customers watch testing firmware versions released left, right and centre for the newer products and feeling completely abandoned by the developers. A lot of the recent reviews on Amazon have started to complain about outdated versions of firmware. Your Beryl or Slate AX will soon follow suit once this Brume 2 is released. You watch this space.

5 Likes

Just found out about Brume 2. Have been using original Brume as my router for quite some time with great results. (for WiFi, Iā€™m using a pair of EAP660HD)ā€¦

How long will the Brume receive support and firmware upgrades? 2 years?

2 Likes

Yes. 2 years when we announce EOL.

1 Like

Whatā€™s the price and will it be available on Amazon?

Why is LAN port 10/100/1000 while WAN is up to 2.5Gbps ?
ā€“ this router wont work with 2Gbps fiberā€¦

I would hope they would make the LAN side the 2.5gbps

Hi,Due to the limitation of MT7981 SOC, MT7981 only supports one GE PHY and two SGMIL,SGMIL-1 is used as the USB3.0 Port and SGMIL-0 is used as the 2.5G Ethernet Port.

2 Likes

will Brume 2 be more powerull than Slate AX when it comes to Wireguard performance?
More 2.5gbps ports would have been a dream!

1 Like

Will it be possible to use a USB 3.0 - 10/100/1000/2500 Ethernet dongle to take advantage of higher throughput ? ā€“ and use it a high-speed LAN port? Thatā€™s a realistic workaround I think.

Since Brume 2 only has one LAN port, might as well have two. O

Not much stronger, Brume has a WireGuard speed of 450Mbpsļ¼ˆMAX.), while AXT1800 has 550Mbps. But Openvpn speeds are about the same.

Yes,the USB3.0 interface uses SGMII_1, while the maximum speed supported by SGMILL is 2.5G.

2 Likes

I am currently using Brume 1 with a GL.inet-supported dongle (I believe RTL8812AU) as my primary access point at home. It is rock solid stable, performs very well, and I would really really love to see GL.inet stock firmware support a couple good modern wifi chipsets on all GL.inet models. The Mediatek 76xxU chipsets might be good candidates.

2 Likes

As part of the overall discussion on product & firmware development,

I would also like to see a bit more attention paid to firmware quality. The GL.inet firmware works well, and for the moment I prefer to use it when I can.

However, bugs often remain for a long time, including ā€œmissing stairā€ type bugs that will stop a newbie in their tracks (like the fact that root password can become inconsistent between http and https login page, or between web interface and ssh) and arenā€™t well documented anywhere. I would love it if a few more of these bugs would get fixed, and would be fine if product development slowed down a bit as a result of that.

Iā€™ve been using Linux-based technologies for nearly 30 years so these little devices are a good deal for me because Iā€™m capable of tinkering with them until they work the way I want. But there are a good number of (mostly) small but frustrating bugs which will make the experience less pleasant for somebody who has less experience.

In my case, I am slowly building up all the knowledge I need so that I can do everything I want as easily with vanilla OpenWRT as with GL.inet firmware, and this is so I wonā€™t have to depend on GL.inetā€™s slower release cycle any more. Not everyone has the time, skill, or resources to do that, and the people that donā€™t, are less likely to continue buying the products if the stock firmware isnā€™t updated enough.

Thanks as always to the GL.inet team as I know they work hard.

8 Likes