Rpi4 < $(community_build)

anon50098793 · July 5, 2021, 4:46am

if you are not using vpn-pbr 3.2(.61-30) is the recommended build...

i'm finding it a bit snappier than 3.1 ymmv
(better ipv6 handling)

3.2.61-30 known issues / unconfirmed / quirks

nlbwmon menu moved to services > bandwidth monitor
custom ntp servers overwritten (fixed in next version)
websockets libs may create issues for mosquitto users of mosquitto is not in ENABLEDSERVICES due to firstboot
new 'tty' web-terminal feature may fail due to dns--router-glob (ongoing-fixes-refinement-in-next-versions)
[unconfirmed] missing flash firmware button in luci [likely <61-20 only]
[unconfirmed] luci_statistics may break due to collectd-mod-disk custom config setup duplication
[untested] vpn-pbr may not handle newer config-network-device format

sammutd88 · July 5, 2021, 4:48am

Awesome thanks, will give it a crack

neil1 · July 5, 2021, 3:54pm

yes, it is

stable[minor-update] online:3.2.61-30(3.2.61-20)

anon50098793 · July 6, 2021, 8:19am

well... may help to clobber the related files on 61-20 (can't hurt);

possible-patch

wget https://github.com/wulfy23/rpi4/raw/master/utilities/sysuppatch.tar.gz -O /sysuppatch.tar.gz
(cd /; tar -xvzf sysuppatch.tar.gz)

dont really use the luci upgrade function (always command line or one-click) but technically it should work (generally speaking)... just rarely test it...

neil1 · July 6, 2021, 4:26pm

I upgraded to

stable uptodate: 3.2.61-30

and it is back

anon50098793 · July 6, 2021, 4:38pm

woohoo!!!
(seriously though thanks alot for testing saved everyone else issues)

moodyblue · July 6, 2021, 10:43pm

I was using 3.2.61-20. Then, inadvertently, clicked on update (in Luci) and my system was updated to 3.2.61-30. Some points here:

A confirmation before the update would have been welcome
I had Adblock and Mosquitto enabled. After the update I had to enable them again. Could this be preserved between updates ?

The build is running ok.

moodyblue · July 7, 2021, 12:35am

@anon50098793 what do you think of including NUT in your build ?

anon50098793 · July 7, 2021, 2:14am

are they in ENABLEDSERVICES ?

agree...

did you add it to /etc/packagesinstall.txt (one package per line)?

don't have any experience with it... board specific config helpers or UI tweaks sound nice... must admit have toyed with the idea of UPSing the pi...
(one other user posted some li-on rig/expressed interest... anyone else running nut?)

moodyblue · July 7, 2021, 9:46am

Adblock and Mosquitto were in enabled services.

I have an APC UPS protecting some devices (including one NAS and the RPi4 running OpenWrt). I would love to use OpenWrt to manage power on sequences (using WOL) after a power fault. I've already modified /etc/rc.local to do that but I also want to cover situations where the power fault was short, the NAS had shutdown but not OpenWrt, so the NAS needs to be restarted.

Of course the NAS could be parametrized to restart automatically when power is resumed, but I want to avoid situations when there are intermitent power failures until the situation stabilizes. The NAS takes a long time to shutdown so I want to wake it up only when battery level is adequate.

I had a long power fault yesterday and OpenWrt seems to be ok after it, probably it doesn't need to perform orderly shutdowns in my case.

anon50098793 · July 7, 2021, 9:55am

cat /boot/plog/plogread-* | grep 15-services | tail -n12

you'd have to provide most of the sample config / setup as i'm unfamiliar with the tools... but sounds like it could be a nice addition... the wol thing can be compartmentalized... (scaled to non nut users via whatever api is simplest so that's easily doable)

add them to your /etc/packagesinstall.txt and let us know when we can test something you have...

moodyblue · July 7, 2021, 9:58am

root@rpi-aveiro-router /54# cat /boot/plog/plogread-* | grep 15-services | tail
-n12
Tue Jul 6 11:06:28 2021 user.warn kernel: [ 19.715078] 15-services> Stopping and disabling simple-adblock [notenable                                 d]
Tue Jul 6 11:06:28 2021 user.warn kernel: [ 19.762710] 15-services> Stopping and disabling mosquitto [notenabled]
Tue Jul 6 11:06:28 2021 user.warn kernel: [ 19.810181] 15-services> Stopping and disabling snmpd [notenabled]
Tue Jul 6 11:06:28 2021 user.warn kernel: [ 19.855775] 15-services> Stopping and disabling atd
Tue Jul 6 11:06:28 2021 user.warn kernel: [ 19.940770] 15-services> Stopping and disabling quagga [notenabled]
Tue Jul 6 11:06:28 2021 user.warn kernel: [ 19.986647] 15-services> Stopping and disabling socat [notenabled]
Tue Jul 6 11:06:28 2021 user.warn kernel: [ 20.011501] 15-services> > enabling default services .............
Tue Jul 6 11:06:28 2021 user.warn kernel: [ 20.035408] 15-services> Starting and enabling collectd
Tue Jul 6 11:06:28 2021 user.warn kernel: [ 20.086876] 15-services> Starting and enabling luci_statistics
Tue Jul 6 11:06:28 2021 user.warn kernel: [ 20.132155] 15-services> Starting and enabling uhttpd
Tue Jul 6 11:06:28 2021 user.warn kernel: [ 20.178113] 15-services> > ENABLEDSERVICES:[/root/wrt.ini empty]
Tue Jul 6 11:06:28 2021 user.warn kernel: [ 20.202448] 15-services> > DISABLEDSERVICES:[/root/wrt.ini empty]

anon50098793 · July 7, 2021, 10:40am

grep ENABLEDSERVICES /root/wrt.ini

moodyblue · July 7, 2021, 10:58am

root@rpi-aveiro-router /54# grep ENABLEDSERVICES /root/wrt.ini
# ENABLEDSERVICES="banip adblock"   #[fboot/upgrade] enable+start
# ENABLEDSERVICES="sqm banip adblock"

anon50098793 · July 7, 2021, 11:02am

you can uncomment it in system > startup > localstartup
( you could also use the new http>[editor] )

should look like this

ENABLEDSERVICES="adblock mosquitto"

KnowNothing · July 7, 2021, 4:23pm

I was never able to get NUT to find the UPS in USB chain. Please post when you figure that out.

malikshi · July 8, 2021, 10:54pm

Everytime update the version need to setting sqm and install speedtest again? 3.2.61-20 to version 3.2.61-30

sammutd88 · July 9, 2021, 12:30am

Quick question, just noticed something from tinkering around and wanted to confirm.

If I run cat /proc/interrupts the result is 100% of interrupts on eth0 going to CPU0 (ie, 1 core).
Installing IRQ balance and rebooting doesn't change this.
Editing /etc/config/irqbalance and changing option enabled "0" to "1" and rebooting makes a small difference, but CPU0 still handles over 98% of interrupts on eth0, albeit a couple go to cores 3 and 4. Is this just standard? I would've assumed irqbalance would do a better job sharing the love, but don't know enough about it.

Note: my wan speed is only 250/25 so not pushing anything at all, just rather things be as efficient as possible! Packet steering is enabled btw.

malikshi · July 9, 2021, 1:56am

Spam log

Fri Jul  9 08:50:26 2021 kern.warn kernel: [31798.573923] overlayfs: failed to look up (atftpd) for ino (-5)
Fri Jul  9 08:50:26 2021 kern.warn kernel: [31798.579963] overlayfs: invalid origin (config/mwan3, ftype=8000, origin ftype=a000).
Fri Jul  9 08:50:26 2021 kern.warn kernel: [31798.587731] overlayfs: failed to look up (mwan3) for ino (-5)
Fri Jul  9 08:50:26 2021 kern.warn kernel: [31798.593551] overlayfs: failed to get inode (-116)
Fri Jul  9 08:50:26 2021 kern.warn kernel: [31798.598259] overlayfs: failed to look up (snmpd) for ino (-116)
Fri Jul  9 08:50:26 2021 kern.warn kernel: [31798.604533] overlayfs: failed to get inode (-116)
Fri Jul  9 08:50:26 2021 kern.warn kernel: [31798.609279] overlayfs: failed to get inode (-116)
Fri Jul  9 08:50:26 2021 kern.warn kernel: [31798.614218] overlayfs: invalid origin (config/atftpd, ftype=8000, origin ftype=4000).
Fri Jul  9 08:50:26 2021 kern.warn kernel: [31798.624491] overlayfs: invalid origin (config/mwan3, ftype=8000, origin ftype=a000).
Fri Jul  9 08:50:26 2021 kern.warn kernel: [31798.636108] overlayfs: failed to look up (acme) for ino (-116)
Fri Jul  9 08:50:26 2021 kern.warn kernel: [31798.642022] overlayfs: invalid origin (config/atftpd, ftype=8000, origin ftype=4000).
Fri Jul  9 08:50:26 2021 kern.warn kernel: [31798.649867] overlayfs: failed to look up (atftpd) for ino (-5)
Fri Jul  9 08:50:26 2021 kern.warn kernel: [31798.655788] overlayfs: invalid origin (config/mwan3, ftype=8000, origin ftype=a000).
Fri Jul  9 08:52:02 2021 kern.warn kernel: [31894.530657] ovl_check_origin_fh: 20 callbacks suppressed
Fri Jul  9 08:52:02 2021 kern.warn kernel: [31894.530663] overlayfs: invalid origin (config/mwan3, ftype=8000, origin ftype=a000).
Fri Jul  9 08:52:02 2021 kern.warn kernel: [31894.671513] overlayfs: invalid origin (config/mwan3, ftype=8000, origin ftype=a000).
Fri Jul  9 08:52:02 2021 kern.warn kernel: [31894.816285] ovl_get_inode: 32 callbacks suppressed
Fri Jul  9 08:52:02 2021 kern.warn kernel: [31894.816288] overlayfs: failed to get inode (-116)
Fri Jul  9 08:52:02 2021 kern.warn kernel: [31894.825797] ovl_cache_update_ino: 18 callbacks suppressed
Fri Jul  9 08:52:02 2021 kern.warn kernel: [31894.825800] overlayfs: failed to look up (acme) for ino (-116)
Fri Jul  9 08:52:02 2021 kern.warn kernel: [31894.837163] overlayfs: invalid origin (config/atftpd, ftype=8000, origin ftype=4000).
Fri Jul  9 08:52:02 2021 kern.warn kernel: [31894.845013] overlayfs: failed to look up (atftpd) for ino (-5)
Fri Jul  9 08:52:02 2021 kern.warn kernel: [31894.850916] overlayfs: invalid origin (config/mwan3, ftype=8000, origin ftype=a000).
Fri Jul  9 08:52:02 2021 kern.warn kernel: [31894.858669] overlayfs: failed to look up (mwan3) for ino (-5)
Fri Jul  9 08:52:02 2021 kern.warn kernel: [31894.864461] overlayfs: failed to get inode (-116)
Fri Jul  9 08:52:02 2021 kern.warn kernel: [31894.869157] overlayfs: failed to look up (snmpd) for ino (-116)
Fri Jul  9 08:52:02 2021 kern.warn kernel: [31894.875280] overlayfs: failed to get inode (-116)
Fri Jul  9 08:52:02 2021 kern.warn kernel: [31894.879985] overlayfs: failed to get inode (-116)
Fri Jul  9 08:52:02 2021 kern.warn kernel: [31894.884832] overlayfs: invalid origin (config/atftpd, ftype=8000, origin ftype=4000).
Fri Jul  9 08:52:02 2021 kern.warn kernel: [31894.895105] overlayfs: invalid origin (config/mwan3, ftype=8000, origin ftype=a000).
Fri Jul  9 08:52:02 2021 kern.warn kernel: [31894.904016] overlayfs: failed to get inode (-116)

anon50098793 · July 9, 2021, 5:19am

changed in the next build... thanks