Support for ZBT-WE1326 (was: New product! 2.4GHZ/5.8GHz Openwrt 802.11AC dual band dual core wifi router with SD card slot)

For Developers
63

I still haven't had the chance to load that image. I will try when I have a free weekend. However, regarding the failsafe recovery on the WE-1326. Does this router only provide a web interface when in recovery? Is there a way to access cli ssh in openwrt when in recovery? I ask because on my TPlink WDR-4300 I could still access CLI in recovery to restore backuped up bin files, and such to recover it. With the WE-1326, if I mess something up I've had to put in recovery, load the default firmware (mt7621-openwrt-512m-20171208.bin) within the recover web interface, and then ssh into it to recovery my last backed up bin to restore my settings (see below script). Is there an easier method to what I am doing?

Script:

cd /tmp
rm *.bin
dd if=/dev/mtd0 of=/tmp/all.bin
dd if=/dev/mtd1 of=/tmp/bootloader.bin
dd if=/dev/mtd2 of=/tmp/config.bin
dd if=/dev/mtd3 of=/tmp/factory.bin
dd if=/dev/mtd4 of=/tmp/firmware.bin
dd if=/dev/mtd5 of=/tmp/rootfs.bin
dd if=/dev/mtd6 of=/tmp/rootfs_data.bin

#Backup /etc/config
rsync -av /etc/config /mnt/32GB/we1326

