ZBT-WG3526 - discussion [open-wrt] | Wi-Fi Router: 300Mb \ s - 900Mb \ s + 5x1Gb | 1 x USB 3.0
Firmware Statistics
What firmware do you have on the ZBT-WG3526?
Stock [ 4 ] ** [7,84%]
Openwrt [ 15 ] ** [29,41%]
LEDE [ 11 ] ** [21,57%]
Pandorabox [ 2 ] ** [3,92%]
Padavan [ 19 ] ** [37,25%]
Total votes: 51
 



Rep: (15)
ZBT-WG3526 Open-Wrt - Discussion
Wi-Fi Router: 2.4GHz (300Mbit \ s) - 5GHz (900Mbit \ s) + 5x1Gbit \ s | USB 3.0 x 1 | SATA x 1 | Internal PCI-e

Attached Image


Description
Additional Images
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image
Attached Image


The ZBT-WG3526 wireless router is delivered using MTK (MediaTek), the new MT7621 dual-core network chip with a clock frequency of up to 880 MHz, providing five adaptive Ethernet interfaces 10/100/1000 m, 1x USB 3.0 (external) and in addition to the PCIE SATA Interface!
Specifications
Type: wireless router

Size 235 * 165 * 20mm

Power: 12 VDC, 2.5 A
Connector type: barrel

CPU1: MediaTek MT7621AT (880 MHz, 2 cores)
FLA1: 16 MiB (Winbond W25Q128FVSG)
RAM1: 512 MiB (Nanya NT5CB256M16BP-D1)
Expansion IFs: USB 3.0, SATA, Micro SD Card slot
USB ports: 1
SATA ports: 1
JTAG: yes
Serial: yes

WI1 chip1: MediaTek MT7603E
WI1 802dot11 protocols: bgn
WI1 MIMO config: 2x2: 2
WI1 antenna connector: RP-SMA
WI2 chip1: MediaTek MT7612E
WI2 802dot11 protocols: an + ac
WI2 MIMO config: 2x2: 2
WI2 antenna connector: RP-SMA

ETH chip1: MediaTek MT7621AT
Switch: MediaTek MT7621AT
LAN speed: 10/100/1000
LAN ports: 4
WAN speed: 10/100/1000
WAN ports: 1

abgn + ac

Additional chips
Serial ATA Controller; ASMedia; ASM1062 ;; 1;

Stock bootloader: U-Boot

Stock FW OS: Linux 3.10.14 Ralink SDK

Third party firmware supported: LEDE Project • (List), OpenWrt, Padavan (unofficially)

Default IP address: 192.168.1.1
the IP 192.168.1.1 is used by 989 additional devices
of which 3 are ZBT devices
Default login user: admin
Default login password: admin
admin: admin credentials used by 964 additional devices
of which 2 are ZBT devices

802dot11 OUI: none specified

Firmware
Useful


There is no curator in the subject. For questions about filling the caps, please contact the section moderators via the COMPLAINT button under the messages.

Post has been editedRamsteiner - 29.04.19, 21:07
Reason for editing: Hat redesign, performed by SKALDEK



Rep: (15)
Mvn2000 @ 08/08/17, 0:34*
No, not because of this. There are only two revisions - 16/32 MB.


I was mistaken, I meant versions with and without the LTE module.

Also, the seller has now unsubscribed that there are no repositories with packages on the stock firmware. But for the rest, all the jambs with Wi-Fi and others are repaired. Bullshit of course ....

Question: And what threatens the fact that on the ice you need to choose a manual channel? It works (well, the wifi analizer drove and chose) .... Or some pitfalls?

Post has been editedvarvar87 - 09.08.17, 19:04



Rep: (22)
* varvar87 , in any case, channels except 36 do not work on a 5 GHz waffle
Yes, and manually changing the channels on such a device is not comme il faut



Rep: (56)
Zee-X @ 08/09/17, 18:31*
railway on sata is not mounted. how to mount it correctly?


Do you have it in / dev?



