• Based on the MediaTek MT7628NN
• 128MB DDR1, 16MB Flash
• USB 2.0 port
• Dual Ethernet (WAN/LAN)
• Button: 1 x switch button, 1 x reset button
• LED: 3 x LEDS (system power led is not GPIO controller)

Please read the article flash.layout for a better understanding. It contains a couple of explanations. Then let's have a quick view at flash layout of this particular device:

Install OpenWrt in GL.Inet devices

Note: It can happen that the browser cache does conflict with the new loaded firmware. This can be avoided by browsing to: http://192.168.1.1/index.html?index. By adding ?index it asked the browser not to load from cache.

→ generic.flashing.tftp

Note: TFTP upgrade requires connecting to the Serial port, and pressing spacebar during boot to access the U-Boot command line.

→ generic.sysupgrade

• Browse to http://192.168.8.1/cgi-bin/luci/admin/system/flashops
• Upload image file for sysupgrade to LuCI
• Wait for reboot

If you don't have a GUI (LuCI) available, you can alternatively upgrade via the command line. There are two command line methods for upgrading:

• sysupgrade
• mtd

Note: It is important that you put the firmware image into the ramdisk (/tmp) before you start flashing.

• Login as root via SSH on 192.168.8.1, then enter the following commands:

cd /tmp
wget https://downloads.openwrt.org/snapshots/targets/ramips/mt76x8/openwrt-ramips-mt76x8-gl-mt300n-v2-squashfs-sysupgrade.bin
sysupgrade /tmp/openwrt-ramips-mt76x8-gl-mt300n-v2-squashfs-sysupgrade.bin

If sysupgrade does not support this router, use mtd.

• Login as root via SSH on 192.168.8.1, then enter the following commands:

cd /tmp
wget https://downloads.openwrt.org/snapshots/targets/ramips/mt76x8/openwrt-ramips-mt76x8-gl-mt300n-v2-squashfs-sysupgrade.bin
mtd write /tmp/openwrt-ramips-mt76x8-gl-mt300n-v2-squashfs-sysupgrade.bin linux && reboot

→ generic.debrick

The U-Boot bootloader has a web interface to update the firmware. To use the web interface, you need to connect to the LAN port, and your computer's ethernet port set to 192.168.1.2/24. To start the web interface:

1. With the router unplugged, press and hold the reset button.
2. Plug in the router.
3. Hold the reset button for at least 3 seconds.
4. Release button, wait a few seconds, and connect to http://192.168.1.1

→ failsafe_and_factory_reset

→ Basic configuration After flashing, proceed with this.
Set up your Internet connection, configure wireless, configure USB port, etc.

The default OEM network configuration is:

Port number 0 is labeled WAN on the unit, port 1 is labeled LAN. Ports 2-5 are not present. Port 6 (CPU) is the internal connection to the router itself. vlan1 = eth0.1, vlan2 = eth0.2 and so on.

→ hardware.button on howto use and configure the hardware button(s). Here, we merely name the buttons, so we can use them in the above Howto.

Original Vendor information

Front:

Back/Backside label:

Each MT300N V2 is assigned a Dynamic DNS address unique to your device.

Use a pry tool in the notch. There are clips all round.

Note the yellow post on the cover that holds the PCB steady. Ensure the cover is replaced with the correct orientation.

PCB front:

→ One port.serial port (J1) on the MT300N V2 comes with the headers factory fitted.

How to connect to the Serial Port of this specific device:

It can be seen at the left end, farthest from the Ethernet port (grey) and is labelled “GND RX0 TX0”. Headers are missing for further connections “VCC” and “I2C_CLK I2C_SD TX1 RX1”. All PINS besides GND and VCC are also usable via GPIO.

→ bootloader

The MT300N V2 has general purpose GPIO pins broken out. Note the headers at the top of the board. These headers are not factory fitted and will need to be fitted manually.

not available.

The 3 way toggle switch comes from the factory with the right-hand third of the plastic part filled, GLI claims this is to prevent confusion over the 3 way toggle, but to keep the feature available when required, decided not to remove the 3-way switch.

The MT300N V2 implements a GPIO switch driver, using the scripts below, the switch position can be determined from shell script and acted upon.

/etc/rc.button/BTN_0
/etc/rc.button/BTN_1

The switch uses GPIOs 42 and 43 and can be access by exporting them as inputs. The values correspond to the switch positions as follows.

Where X indicates a “Don't Care” state.

The scripts receive both a button ID in the form “BTN_X” and an action such as “pressed” or “unpressed”.

Note that to access them as GPIOs (and stop receiving button events), you need to unload the gpio_button_hotplug module, or unbind it by executing:

echo gpio-keys > /sys/bus/platform/drivers/gpio-keys/unbind

Space for additional notes, links to forum threads or other resources.

• …

How to add tags