OpenWrt 19.07.3 service release

Upgraded my C7 V5 and my NBG6617.without a problem. Thank you.
btw when I can't log into LuCI after IP address changes I visit the logout page first.

http://192.168.1.1/cgi-bin/luci/admin/logout

No such problem with my C7 V5

Upgraded both Archer C7 V2 and Home Hub 5A form 19.07.2 to 19.07.3. All went smoothly. Looking good.

Thanks guys!

Flashed my Archer C7 V2 and it's been 24 hours with no issues on heavy usage.

I reported this on GiHub and has been fixed by @jow

See here for the details > https://github.com/openwrt/luci/issues/4093

1 Like

There are a few bugs with the new firmware but I am reporting them. The quicker they get noticed the quicker than can get fixed.

LuCI SSL has definitely improved. Firefox mobile had problems working with OpenSSL and the LuCI web-GUI over HTTPS but it's now very smooth and no more page timeouts for me.

Hi

19.07.3 seems to be non-starter on my x86 box (the snapshot builds were the same too last time I tried them). Kernel log on console stops at "random: crng init done". The intel i211 nics don't get loaded so I'm limited to console to interact with it.

console

On 19.07.2 it's loading up the ethernet drivers at that point:

[    5.607877] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
[    5.609598] e1000: Copyright (c) 1999-2006 Intel Corporation.
[    5.611906] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.4.0-k
[    5.611929] urngd: v1.0.2 started.
[    5.613536] igb: Copyright (c) 2007-2014 Intel Corporation.
[    5.624497] random: crng init done
[    5.848583] pps pps0: new PPS source ptp0
[    5.850605] igb 0000:03:00.0: added PHC on eth0
[    5.851939] igb 0000:03:00.0: Intel(R) Gigabit Ethernet Network Connection

At first I though the default build might have changed and it might be missing a kmod (although I checked e1000/e1000e & igb are there). I did a custom build with all the packages inc kmods from my 19.07.2 setup and flashed to a test partition but the problem's still there. No sign of life for the nics. So I'm not sure where to go next with it. Am I missing something (PEBKAC?)

Make sense to anyone? Any ideas would very appreciated.

Updated 5 Meraki MR24 AP's via GUI, keeping settings (and re-disabling dnsmasq, firewall, and odhcpd). No problems, and all running smoothly after two days. Many thanks!

Great work guys,keep up the good work!!
Any support for tp-link archer c3200 anytime soon?

If you own a C3200 and you would like to help to get OpenWrt on this device, please open a new topic.

2 Likes

Success report for WNDR3800 (really the WNDRMACV2) coming from 19.07.2 ath79.

Thank you OpenWRT Team for providing this build
My routers are working without any defects
Appreciate that :pray: :kissing_heart: :wine_glass:

Hello i'm up and running smoothly on 19.07.3 since 10 days.
Btw i've noticed strange messages on syslog, I dont know what they mean, like:
Tue Jun 2 11:12:23 2020 daemon.err dnsmasq[2226]: failed to send packet: Host is unreachable
Tue Jun 2 11:12:24 2020 daemon.err dnsmasq[2226]: failed to send packet: Host is unreachable

Same message repeated like 30 times... any help would be appreciated
Thanks

1 Like

This is running phenomenal on my WRT32X. Only thing I changed was installing Linux kernel 5.4.42 off of the davidc502 mvebu builds. Bandwidth tests max out my cable modem with A+ quality and A+ bufferbloat ratings from dslreports.com/speedtest. Network sharing with samba4 is running 80-100MB/s off my USB 3.0 hard drive. 5GHz wifi is stable. SQM and Adblock work great, Luci is fast and silky smooth, everything seems in a good place right now. Thanks for the hard work everyone!

I compiled OpenWrt 19.07.3 for some of my devices. Everything is working well so far so congratulations to the team. I only have some concerns regarding the "service release" definition.

From the OpenWrt core perspective, extra care has been taken to only include tested commits that solves functional or security issues and it seems like very good choice.

However, this is not true for LuCI. The github branch of 19.07 is not really focused on bugfixes. At the end, this introduces almost the same amount of regression than the amount of bug fixed. In 19.07.3, LuCI started to really integrate ACL which caused several issue (the one that require the login/logout after app install, some empty ubus calls, ...). Also, I was surprised to see that the display changed from Free to Used memory and that the "Refresh" status has been changed too.

I don't know what is the general opinion on that, but I would expect a service release to focus on polishing the build security and stability, without introducing any functional change. Maybe this should be discussed by the project team ?

Note that this is a personal opinion and comment, but, once again, the team did a very good job :slight_smile:.

The basic problem is that we are once again in a "too slow releases" cycle.

20.01 was supposed to come in January, the n20.07 in a month etc. if we would follow the roughly 6 month release cycle.

When the next "major" release gets slowed down too much, the interest to backport also new stuff to 19.07 grows. And that brings then also new bugs, sadly.

Hopefully 20.0x could be prepared in the next few months, so that 19.07 could be properly retired.

1 Like

Hey. Installed 19.07.03 Sunday, on our WRT 3200.
Everything went well with the install, and the system is working great.
Added DNSCrypt, Adblock, Sensors, and Advanced reboot, all are favorites here.
Thanks to the team, and I'm looking forward to the next build!
Knacht
KD8DWO

I was wondering if this can be due to firefox w/uBlockOrigin plugin?
Can somebody with same plugin confirm what system log shows?
Thanks

If I had to make a guess, I would bet you have configured an upstream DNS that is unreachable. However, I think you would get.more help if you open a separate thread.

Hi,

thanks for the great release. It's working perfectly well on my TPlink archer c7's. I've only got one wish: Please include non-ct ath10k drivers by default instead of ct. They have more range (coverage), stability and my best throughput was around 500 mbit/s between two archers via 802.11s. And the 802.11s can be encrypted with non-ct, too.

Many thanks and keep up the good work!

Catfriend1

1 Like