Rep: (22)
* alexnik81, yes, displayed



Rep: (56)
* Zee-X,
Is it mounted with your hands?



Rep: (22)
* alexnik81, and did them) after the standard as a usb-drive did not fail

Post has been editedZee-X - 09.08.17, 21:20



Rep: (56)
mdev tried to distort?



Rep: (22)
* alexnik81, earned !!! thank you, + set
only enough until reboot

Post has been editedZee-X - 09.08.17, 21:50



Rep: (7)
People! And by chance, u-boot was not overloaded with anyone. And then the Chinese couple is annoying with its minimalism and hieroglyphs.



Rep: (14)
Zee-X @ 08/09/17, 20:03*
in any case, channels other than 36 do not work on a 5 GHz waffle

In LEDE, all the 5 GHz channels that are in use work if you set the corresponding region.

Zee-X @ 08/09/17, 9:31 PM*
only enough until reboot

Personalization - Scripts - Run after full router startup:
mount -t ext4 / dev / sda1 / opt

I stuck an almost unused gigabyte SLC SSD, bought on Avito for 300 rubles, into the router.

Attached images
Attached Image
Attached Image



Rep: (0)
Let me ask a person who knows nothing about Linux: in order to flash the firmware indicated in the header into this box, does everyone have to go through a quest to install a virtual machine, build, compile, and all that? On the output, each one gets a strictly unique firmware? Or can it be done once, to a person who is well versed in such matters, and in the header indicate a link not to configs, but to a ready-made firmware file?



Rep: (65)
* patient
on the same disk next to the config and the finished firmware lies



Rep: (22)
by the way, concerning a config
for some reason, when building in error. The toolchain is going fine. a little later I will make logs

