Half-public something, but not a frequent community build...
(Mwlwifi is crappy abandonware, so I do not take my wrt3200acm that seriously.)
Dear hnyman,
Thanks for the information. I am being encouraged to let others get involved in the conversation - so I am going to go silent for a while. However, thanks for all you do in developing OpenWRT across many platforms.
Peace
now showing error
"Unable to fetch traffic statistic data: JSON.parse: unexpected end of data at line 1 column 16516 of the JSON data"`
I am not sure if this is the right place to ask. It could be a build issue (i.e. different packages used), or just plain understanding. very new to OpenWRT.
I just aquired a R7800 and now want to use this after my modem (AVM fritzbox brand modem-router configured to allow PPPoE from other devices for VDSL).
my ISP says that native ipv6 support is required, and has some information regarding openwrt specifically:
How can I enable IPv6 on a router with OpenWRT?
The following steps describe only the configuration of IPv6 access, but not the setup and configuration of a packet filter (iptables)!
To set up IPv6 on a router with OpenWRT operating system (version 'Attitude Adjustment'), some packages have to be (re)installed first as follows:
opkg update
opkg install kmod-ipv6
opkg install wide-dhcpv6-client
opkg install radvd
The package 'kmod-ipv6' activates IPv6 support in general, 'wide-dhcpv6-client' is needed for DHCPv6 prefix delegation, 'radvd' is used to distribute the IPv6 prefix in the LAN.
Now you can enable IPv6 for the PPPoE connection. To do this, please add the following lines to the configuration of the interface used for PPPoE in '/etc/config/network'.
option ipv6 1
option accept_ra 1
The next PPPoE connection should now already have a /64 prefix, so the PPPoE interface should have a corresponding address. In the next step, please change the configuration in '/etc/config/dhcp6c' to get a /48 for the internal networks using prefix delegation.
To do this, please modify the following lines:
config 'dhcp6c' 'basic' option 'enabled' '1'
config 'interface' 'loopback' option 'enabled' '1' option 'sla_id' '0' option 'sla_len' '16
config 'interface' 'lan' option 'enabled' '1' option 'sla_id' '1' option 'sla_len' '16'
Important are the options for 'sla_len'. They determine which part of the /48 prefix should be used for an internal network. In the last step radvd is configured to distribute the appropriate prefix on the LAN interface via router advertisement.
config interface
option interface 'lan
option ignore 0
config prefix
option interface 'lan
option ignore 0
now since these are different packages, but this build comes with ipv6 packages, I am not sure if all prerequisites are met so that I can use your build on my connection: No matter how I configure, it always comes down to the following error:
Timeout waiting for PADO packets
Unable to complete PPPoE Discovery
From what I understand this could be related to ipv6 configuration. But maybe I have an issue elsewhere?
No. Wrong place.
This thread is about my build for R7800.
Ps. The advice you quoted is hopelessly outdated, as it starts from the year 2012 perspective (Attitude Adjustment). radvd has been deprecated years ago.
All the prerequisites for ipv6 are met with hynmanâs build. Feel free to load it and try it out.
Hi,
I have installed this build on my r7800 and I am having wifi performance issues. Mostly, speeds are relatively slow (although I haven't done a proper test) and connections are unstable (dropping out entirely sometimes, but usually the device stays connected and simply can't communicate with any others on the network).
I have tried tweaking usual wireless options (band, transmit power) without much improvement. This seems to be more of a problem with the linux and android based devices on the network than with the windows ones, although I can't confirm that this is the case. The ISP-provided router did not have these issues so I am assuming interference etc are not the problem here.
I would appreciate any help!
I just build 19.07 branch patched with patches from r11250 release and booted the initramfs image, still having stock fw in the flash.
I see following errors on console:
root@OpenWrt:/# dmesg | grep -i 'mtd\|ubi'
[ 1.265851] 8 fixed-partitions partitions found on MTD device qcom_nand.0
[ 1.273229] Creating 8 MTD partitions on "qcom_nand.0":
[ 1.344889] 0x000001880000-0x000007900000 : "ubi"
[ 2.857613] UBI error: no valid UBI magic found inside mtd6
[ 38.731797] print_req_error: I/O error, dev mtdblock0, sector 0
[ 38.732246] print_req_error: I/O error, dev mtdblock0, sector 8
[ 38.737011] print_req_error: I/O error, dev mtdblock0, sector 16
[ 38.742832] print_req_error: I/O error, dev mtdblock0, sector 24
[ 38.749983] print_req_error: I/O error, dev mtdblock0, sector 0
[ 38.754666] Buffer I/O error on dev mtdblock0, logical block 0, async page read
[ 38.765648] print_req_error: I/O error, dev mtdblock0, sector 0
[ 38.767598] Buffer I/O error on dev mtdblock0, logical block 0, async page read
[ 38.774507] print_req_error: I/O error, dev mtdblock1, sector 0
[ 38.781201] print_req_error: I/O error, dev mtdblock1, sector 8
[ 38.787160] print_req_error: I/O error, dev mtdblock1, sector 16
[ 38.792991] print_req_error: I/O error, dev mtdblock1, sector 24
[ 38.799385] Buffer I/O error on dev mtdblock1, logical block 0, async page read
[ 38.807681] Buffer I/O error on dev mtdblock1, logical block 0, async page read
Is this normal/expected?
Or should I assume that the flash contains bad blocks?
The router is brand new, still having the original factory firmware, not flashed with anything yet.
I only disassembled it to attach a serial cable for console access (both covers removed, so I hope the cooler thermo stickers got attached back properly with re-assembly).
Youâd do best with opening a thread in the âinstalling and using openwrtâ forum to chase down configuration, router, and client issues.
i can't remember exactly (do a search) but some of these messages (or ones like them) are expected.
dd wrt for r7800 is very stable, any builld by BS since a year and more....
this is not linked with hnyman's build.
probably you are meeting CT drivers. i still can't use them proficiently, even if they are way faster than non-ct one. Try a non-ct build
Hi Hnynam. I have R7800 with Micron MT29F1G08ABBEAH4 same to you. But I had boot loop with all firmware openwrt or stock. I tried your firmware R7800-owrt1907-r11250-ebe8cc2b2a-20201205-1419-factory.img. And log
'Untitled Post' | TextUploader.com
Could you help me. I think my router has bad block NAND chip. Thanks
Not much help from me, sorry.
Your log looks rather normal until the reboot.
The reboot happens in the middle of wifi firmware load/init. The log seemed to come from the mainline ath10k driver, not the default ath10k-ct wifi driver. (so the log was not from the 19.07 build you mentioned, from apparently from my mainline ath10k master build)
Could be that the wifi chips are somehow faulty in your unit, as you seem to have difficulties with many different firmwares.
1 Like
Thanks. I used tftp R7800 initramf -> bootm and It loaded openwrt luci --> Update: r7800 squashfs upgrade. And it reboot and boot loop again. Sorry my bad English
tftp should look something like this on a linux system with hynman's latest 1907 build (not trying to insult your intelligence if this is what you are already doing 
)
tftp 192.168.1.1
binary
put R7800-owrt1907-r11266-cb58c7fe73-20201217-1656-factory.img
If tftp is not working and multiple firmware types are not loading you may have a more serious router issue.
Do the recent builds use the newer 19.07.5? Been eyeing your builds for awhile after having some issues with Kong builds, thanks for all your hard work 
My 19.07 build is slightly newer than 19.07.5, as I build it from the head of the 19.07 branch. So, it has everything of 19.07.5 plus the possible fixes/changes after it.
Gotcha, last question for you, what are the differences between the master and 19.07 releases?
Basic OpenWrt stuff... Read a bit wiki about OpenWrt versions.
Master is the bleeding edge development branch, while 19.07 is the stable release branch. So, master has new stuff, while 19.07 is mainly July 2019 code plus some fixes.
Both work ok for R7800.