#Backup Firmware
rsync -av /tmp/*.bin /mnt/32GB/we1326

#Rsync to 150GB
rsync -av /mnt/32GB/we1326 /mnt/150GB/

#opkg list backup
opkg list_installed | cut -f 1 -d ' ' >> /mnt/32GB/we1326/opkg_installed
opkg list_installed | cut -f 1 -d ' ' >> /mnt/150GB/we1326/opkg_installed
64

matsic,

So I downloaded this image. I ssh'd into openwrt:

sysupgrade -v lede-ramips-mt7621-zbt-we1326-squashfs-sysupgrade.bin

It finishes, and reboots. However, my PC never gets an ip address again. Even manually assigning an ip I cannot access the router via web or ssh. I have to force the router back into restore, load default firmware, and restore my backup firmware.bin to get it working again.

How did you upgrade to LEDE from openwrt? It should be as simple as sysupgrade, but that doesn't seem to work. Can I only upgrade via ZBT restore boot mode?

65

just use LUCI page to flash image and use keep settings

66

Is there a LEDE build yet that properly has the sd card slot working?

67

No. We don't have it now.
Thank you!

elina@fusonwap.com

68

@matsic I installed your fimware but am using the we1326 with an internal PCIe LTE card, the Quectel EC25 (Got it like this). It doesn't show up in the Interfaces overview. I assume either drivers are missing or I need to update / add some packages, however I am unsure what exactly is missing. Do you know what the problem could be?

69

I have no LTE in my device so cannot check it.
Just tested work SD card and USB flash card 8 GB.

70

Hello, I just got this router a few days ago, the 4G LTE sim card slot version. I've managed to browse the internet from inside the OpenWRT firmware (through ssh, of course) and it's using the 4G connection (it's the only way anyway, I don't connect it with any other source), but other devices connecting to this router cannot do the same.

I have a AP connected to br-lan network, which bridges several interfaces, except the 4G one (not appeared on the physical settings list). I believe this is why connected devices cannot browse as the firmware does, because incoming requests can't be forwarded to the 4G interface. How should I proceed? Thanks in advance.

71

OK, kill me for not recognizing "masquerading" option in the firewall settings. It's working now.

72

So,

Like @drbrains, I nuked mine, and ignored it forever, since most of my household was still on 2.4Ghz. I've got a functional ZBT-WE1326, and I'd like to make more progress on this..

@matsic - Do you have a copy of your local setup I can rebase to 17.01.4? I see you're using a more recent kernel than the -snapshot builds, but I am not sure what else you've done other than add the device support, bundle LuCi, et al..

73

My ZBT-WE1326 refuses to work with the ZBT-WE1326 openwrt image. Instead, it works fine with ZBT-WE2626 image.

74

The snapshot images don't have LuCI or anything like that. Is it that it didn't work, or that you had issues accessing the router?

I'd be interested to see your dmesg/lsmod info using the WE2626 image- I assume as they're all the same mt76 base with minimal wifi differences that it'll just work- possibly at a loss of image space.

75

@matsic's image works. The latest LEDE/OpenWRT snapshot is still 4.1.x based, and you'll want to use a 4.4.x kernel- so, no. This device -is still not officially supported- still lacks a current build with all standard tools.

76

"config.txt" added to https://mega.nz/#F!8UUTTAIQ!CJaaoS0QicKmFeiEOX9zxw
It contains all added packages.
It can be that some extra packages added to it as it saved later than that build executed.

1 Like
77

?

Support for WE-1326 has been added with https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=ff258effd508fc75edfb08ba709b333619d3f1e8

78

I mean to imply that there's no "Official" build, yet. We're still stuck in snapshots and no LuCI/etc, that many people expect to be available. I guess that was a bit more typing initially, which should have been rectified.

Also, it's not the most stable on anything but the most current mt76 driver - but that's not really device specific. :confused:

79

I have been trying to get trunk image openwrt-ramips-mt7621-zbt-wg2626-squashfs-sysupgrade.bin working on this router since last week. I did manage to get serial output after opening the hood and soldering in the header pins. On my serial console I now see what sholwe sees:

xhci_pci xhci_hcd gpio_button_hotplug usbcore nls_base usb_common
[   19.330000] CPU: 2 PID: 563 Comm: kmodloader Not tainted 4.4.14 #1
[   19.330000] Stack : 00000000 00000000 804c6842 00000036 00000000 00000000 80470000 804e0000
	  8ec5aea8 80473c63 803ec248 00000002 00000233 804c365c 8fa24010 024000c0
	  80086ba0 80063514 80470000 804e0000 80478158 8047815c 803f0b5c 8f239a9c
	  00000003 8006129c 8fa24010 024000c0 80086ba0 00000000 00000000 00239a9c
	  00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
	  ...
[   19.370000] Call Trace:
[   19.370000] [<800165b0>] show_stack+0x50/0x84
[   19.380000] [<801aaf70>] dump_stack+0x84/0xbc
[   19.380000] [<8002be10>] warn_slowpath_common+0xa0/0xd0
[   19.390000] [<8002bec4>] warn_slowpath_null+0x18/0x24
[   19.390000] [<8f32d444>] mt7603_eeprom_init+0x174/0x420 [mt7603e]
[   19.400000] [<8f329194>] mt7603_register_device+0xec/0x908 [mt7603e]
[   19.400000] [<8f328128>] init_module+0x32128/0x33050 [mt7603e]
[   19.410000] [<801e9e8c>] pci_dev_get+0x1c/0x30
[   19.410000] [<801ea400>] pci_device_probe+0x78/0xe8
[   19.420000] [<8021033c>] driver_probe_device+0x120/0x28c
[   19.420000] [<80210524>] __driver_attach+0x7c/0xb4
[   19.430000] [<8020e828>] bus_for_each_dev+0x94/0xa4
[   19.430000] [<8020fa38>] bus_add_driver+0xf0/0x208
[   19.440000] [<80210c5c>] driver_register+0xb0/0x104
[   19.440000] [<8f2f6048>] init_module+0x48/0x78 [mt7603e]
[   19.450000] [<8000f71c>] do_one_initcall+0x1f0/0x218
[   19.450000] [<80087d9c>] do_init_module+0x74/0x1d4
[   19.460000] [<800896c0>] load_module+0x1750/0x1bf4
[   19.460000] [<80089c60>] SyS_init_module+0xfc/0x140
[   19.470000] [<800077a8>] syscall_common+0x30/0x54
[   19.470000] 
[   19.470000] ---[ end trace a3fb302439587c3f ]---
[   22.610000] mt7603e 0000:02:00.0: Firmware Version: _e1_drv_tv
[   22.620000] mt7603e 0000:02:00.0: Build Time: 20140313215548
[   23.640000] mt7603e 0000:02:00.0: Timeout waiting for ROM code to become ready
[   23.640000] mt7603e: probe of 0000:02:00.0 failed with error -5

The older config had a lot of drivers that the trunk config doesn't. The mt76*ko seem to be all there though.
Trying matsic's image. Glad I ended up here :slight_smile:

80

What would happen if I flashed the latest LEDE snapshot (coming from original factory openwrt), AND cleared settings?

Is it possible to manually install LUCI after flashing snapshot) with or without clearing settings?

81

Yes, and no. There are some "safe" tools available, for instance, LuCI is available for snapshots, but LuCI-ssl isn't. Don't expect there to be any funky filesystem drivers like HFS+, etc..

I'm going to work on rebuilding off of @hnyman's WNDR-3x00 tree, because I've grown to love it, and @matsic's image is still fairly unstable for me with mt76 - for whatever reason, I can run it for days, but the moment i use my Kindle Fire to watch videos, the entire local network tanks and it needs a power reset.

Also, in -HEAD:

48 min ago Felix Fietkau mt76: update to the latest version master commit | commitdiff | tree | snapshot

Yum. Er, I mean Opkg.

1 Like
82

I've posted a new update, but it's based on kernel 4.1.x still; I'll update to 4.4.x when I get a recent SD card to test with.

In the mean time, I suggest using @matsic's installation, unless you want a neutered instance.