logs
Making all in scripts
make [6]: enter the directory “/ home / a / prometheus / rt-n56u / trunk / tools / xz / src / scripts”
make [6]: The purpose of “all” does not require command execution.
make [6]: exit the directory “/ home / a / prometheus / rt-n56u / trunk / tools / xz / src / scripts”
make [6]: enter the directory “/ home / a / prometheus / rt-n56u / trunk / tools / xz / src”
make [6]: The all-am target does not require any commands.
make [6]: exit the directory “/ home / a / prometheus / rt-n56u / trunk / tools / xz / src”
make [5]: exit the directory “/ home / a / prometheus / rt-n56u / trunk / tools / xz / src”
Making all in po
make [5]: enter the directory “/ home / a / prometheus / rt-n56u / trunk / tools / xz / po”
make [5]: exit the directory “/ home / a / prometheus / rt-n56u / trunk / tools / xz / po”
Making all in tests
make [5]: enter the directory “/ home / a / prometheus / rt-n56u / trunk / tools / xz / tests”
make [5]: The purpose of “all” does not require command execution.
make [5]: exit the directory “/ home / a / prometheus / rt-n56u / trunk / tools / xz / tests”
make [5]: enter the directory “/ home / a / prometheus / rt-n56u / trunk / tools / xz”
make [5]: exit the directory “/ home / a / prometheus / rt-n56u / trunk / tools / xz”
make [4]: ​​exit the directory “/ home / a / prometheus / rt-n56u / trunk / tools / xz”
make [3]: exit the directory “/ home / a / prometheus / rt-n56u / trunk / tools / xz”
gcc -Wall -O2 -I. -I / usr -I / home / a / prometheus / rt-n56u / trunk / tools / mksquash_xz-4.0 /../ xz / src / liblzma / api -D_FILE_OFFSET_BITS = 64 -D_LARGEFILE_SOURCE -D_GNU_SOURCEAULTOMECODPZULTPDCPLCPDC "-Wall -DGZIP_SUPPORT -DXZ_SUPPORT -DXATTR_SUPPORT -DXATTR_DEFAULT -c -o mksquashfs.o mksquashfs.c
gcc -Wall -O2 -I. -I / usr -I / home / a / prometheus / rt-n56u / trunk / tools / mksquash_xz-4.0 /../ xz / src / liblzma / api -D_FILE_OFFSET_BITS = 64 -D_LARGEFILE_SOURCE -D_GNU_SOURCEAULTOMECODPZULTPDCPLCPDC "-Wall -DGZIP_SUPPORT -DXZ_SUPPORT -DXATTR_SUPPORT -DXATTR_DEFAULT -c -o read_fs.o read_fs.c
gcc -Wall -O2 -I. -I / usr -I / home / a / prometheus / rt-n56u / trunk / tools / mksquash_xz-4.0 /../ xz / src / liblzma / api -D_FILE_OFFSET_BITS = 64 -D_LARGEFILE_SOURCE -D_GNU_SOURCEAULTOMECODPZULTPDCPLCPDC "-Wall -DGZIP_SUPPORT -DXZ_SUPPORT -DXATTR_SUPPORT -DXATTR_DEFAULT -c -o sort.o sort.c
gcc -Wall -O2 -I. -I / usr -I / home / a / prometheus / rt-n56u / trunk / tools / mksquash_xz-4.0 /../ xz / src / liblzma / api -D_FILE_OFFSET_BITS = 64 -D_LARGEFILE_SOURCE -D_GNU_SOURCEAULTOMECODPZULTPDCPLCPDC "-Wall -DGZIP_SUPPORT -DXZ_SUPPORT -DXATTR_SUPPORT -DXATTR_DEFAULT -c -o swap.o swap.c
gcc -Wall -O2 -I. -I / usr -I / home / a / prometheus / rt-n56u / trunk / tools / mksquash_xz-4.0 /../ xz / src / liblzma / api -D_FILE_OFFSET_BITS = 64 -D_LARGEFILE_SOURCE -D_GNU_SOURCEAULTOMECODPZULTPDCPLCPDC "-Wall -DGZIP_SUPPORT -DXZ_SUPPORT -DXATTR_SUPPORT -DXATTR_DEFAULT -c -o pseudo.o pseudo.c
pseudo.c: 69: 13: warning: ‘dump_pseudo’ defined but not used [-Wunused-function]
static void dump_pseudo (struct pseudo * pseudo, char * string)
^
gcc -Wall -O2 -I. -I / usr -I / home / a / prometheus / rt-n56u / trunk / tools / mksquash_xz-4.0 /../ xz / src / liblzma / api -D_FILE_OFFSET_BITS = 64 -D_LARGEFILE_SOURCE -D_GNU_SOURCEAULTOMECODPZULTPDCPLCPDC "-Wall -DGZIP_SUPPORT -DXZ_SUPPORT -DXATTR_SUPPORT -DXATTR_DEFAULT -c -o compressor.o compressor.c
gcc -Wall -O2 -I. -I / usr -I / home / a / prometheus / rt-n56u / trunk / tools / mksquash_xz-4.0 /../ xz / src / liblzma / api -D_FILE_OFFSET_BITS = 64 -D_LARGEFILE_SOURCE -D_GNU_SOURCEAULTOMECODPZULTPDCPLCPDC "-Wall -DGZIP_SUPPORT -DXZ_SUPPORT -DXATTR_SUPPORT -DXATTR_DEFAULT -c -o gzip_wrapper.o gzip_wrapper.c
gcc -Wall -O2 -I. -I / usr -I / home / a / prometheus / rt-n56u / trunk / tools / mksquash_xz-4.0 /../ xz / src / liblzma / api -D_FILE_OFFSET_BITS = 64 -D_LARGEFILE_SOURCE -D_GNU_SOURCEAULTOMECODPOMPDCPLCPDC "-Wall -DGZIP_SUPPORT -DXZ_SUPPORT -DXATTR_SUPPORT -DXATTR_DEFAULT -c -o xz_wrapper.o xz_wrapper.c
gcc -Wall -O2 -I. -I / usr -I / home / a / prometheus / rt-n56u / trunk / tools / mksquash_xz-4.0 /../ xz / src / liblzma / api -D_FILE_OFFSET_BITS = 64 -D_LARGEFILE_SOURCE -D_GNU_SOURCEAULTOMECODPZULTPDCPLCPDC "-Wall -DGZIP_SUPPORT -DXZ_SUPPORT -DXATTR_SUPPORT -DXATTR_DEFAULT -c -o xattr.o xattr.c
gcc -Wall -O2 -I. -I / usr -I / home / a / prometheus / rt-n56u / trunk / tools / mksquash_xz-4.0 /../ xz / src / liblzma / api -D_FILE_OFFSET_BITS = 64 -D_LARGEFILE_SOURCE -D_GNU_SOURCEAULTOMECODPZULTPDCPLCPDC "-Wall -DGZIP_SUPPORT -DXZ_SUPPORT -DXATTR_SUPPORT -DXATTR_DEFAULT -c -o read_xattrs.o read_xattrs.c
gcc mksquashfs.o read_fs.o sort.o swap.o pseudo.o compressor.o gzip_wrapper.o xz_wrapper.o xattr.o read_xattrs.o -lpthread -lm -lz / home / a / prometheus / rt-n56u / trunk / tools / mksquash_xz-4.0 /../ xz / src / liblzma / .libs / liblzma.a -o mksquashfs
gcc -Wall -O2 -I. -I / usr -I / home / a / prometheus / rt-n56u / trunk / tools / mksquash_xz-4.0 /../ xz / src / liblzma / api -D_FILE_OFFSET_BITS = 64 -D_LARGEFILE_SOURCE -D_GNU_SOURCEAULTOMECODPZULTPDCPLCPDC "-Wall -DGZIP_SUPPORT -DXZ_SUPPORT -DXATTR_SUPPORT -DXATTR_DEFAULT -c -o unsquashfs.o unsquashfs.c
gcc -Wall -O2 -I. -I / usr -I / home / a / prometheus / rt-n56u / trunk / tools / mksquash_xz-4.0 /../ xz / src / liblzma / api -D_FILE_OFFSET_BITS = 64 -D_LARGEFILE_SOURCE -D_GNU_SOURCEAULTOMECODPZULTPDCPLCPDC "-Wall -DGZIP_SUPPORT -DXZ_SUPPORT -DXATTR_SUPPORT -DXATTR_DEFAULT -c -o unsquash-1.o unsquash-1.c
gcc -Wall -O2 -I. -I / usr -I / home / a / prometheus / rt-n56u / trunk / tools / mksquash_xz-4.0 /../ xz / src / liblzma / api -D_FILE_OFFSET_BITS = 64 -D_LARGEFILE_SOURCE -D_GNU_SOURCEAULTOMECODPZULTPDCPLCPDC "-Wall -DGZIP_SUPPORT -DXZ_SUPPORT -DXATTR_SUPPORT -DXATTR_DEFAULT -c -o unsquash-2.o unsquash-2.c
gcc -Wall -O2 -I. -I / usr -I / home / a / prometheus / rt-n56u / trunk / tools / mksquash_xz-4.0 /../ xz / src / liblzma / api -D_FILE_OFFSET_BITS = 64 -D_LARGEFILE_SOURCE -D_GNU_SOURCEAULTOMECODPZULTPDCPLCPDC "-Wall -DGZIP_SUPPORT -DXZ_SUPPORT -DXATTR_SUPPORT -DXATTR_DEFAULT -c -o unsquash-3.o unsquash-3.c
gcc -Wall -O2 -I. -I / usr -I / home / a / prometheus / rt-n56u / trunk / tools / mksquash_xz-4.0 /../ xz / src / liblzma / api -D_FILE_OFFSET_BITS = 64 -D_LARGEFILE_SOURCE -D_GNU_SOURCEAULTOMECODPZULTPDCPLCPDC "-Wall -DGZIP_SUPPORT -DXZ_SUPPORT -DXATTR_SUPPORT -DXATTR_DEFAULT -c -o unsquash-4.o unsquash-4.c
gcc -Wall -O2 -I. -I / usr -I / home / a / prometheus / rt-n56u / trunk / tools / mksquash_xz-4.0 /../ xz / src / liblzma / api -D_FILE_OFFSET_BITS = 64 -D_LARGEFILE_SOURCE -D_GNU_SOURCEAULTOMECODPOMPDCPLCPDC "-Wall -DGZIP_SUPPORT -DXZ_SUPPORT -DXATTR_SUPPORT -DXATTR_DEFAULT -c -o unsquashfs_xattr.o unsquashfs_xattr.c
gcc unsquashfs.o unsquash-1.o unsquash-2.o unsquash-3.o unsquash-4.o swap.o compressor.o gzip_wrapper.o xz_wrapper.o read_xattrs.o unsquashfs_xattr.o -lpthread -lm -lz / home /a/prometheus/rt-n56u/trunk/tools/mksquash_xz-4.0/../xz/src/liblzma/.libs/liblzma.a -o unsquashfs
mkdir -p /home/a/prometheus/rt-n56u/trunk/tools/mksquash_xz-4.0/../bin
cp mksquashfs /home/a/prometheus/rt-n56u/trunk/tools/mksquash_xz-4.0/../bin/mksquashfs_xz-4.0
cp unsquashfs /home/a/prometheus/rt-n56u/trunk/tools/mksquash_xz-4.0/../bin/unsquashfs_xz-4.0
make [2]: exit the directory “/home/a/prometheus/rt-n56u/trunk/tools/mksquash_xz-4.0”
make [1]: exit the directory “/ home / a / prometheus / rt-n56u / trunk / tools”
make ARCH = mips CROSS_COMPILE = / opt / rt-n56u / toolchain-mipsel / toolchain-3.4.x / bin / mipsel-linux-uclibc- -j8 -C linux-3.4.x || exit 1
make: /opt/rt-n56u/toolchain-mipsel/toolchain-3.4.x/bin/mipsel-linux-uclibc-gcc: Command not found
make [1]: entry into the directory “/home/a/prometheus/rt-n56u/trunk/linux-3.4.x”
/ bin / sh: 1: /opt/rt-n56u/toolchain-mipsel/toolchain-3.4.x/bin/mipsel-linux-uclibc-gcc: not found
/ bin / sh: 1: /opt/rt-n56u/toolchain-mipsel/toolchain-3.4.x/bin/mipsel-linux-uclibc-gcc: not found
/ bin / sh: 1: /opt/rt-n56u/toolchain-mipsel/toolchain-3.4.x/bin/mipsel-linux-uclibc-gcc: not found
/ bin / sh: 1: /opt/rt-n56u/toolchain-mipsel/toolchain-3.4.x/bin/mipsel-linux-uclibc-gcc: not found
make [1]: /opt/rt-n56u/toolchain-mipsel/toolchain-3.4.x/bin/mipsel-linux-uclibc-gcc: Command not found
CHK include / linux / version.h
CHK include / generated / utsrelease.h
CC scripts / mod / empty.o
/ bin / sh: 1: /opt/rt-n56u/toolchain-mipsel/toolchain-3.4.x/bin/mipsel-linux-uclibc-gcc: not found
scripts / Makefile.build: 307: recipe execution error for the target "scripts / mod / empty.o"
make [3]: *** [scripts / mod / empty.o] Error 127
make [3]: *** Waiting for task completion ...
HOSTCC scripts / mod / mk_elfconfig
CC kernel / bounds.s
/ bin / sh: 1: /opt/rt-n56u/toolchain-mipsel/toolchain-3.4.x/bin/mipsel-linux-uclibc-gcc: not found
/home/a/prometheus/rt-n56u/trunk/linux-3.4.x/./Kbuild:35: error executing the recipe for the target "kernel / bounds.s"
make [2]: *** [kernel / bounds.s] Error 127
Makefile: 993: recipe execution error for target “prepare0”
make [1]: *** [prepare0] Error 2
make [1]: *** Waiting for the completion of tasks ...
scripts / Makefile.build: 443: recipe execution error for the scripts / mod target
make [2]: *** [scripts / mod] Error 2
Makefile: 503: recipe execution error for the scripts target
make [1]: *** [scripts] Error 2
make [1]: exit from the directory “/home/a/prometheus/rt-n56u/trunk/linux-3.4.x”
Makefile: 137: recipe execution error for linux target
make: *** [linux] Error 1


