Beryl / MT3000 and Repeater issues dating back years

I have come here to express my frustration with GLiNET performance as regards the basic function to connect to another Wifi Network in Repeater mode; especially to 5GHz networks, a common problem in my experience.

I have been through many iterations of FW, am now on 4.7.4 stable, yet the connectivity issues persist. Solutions range from changing country codes (not sure if still possible) to manually selecting 2.4GHz connectivity, to disabling the DFS Channel Option, to only choosing channels below 48, because Auto tries to connect to 5GHz bit just sits there with messages that it is "Getting" an IP and never goes any further.

I have to ask, if you have to manually change to 2.4GHz to get a connection, why can't the Auto mode do that, just give up on 5GHz (which rarely works for me anwyay) and select 2.4Ghz based on an apparent inability to connect at 5GHz.

I am pretty sure this isn't limited to the Beryl, but I really would have thought GLiNET would have sorted this out by now, for a Travel Router, which is exactly what you need this basic functionality for.

No-one wants to rock up to a Hotel Room or Airport and pfaff around with the Router for an hour, come on GLiNET, surely you can fix that and make it reliable, so folks can say "it just works". Make that your challenge.


Has worked fine for me and I travel for a living. Use the op24 firmware.

1 Like

Fair enough and I am happy that works for you (yes I tried it, wasn't perfect for me, kept disconnecting), but TBH folks shouldn't have to use a 3rd party FW (even if parts are integrated into GLiNET FW later). IMO, the number of people who have problems with it speaks for itself.

Most folks won't elect to install that op24 FW, they will use the GLiNET FW and jusy say yes to the stable track updates.

[EDIT] btw, when yours does connect, is it mostly at 2.4GHz or 5GHz?

A combination of both. Doesn’t seem to matter what it connects to, it stays connected for the period of my stay.

1 Like