Rpi4 < $(community_build)

Ah darn, I should have seen that one, thank you for helping out.

EDIT: Alright I have now changed operating frequency to Legacy with 2.4ghz but as it seems (if I haven't forgotten something) the change is not reflected in config-wifi-device:

cat /etc config/wireless
config wifi-device 'radio0'
        option type 'mac80211'
        option path 'platform/soc/fe300000.mmcnr/mmc_host/mmc1/mmc1:0001/mmc1:0001:1'
        option band '5g'
        option cell_density '0'
        option country 'DE'
        option hwmode '11g'
        option channel 'auto'
        option legacy_rates '1'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option encryption 'psk2+ccmp'
        option key 'very_secret_pw'
        option ssid 'SSID'
        option wmm '0'
        option wpa_disable_eapol_key_retries '1'

option band is still set to 5g. I guess I just change it to 24g manually and reboot?

EDIT2: I have changed the band to '24g' manually and it now has changed the band properly to 2.4ghz.

1 Like

is this build related?

1 Like

lol... 99.9% chance yes...

thanks for the info... will check it out...

(is that 3.2.61-20 by any chance?)

1 Like

G'Day all, newbie here. Got a rpi4b on the way and want to give Openwrt a crack to use as my router, and relegate my ERX-SFP to poe switch status. Got a UE300 ethernet dongle to accompany. Just wanted to confirm if I should use 3.1 vs 3.2 branch? Is there a stability difference? Have a fairly basic config, just a separate VLAN for IoT devices, a few extra firewall rules as applicable and use Wireguard for remote access/managment. Wireless won't be used, access points in house are powered via switch.

Any tips appreciated. Looking forward to giving it all a crack.

1 Like

That's not a valid band option, use one of these instead:

 2g, 5g, 60g, 6g

See for reference: https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=package/kernel/mac80211/files/lib/wifi/mac80211.sh;h=0763da8fd813e880f848bcd389d29a2387eeedde;hb=8504212f65865449dd6b9ed9daa0ba9781f8f287#l123)


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

1 Like

Awesome thanks, will give it a crack

yes, it is

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

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

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...

1 Like

I upgraded to

stable uptodate: 3.2.61-30

and it is back

1 Like

:thinking: :cold_face: :partying_face:
(seriously though thanks alot for testing saved everyone else issues)

1 Like

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:

  1. A confirmation before the update would have been welcome
  2. 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.


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



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?)

1 Like

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.

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...

root@rpi-aveiro-router /54# cat /boot/plog/plogread-* | grep 15-services | tail
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]
1 Like
grep ENABLEDSERVICES /root/wrt.ini
root@rpi-aveiro-router /54# grep ENABLEDSERVICES /root/wrt.ini
# ENABLEDSERVICES="banip adblock"   #[fboot/upgrade] enable+start
# ENABLEDSERVICES="sqm banip adblock"
1 Like

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

should look like this

ENABLEDSERVICES="adblock mosquitto"