the most interesting thing is that the file /opt/rt-n56u/toolchain-mipsel/toolchain-3.4.x/bin/mipsel-linux-uclibc-gcc exists

Post has been editedZee-X - 10.08.17, 13:21



Rep: (56)
Zee-X @ 08/09/2017, 21:31*
*
only enough until reboot

Well into the scripts
Mvn2000 @ 08/10/2017, 11:00*
...

Personalization - Scripts - Run after full router startup:
mount -t ext4 / dev / sda1 / opt

Add.
True for full-time work better or through
/sbin/automount.sh sdax Label

Where sdax is the desired partition. Label - Any valid name for the folder in / media.
Or mdev -s.



Rep: (27)
Zlomen @ 08/10/17, 07:22*
People! And by chance, u-boot was not overloaded with anyone. And then the Chinese couple is annoying with its minimalism and hieroglyphs.


there issucha project, but not for a mipsel, it seems. Study at your leisure, otherwise I fell out of the clip for a while



Rep: (7)
There is such a project
And what is bad about this.https://github.com/bky...tree/master/uboot/mips
It should seem to be closer. I never collected anything from source codes, therefore I am not ready yet.

Post has been editedzlomen - 11.08.17, 10:38



Rep: (27)
Well, I'm with you again. Following the standard link above, one more compiled firmware (the word anonym is in the file name). Updated:

