Build for Netgear R7800

r9627: dnsmasq keeps starting even though I have the service disabled. Any ideas what could be causing it? What is strange is that I'm stopping it and disabling in rc.local but the process is still there after a reboot. There is no dnsmasq in /etc/rc.d, so something else must be causing it to start.

Luci is also very slow, it just sits there spinning. If I restart uhttpd it's fine for a while but then back to being painfully slow.

Anyone else seeing this problem? Seems to happen in Chrome, Firefox looks OK. I tried a clean Chrome profile and same problem. Not sure if it's related to this change:

Another problem:
I installed bind-dig opkg, but can't run dig, any ideas?

# dig
Error relocating /usr/lib/libdns.so.1207: ENGINE_get_id: symbol not found
Error relocating /usr/lib/libdns.so.1207: ENGINE_load_private_key: symbol not found
Error relocating /usr/lib/libdns.so.1207: ENGINE_load_builtin_engines: symbol not found
Error relocating /usr/lib/libdns.so.1207: ENGINE_set_default: symbol not found
Error relocating /usr/lib/libdns.so.1207: ENGINE_free: symbol not found
Error relocating /usr/lib/libdns.so.1207: ENGINE_load_public_key: symbol not found
Error relocating /usr/lib/libdns.so.1207: ENGINE_by_id: symbol not found

Could be openssl 1.1.1 misbehaving with the engine config option. Apparently some packages have been compiled with engine support dependency while openssl itself is not.

Thank you. Hopefully it gets fixed in future pkg builds.
Any ideas for the slow Luci UI in Chrome? Not only slow, many times request never finish, they just time out, rendering the UI unusable in Chrome.

Time for a solution update on the issues I've been facing:

  • Trying to disbable dnsmasq service but it was still running: turns out that calling /etc/init.d/dnsmasq stop and disable from /etc/rc.local at every boot causes this, dnsmasq starts running even though it was previously disabled and stopped. Not sure whether it's a bug in the init scripts. I just have to remember to do it once after a firmware upgrade as I don't know how else I can automate it short of building my own firmware.
  • Slow https UI/requests time out in Chrome only, but OK in Firefox, or plain http OK too: I was tired of accepting the self-signed TLS cert every time and didn't want to add it as an exception, so I decided to have my local CA and generate my own cert signed by it. I used this useful tool: https://github.com/FiloSottile/mkcert
    Now no more warnings from browsers and to my surprise it also fixed the Chrome issues, though I didn't think it would. There must have been something about that self-signed cert generated by OpenWRT that Chrome didn't like.

hello,
i can't get nginx to start with this build.
did i miss something?
the service is not starting but not giving any error, so i tried manually and i got this:

root@RUTTO:/etc/nginx# /usr/sbin/nginx -c /etc/nginx/nginx.conf
Error relocating /usr/sbin/nginx: ENGINE_load_private_key: symbol not found
Error relocating /usr/sbin/nginx: ENGINE_set_default: symbol not found
Error relocating /usr/sbin/nginx: ENGINE_free: symbol not found
Error relocating /usr/sbin/nginx: ENGINE_by_id: symbol not found

thanks

edit to add: well, nginx with ssl, is it the problem?

openssl needs to be compiled with engine support

@ansuel
Do you see that as a hard new requirement for nginx, or does that only happen because some openssl in buildbot is now complied with engine support and nginx compliation detects it.

(There are some packages that currently erroneously force engine support to be enabled in openssl in buildbot, although engine support is not on by default. That likely leads also nginx to be compiled with engine support in buildbot, although that does not match the intended openssl defaults). See my analysis in
https://github.com/openwrt/packages/pull/8341#issuecomment-478322454

i have r7800 and as it doesn't have any hardware crypto i also disabled engine support for openssl

Got the same problem with nginx crashing on boot. By enabling engine support nginx starts to work again.

will check if nginx get compiled with engine support.

i suppose this is something i can only fix building the image by myself..
am i wrong?

checking the compilation option and can't find any way to enable/disable engine support for nginx so... openssl problem

yes for now

that's bad
i don't want to expose my local surveillance cams with no ssl
do you think this is something that is gonna be fixed soon?
thanks

yes
as i think this is broken in master build

Other packages are broken the same way, such as bind-dig

well i'll try to wait some days and see what happens :slight_smile:
it seems this build is working much better than the previous one i had (well, it was from late 2018..) with my iptv, so i don't want to revert back :slight_smile:
Thanks

Hi Guys,

Is there a known stable build, I have tried various with my R7800 but it’s only lasted a week maximum before needing to be manually powered off to come back on. I am currently on OpenWrt 18.06-SNAPSHOT r7720-0a637c7f87.

However I am seeing a lot of;

kern.warn kernel: [42873.176056] ath10k_pci 0001:01:00.0: received unexpected tx_fetch_ind event: in push mode

My Samsung S8 also keeps saying it may not have the internet when everything else does.

i see a new r9765 build, any news on engine support problem?
thanks :slight_smile:

No, I have not changed my own build from the normal openssl defaults. (but buildbot is still building openssl with the settings forced by libp11 since packages feed PR #8341 , so the other packages in the buildbot snapshot repo may be built to assume that engine support.)

https://svn.dd-wrt.com/changeset/39347 there is hw offloading for ath10k..