Firmware release v2.27

kyson-lok · 2018-04-22T01:20:37.814Z

I doubt that how can you access web when it is bridged.
v2.27 has the functionality of wisp bridge, you can try to connect to main router via wisp, and then select switch button to wisp bridge, and then move it right edge.

Breath81 · 2018-04-23T15:55:44.886Z

Thank you for your answer.
“I doubt that how can you access web when it is bridged.” What do you mean? During the last year I have been connecting your router to a pub wifi hotspot doing:

New connection
Repeater
Selecting the SSID, leaving the password empty, selecting the WISP mode,
Clicking Submit.
After that, the captive portal was opening in my android tv box browser, and I was getting internet.

With the 2.27 version this is not working anymore.

“v2.27 has the functionality of wisp bridge, you can try to connect to main router via wisp, and then select switch button to wisp bridge, and then move it right edge.”
I am confused: Which button? Plus, why should this procedure be completely different from the 2.264?
And again, why is not working with 2.27 but it is working just fine with the 2.264 and previous ones (as I said, it was working, it stopped working with 2.27 and it back working when I re-flashed the old version 2.264).
Now, I have to admit, I am not Bill Gates, but if it worked for 1 year and half and stopped working flashing the 2.27 I would say that there is a big problem with this last version.

Thank you

kyson-lok · 2018-04-24T01:07:29.708Z

@Breath81 Sorry for that I hava misunderstood what you said. That is repeater not bridge mode, and this procedure is the same as 2.264. I’m strange that the repeater doesn’t work for you. It works fine for me. We will try more.

alzhao · 2018-04-24T07:10:10.781Z

For the portal process, v2.27 should be pretty much the same as v2.264 and I tested exactly the same as you today.

What you need to note is that, untick “dns rebind-protection” in dns page. You may need to do this first before connecting repeater.

Breath81 · 2018-04-24T13:10:53.318Z

Thank you. My bad, I used the wrong term. I tried several times, even changing back the DNS of the hotspot provider, and nothing worked. The thing i noticed, the MAC address page didnt change even when I was changing it. I was able to see the changes in Luci, tho.

Breath81 · 2018-04-24T13:12:53.759Z

Hi,
I tried almost everything: I unticked them, I changed the DNS’s to the ones of the hotspot provider and so on, but nothing happened. The hotspot portal wasn’t kicking in, so I could not have access to internet.
I cannot remember if I unticked them before or after, tho. I will install back the 2.27 and see.

However, the weird thing is: I had internet (so I was connected to the hotspot) but internet stopped working as soon as the firmware was updated. Now, if I don’t change my mac address, the hotspot still recognises my router as “already logged in” so I should be able to keep surfing in internet without any problem. Why, after the update, everything stopped working?

gachmuret · 2018-04-25T05:55:19.504Z

kyson-lok:

release v2.27 except mt300n-v1 and mt300a

Hi there,

What do you mean with except mt33n-v1 and mt300a?
In the firmware download section I see that you released a v2.27 firmware for mt300a… is it safe to use?

kyson-lok · 2018-04-25T06:46:07.625Z

@gachmuret Do you mean this url? This is safe to upgrade but doesn’t work with keep configuration file, it means that it is the same as doesn’t keep configuration when upgrading.

gachmuret · 2018-04-25T13:38:55.375Z

Yes, that’s what I meant… my bad, I wasn’t aware that I’m looking in testing folder…

So official v1 has no release yet? What’s the matter? I’m on the test release since its release and didn’t encounter issues… in contrary all seems to be more stable and I see an increase in Luci GUI speed also…

As for keep configuration no problem… one can just backup it and reupload after upgrade.

bengsig · 2018-04-25T16:13:31.810Z

I updated my GL.MIFI today and most things worked. However, the changed LED assignment did not, and I couldn’t correct it using the (advanced) gui. The changes were either not saved or caused the 3g-modem interface to go down. In the end, I had to edit /etc/config/system directly with this contents:

config led ‘led_cloud’
option default ‘0’
option trigger ‘netdev’
option dev ‘tun0’
option sysfs ‘gl-mifi:wan’
option name ‘CLOUD’
option mode ‘link tx rx’

config led ‘led_3g4g’
option default ‘0’
option trigger ‘netdev’
option mode ‘link tx rx’
option sysfs ‘gl-mifi:net’
option name ‘3G4G’
option dev ‘3g-modem’

config led ‘led_wlan’
option name ‘WLAN’
option sysfs ‘gl-mifi:wlan’
option trigger ‘phy0tpt’
option default ‘0’