Samba up to 3.6.25 - thanks to the LEDE project
dnsmasq to 2.77
KMS server build 1111. True, so far I had to turn it on with my hands. Do
echo "/ usr / bin / vlmcsd -j /etc_ro/vlmcsd.kmd -l syslog -L 0.0.0.0:1688">>/etc/storage/post_wan_script.sh
in the console, or insert a line acc. script through admin panel.
Fighters with RosKomNadzor - Tor, Privoxy, DNSCrypt. Included through the admin panel in "Advanced =>Administration ", managed in the same place. Padawan source patchesby thispatch, they bow. Thor copied without GeoIPv6, only v4



Rep: (56)
And what is bad about this.https://github.com/bky...tree/master/uboot/mips
It should seem to be closer. I never collected anything from source codes, therefore I am not ready yet.

The fact that the web is not there.



Rep: (7)
The fact that the web is not there

oops: russian_ru:



Rep: (58)
Greetings to all! and immediately on the matter with questions to you comrades! ;)

That's how 2 years I have two xiaomi mi-3 (128mb) work perfectly! (firmware padawan) between them a 5 hertz bridge transmit IPTV.
but having read about the quality of the memory and the power supply, I decided not to destroy my syaomak and did not drive the transports and films from the screw. Syaomka is only 100mbps and this is not enough for me to work qualitatively.
dreamed about (1 GB in LAN and a van to the provider, enough waffles) for Asus did not dare! and then I came across: ZBT WE1326 (1GB-512MB), I ordered everything was sent fine, it seems like it’s openVRT with gui from Lusi all on MT as on syaomke, what can I describe! everything in the subject))
so that’s what comrades need! I want to establish this beast ZBT WE1326 on the Padawan and if I dance it I will order another such handsome one))
Xiaomi sewed according to the instructions Prometeus from the forum 4 PDA he figured it out without problems! but here I didn’t understand a bit .. I don’t want Brick and reanimate it ...
If it’s not difficult for anyone to lay out the instructions in detail, please or link how to reliably switch to Padawan. : thank_you:


Full version    

Help     rules

Now: 09/16/19, 12:03