Build for Netgear R7800

Fully agree with you (and I started this OT this time :wink: , no need to be sorry )

In addition to the user's ISPs own network bandwidth, is the opposite side's server actually able to serve the user with gigabit content/download/whatever ? Most content / cloud service providers have no possibility to actually saturate gigabyte uploads simultaneously for a substantial part of their users.

That is part of the reasoning why I have not invested time to do the ultimate tweaks to get the last 200 Mbit of throughput from R7800.

Sure, short-period peak performance with artificial speed tests is nice to achieve, but has little to do with real-life networking (from home-user perspective).

2 Likes

Freeing up CPU cycles means more work can be done. Useful for folks using VPN, especially in a constrained environment like a consumer router.

2 Likes

Having errors with the stubby package crashing on the latest build master-r14820-5cdc65f6d1-20201031. Is it just me? If so, I'll try factory reset.

Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error loading shared library libyaml-0.so.2: No such file or directory (needed by /usr/sbin/stubby)
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error loading shared library libgetdns.so.10: No such file or directory (needed by /usr/sbin/stubby)
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_list_get_bindata: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_dict_set_dict: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_context_set_listen_addresses: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_reply: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_context_set_resolution_type: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: yaml_event_delete: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_context_create: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_context_config: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_dict_get_bindata: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_list_create: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: yaml_parser_parse: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_context_get_edns_client_subnet_private: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_dict_create: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_dict_get_names: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_list_get_length: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_get_errorstr_by_id: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_dict_get_list: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_dict_get_int: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_dict_remove_name: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_context_run: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_context_get_tls_authentication: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: yaml_parser_delete: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_list_destroy: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_convert_dns_name_to_fqdn: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_dict_set_int: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_list_get_dict: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_pretty_print_dict: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_dict_set_list: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_context_get_resolution_type: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_str2dict: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_context_destroy: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_dict_create_with_context: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: yaml_parser_set_input_string: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_context_get_tls_query_padding_blocksize: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_dict_get_dict: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_general: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_context_get_api_information: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_dict_destroy: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_context_get_dns_transport_list: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: yaml_parser_initialize: symbol not found
Sun Nov  1 15:01:07 2020 daemon.err stubby[11548]: Error relocating /usr/sbin/stubby: getdns_context_set_logfunc: symbol not found
Sun Nov  1 15:01:07 2020 daemon.info procd: Instance stubby::stubby s in a crash loop 6 crashes, 0 seconds since last crash```

There is no stubby in my build.

Either something wrong with the stubby package itself, or opkg has failed to install all needed packages.

You're right! opkg doesn't appear to install the required dependencies on the latest build. It installs the needed dependencies automatically on the old R7800-master-r14793-9f1927173a-20201028 build. Installing each dependency manually with opkg worked on the latest build. Thanks!

It should now be fixed in master-r14849-4a2b1ff7fb-20201102 thanks to the fix by

1 Like

@hnyman do you plan to add a release for broken nand ?
Or at least a debug one to help people ?
I will try to compile one to verify and see after how to hook yours scripts.

No.
What broken NAND?

@hnyman see the previous link, the home page of R7800 on OpenWrt, I can't pin the direct section so you need to browse the page.

No, I am not going to a build for that. The problem only materialised with the first installation with the "factory" image, but subsequent sysupgrades will work ok in any case.

The advice is wiki assumes that there is just one faulty block, but there is no certainty on that.

I feel that the best solution might be to use RAM based initramfs image for the initial factory install, and then sysupgrade from that running image.

Forum has discussions about that.

I have a kind of broken R7800

  • Netgear OS Kind : work well except a weird dns bug with routerlogin.net
  • DD Wrt : work but wifi is slow with AX200 clients
  • Open Wrt : reboot randomly after installation, starting from some build after the big layout partition change.

I also have broken ssl chip :disappointed:

I use both DDWRT and OpenWRT and do not have problems with my AX200 client but default settings of DDWRT are not the best

I experience a strange Wi-Fi issue with this build ( to be precise: OpenWrt SNAPSHOT r14694-e788e9bd87 / LuCI Master git-20.280.41447-12e50de )
It happens from time to time that my Wi-Fi devices disconnect. Typically I realize it only because google home says it cannot connect to the Internet.
Today, I managed to capture the dmesg output when it happened. See below.
Any idea what the cause might be? I believe that the wi-fi typically comes up again after a while, but I'm not quite certain. It does work again after doing an 'enable' in the Luci UI.

[1848421.386767] ath10k_pci 0001:01:00.0: SWBA overrun on vdev 1, skipped old beacon
[2504211.330368] device wlan0 left promiscuous mode
[2504211.330484] br-lan: port 2(wlan0) entered disabled state
[2504211.362664] ath10k_pci 0000:01:00.0: mac flush null vif, drop 0 queues 0xffff
[2504211.365099] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[2504211.368810] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[2504211.375792] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[2504211.485939] ath10k_pci 0001:01:00.0: No VIF found for vdev 1
[2504211.485965] ath10k_pci 0001:01:00.0: wmi-event-beacon-tx, could not find vdev for id: 1
[2504211.510997] ath10k_pci 0001:01:00.0: No VIF found for vdev 1
[2504211.511017] ath10k_pci 0001:01:00.0: received addba event for invalid vdev_id: 1
[2504211.516376] ath10k_pci 0001:01:00.0: No VIF found for vdev 1
[2504211.523350] ath10k_pci 0001:01:00.0: received addba event for invalid vdev_id: 1
[2504211.529828] ath10k_pci 0001:01:00.0: No VIF found for vdev 1
[2504211.536708] ath10k_pci 0001:01:00.0: received addba event for invalid vdev_id: 1
[2504211.542513] ath10k_pci 0001:01:00.0: No VIF found for vdev 1
[2504211.549999] ath10k_pci 0001:01:00.0: received addba event for invalid vdev_id: 1
[2504211.557184] ath10k_pci 0001:01:00.0: No VIF found for vdev 1
[2504211.563451] ath10k_pci 0001:01:00.0: received addba event for invalid vdev_id: 1
[2504211.721730] Virtual device wlan1-1 asks to queue packet!
[2504211.730622] Virtual device wlan1-1 asks to queue packet!
[2504211.941718] Virtual device wlan1-1 asks to queue packet!
[2504211.941809] Virtual device wlan1-1 asks to queue packet!
[2504212.161562] Virtual device wlan1-1 asks to queue packet!
[2504212.371715] Virtual device wlan1-1 asks to queue packet!
[2504212.591819] Virtual device wlan1-1 asks to queue packet!
[2504213.261631] Virtual device wlan1-1 asks to queue packet!
[2504213.501757] Virtual device wlan1-1 asks to queue packet!
[2504214.651055] ath10k_pci 0001:01:00.0: WARNING: failed to wait for beacon tx callback for vdev 1: 0
[2504214.651372] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
[2504214.658932] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
[2504214.666865] br-iot: port 2(wlan1-1) entered disabled state
[2504214.673167] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
[2504214.687412] device wlan1-1 left promiscuous mode
[2504214.687444] br-iot: port 2(wlan1-1) entered disabled state
[2504214.960400] device wlan1 left promiscuous mode
[2504214.960509] br-lan: port 3(wlan1) entered disabled state
[2504214.991145] ath10k_pci 0001:01:00.0: mac flush null vif, drop 0 queues 0xffff
[2504214.992398] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 0
[2504214.997256] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 0
[2504215.004279] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 0
[2504226.072217] ath10k_pci 0000:01:00.0: unsupported HTC service id: 1536
[2504226.072252] ath10k_pci 0000:01:00.0: 10.4 wmi init: vdevs: 16  peers: 48  tid: 96
[2504226.077734] ath10k_pci 0000:01:00.0: msdu-desc: 2500  skid: 32
[2504226.160855] ath10k_pci 0000:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186  msdu-desc: 2500  sw-crypt: 0 ct-sta: 0'
[2504226.161691] ath10k_pci 0000:01:00.0: wmi print 'free: 84920 iram: 13316 sram: 11224'
[2504226.552648] ath10k_pci 0000:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
[2504226.566903] br-lan: port 2(wlan0) entered blocking state
[2504226.566965] br-lan: port 2(wlan0) entered disabled state
[2504226.572060] device wlan0 entered promiscuous mode
[2504232.492598] ath10k_pci 0001:01:00.0: unsupported HTC service id: 1536
[2504232.493404] ath10k_pci 0001:01:00.0: 10.4 wmi init: vdevs: 16  peers: 48  tid: 96
[2504232.498011] ath10k_pci 0001:01:00.0: msdu-desc: 2500  skid: 32
[2504232.583397] ath10k_pci 0001:01:00.0: wmi print 'P 48/48 V 16 K 144 PH 176 T 186  msdu-desc: 2500  sw-crypt: 0 ct-sta: 0'
[2504232.584268] ath10k_pci 0001:01:00.0: wmi print 'free: 84920 iram: 13316 sram: 11224'
[2504233.331620] ath10k_pci 0001:01:00.0: Firmware lacks feature flag indicating a retry limit of > 2 is OK, requested limit: 4
[2504233.338378] br-lan: port 3(wlan1) entered blocking state
[2504233.342083] br-lan: port 3(wlan1) entered disabled state
[2504233.347806] device wlan1 entered promiscuous mode
[2504233.353133] br-lan: port 3(wlan1) entered blocking state
[2504233.357468] br-lan: port 3(wlan1) entered forwarding state
[2504233.370751] br-lan: port 3(wlan1) entered disabled state
[2504240.916746] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[2504240.917052] br-lan: port 2(wlan0) entered blocking state
[2504240.922289] br-lan: port 2(wlan0) entered forwarding state
[2504243.969068] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[2504243.969553] br-lan: port 3(wlan1) entered blocking state
[2504243.974663] br-lan: port 3(wlan1) entered forwarding state
[2504243.987601] br-iot: port 2(wlan1-1) entered blocking state
[2504243.987626] br-iot: port 2(wlan1-1) entered disabled state
[2504243.992614] device wlan1-1 entered promiscuous mode
[2504244.006482] br-iot: port 2(wlan1-1) entered blocking state
[2504244.006508] br-iot: port 2(wlan1-1) entered forwarding state
[2504244.037020] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1-1: link becomes ready
[2627642.621161] device wlan0 left promiscuous mode
[2627642.621263] br-lan: port 2(wlan0) entered disabled state
[2627642.654476] ath10k_pci 0000:01:00.0: mac flush null vif, drop 0 queues 0xffff
[2627642.656409] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[2627642.660744] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[2627642.667609] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 0
[2627642.803994] ath10k_pci 0001:01:00.0: No VIF found for vdev 1
[2627642.804032] ath10k_pci 0001:01:00.0: received addba event for invalid vdev_id: 1
[2627642.809391] ath10k_pci 0001:01:00.0: No VIF found for vdev 1
[2627642.816341] ath10k_pci 0001:01:00.0: received addba event for invalid vdev_id: 1
[2627642.822192] ath10k_pci 0001:01:00.0: No VIF found for vdev 1
[2627642.829701] ath10k_pci 0001:01:00.0: no vif for vdev_id 1 found
[2627642.836762] ath10k_pci 0001:01:00.0: No VIF found for vdev 1
[2627642.841671] ath10k_pci 0001:01:00.0: received addba event for invalid vdev_id: 1
[2627642.853344] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
[2627642.854940] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
[2627642.861814] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
[2627642.869279] br-iot: port 2(wlan1-1) entered disabled state
[2627642.886664] device wlan1-1 left promiscuous mode
[2627642.886693] br-iot: port 2(wlan1-1) entered disabled state
[2627643.121206] device wlan1 left promiscuous mode
[2627643.121303] br-lan: port 3(wlan1) entered disabled state
[2627643.161929] ath10k_pci 0001:01:00.0: mac flush null vif, drop 0 queues 0xffff
[2627643.163155] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 0
[2627643.168047] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 0
[2627643.175225] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 0
root@dg1sek-router:~# 

Just downloaded and installed "master-r14947-0f7a3288e1-20201115 (ath10k-ct) " today.

After installation (clean install with rest of settings) I logged into the the Luci interface, set up my router passwords and set up wireless names, channels, passwords, etc. After this I then went to System, then Software, then hit the Update Lists button. Tried to find the "Stubby" package but it appears to be missing.

I had DNS over TLS working fine via the instructions found here: [Tutorial] [No CLI] Configuring DNS over TLS with LuCI using Stubby and Dnsmasq. Since I can not find the "Stubby" package I am unable to install DNS over TLS as I had before.

Am I missing something.

If you look at the buildbot failure logs, you can notice that lots of packages currently fail in buildbot, including stubby.

You need to wait until sources are fixed so that buildbot is happy again.

1 Like

Thank You for your quick reply.

I reverted to the "stable openwrt-19.07" and everything is working correctly.

It's interesting that the "master-r14935-95b0751d0f-20201113" and prior had the "Stubby" packages. I guess they introduced some bugs in the latest master package. Guess I'll stay with the stable...

Also, I want to thank you for creating these firmware packages for the R7800. Your efforts are greatly appreciated!

Hi,
do you have any repository of older builds of yours? I just tried master-r14965-3f1109bf2a-20201117 and seems there still some issues with the repos as unbound is completely gone from them and I wanted to revert to the older version I was sure I kept a backup of, but turns out I didn't.

edit: Uh oh, I found a month old build of yours, but unbound is still not in the repos guess I'll forgo using it for now until it gets sorted. Found ERROR: package/feeds/packages/unbound failed to build. in the latest buildbot logs so I'll keep checking until it's successful, looks like lot of packages failed to build. I should also learn to read as it is literally discussed in the posts above...

Is using the just-released 5.9ghz unlicensed spectrum going to require a firmware update or is there a package update that I'm missing?

1 Like

That will require new hardware, router- and client side.

Are you sure? This is spectrum that is already legal in parts of the world.

image

1 Like