config led ‘led_lan’
option name ‘LAN’
option sysfs ‘gl-mifi:lan’
option trigger ‘netdev’
option mode ‘link tx rx’
option dev ‘eth1’
option default ‘0’

The lan, wifi and 3g/4g LED’s are for their normaly purpose, while the wan led is up when my OpenVPN connection has been established. One surely confusing thing is that the name of the 3G/4G LED (the right most) isn’t gl-mifi:3gcontrol, but gl-mifi:net

pabzter · 2018-04-25T23:45:35.747Z

Did update on one AR300M to 2.27.

I see the device now properly connects with AES-256-CBC settings however the speed has dropped off tremendously. I’m only able to achieve 3Mbps or so in my normal configuration whereas previously it would do 7-10Mbps pretty regularly. It appears AES-256-CBC really, really hits these small routers hard.

Have not seen any other glaring issues (yet…) but I’ve just started to use 2.27 on one device. The slow down of the VPN was marked and immediately noticeable

kyson-lok · 2018-04-26T01:08:31.279Z

The most critical issue is keeping configuration. So we don’t place it to released directory. Maybe someone care for this.

alzhao · 2018-04-26T06:01:36.166Z

gl-mifi:3gcontrol is usb power control of the modem. Never use it as IO.

rich · 2018-05-01T15:40:37.157Z

Are there plans to provide an update for the MT-300n V1?

kyson-lok · 2018-05-02T02:05:48.156Z

@rich If you don’t care for keeping configuration file issue, you can upgrade manually. Firmware is available in mt300n-v1.

viking777 · 2018-05-02T16:06:41.267Z

I posted a couple of weeks ago that since attempting the upgrade to firmware version 2.27 my A300M was bricked, with no way to reach the user interface.
I notice today that that is not quite the case, by doing a few things differently I am able to get some life out of it - not enough to use it, but enough to confirm that it is not completely bricked.
The things I had to do differently were:

Only boot my pc after connecting the router, not before
Connect on 192.168.1.1, instead of 192.168.8.1.
Use a different browser (not Firefox).
When I do these things I can get into the luci interface.
From there I flashed a backup of my previous configuration, which worked, and restored my root password and even restored the wifi network to life which was previously completely dead.

So the router cannot be beyond repair, and I would like to get it back again, but I ONLY have access to the luci interface not to the main UI, and I am not familiar enough with that interface to be able to get main UI going again (for all I know it might not even be possible).

Is there a way that I can achieve this from luci and if so what is it?

Edit: I have just reconnected the gli router to my modem and it is working perfectly, I am posting this edit with wifi internet provided by the gli, so it is in no way bricked, however I am still completely unable to connect to the default UI and so am unable to control such things as my vpn. The luci Network/Interfaces shows a vpn ‘tun0’ connection but it is not active.

viking777 · 2018-05-02T18:49:50.395Z

I ssh’d into the router and read www/index.html - which I think is the correct address for the Normal UI - this is what it reads, is there something wrong here?

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11$
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Cache-Control" content="no-cache" />
<meta http-equiv="refresh" content="0; URL=/cgi-bin/luci" />
</head>
<body style="background-color: white">
<a style="color: black; font-family: arial, helvetica, sans-serif;" href="/cgi-$
</body>
</html>

blue-wavenet · 2018-05-02T20:42:45.406Z

Looks to me like you have flashed with the “clean” version…

kyson-lok · 2018-05-03T02:03:13.886Z

@viking777 You should upgrade stardard firmware, here are all firmware for all products, the stardard firmware is located in each product v1 subdirectory.

viking777 · 2018-05-03T10:08:01.425Z

@blue-wavenet - Yes, I did flash the ‘clean’ version - I guess that is wrong.
@kyson-lok - Sorry for being so ignorant about this, but I did read the readme.txt in https://www.gl-inet.com/firmware/ar300m/ and it seems to say something different:

Nand firmware is in “nand” folder. Normally what you use is in this folder.
All other folders is for Nor firmware. For example, “v1” is our stock firmware for Nor flash and “tor” is the tor firmware for Nor flash.

Also, when I try to flash a file from the v1 folder I get the message:

The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform.

Could somebody please point me at the ‘exact’ file I need to flash to recover my router?

Thank you in advance.

Edit: I did try this file: https://www.gl-inet.com/firmware/ar300m/nand/v1/openwrt-ar300m-nand-2.264.tar but it still does not have the normal UI, only luci.