Rpi4 < $(community_build)

poodad · August 5, 2020, 11:54am

No to NORCCUSTOM=1

Let me re-write the sdcard and start over.

anon50098793 · August 5, 2020, 12:02pm

no worries... as a bonus latest build has persistent nlbwmon + statistics ( with conntrack and irq )

poodad · August 5, 2020, 1:31pm

I'm having strange persistence problems. My RPi remembers things it should be forgetting. I pulled the sdcard and wrote your latest image to it. When I booted the RPi, it remembered the previous IP address I'd set on the ethernet interface.

Can't do an opkg update.
Collected errors:

opkg_conf_parse_file: Failed to open /etc/opkg/customfeeds.conf: Stale file handle.

I put the sdcard back in the computer, used disk manager to format the first partition (not a fast format, so presumably all blocks in the first partition were wiped). Deleted all the partitions, then wrote the image with win32diskimager.

Same results.

Do I need to somehow zero out the whole sdcard before writing images to it?

Does the RPi have some sort of built-in nonvolatile storage OpenWRT is using?

anon50098793 · August 5, 2020, 1:32pm

the last time I used factory... I ended up zero-ing the sdcard... ( linux dd zero + zcat dd )... not sure if win32diskimager zero's properly... just deleting is likely not enough...

the pi4's nv storage is a minimal bootloader only...( nothing os related ) previous pi's had no nv at all.

poodad · August 5, 2020, 2:13pm

No dd under windows (yes, I realize there are win32 ports of dd). What I did on the last spin:

Use disk manager to create partition in the empty remainder of the sdcard
Deleted FAT partition #1
Deleted partition2
Create a fat32 partition in the space previously held by the first two partitions
Do a format, but deselect the "quick" option forcing all blocks to be written
Use Win32DiskImager to write the image.

Again, thank you. You have moved me light-years ahead in my quest to build the ultimate LTE router.

poodad · August 5, 2020, 2:43pm

Fan issue solved. While poking around in luci's software packages available I discovered kmod-hwmon-rpi-poe-fan. I installed it and the fan spun right up!

neil1 · August 9, 2020, 9:57am

please add support for simple ad blocker it does support ad blocking even when you are using dns over https

github.com

openwrt/packages/blob/master/net/simple-adblock/files/README.md#how-to-use-dnsmasq-ipset

# Simple AdBlock

[![HitCount](http://hits.dwyl.com/stangri/openwrt/simple-adblock.svg)](http://hits.dwyl.com/stangri/openwrt/simple-adblock)

A simple DNSMASQ/Unbound-based AdBlocking service for OpenWrt/LEDE Project.

## Features

- Super-fast due to the nature of supported block-lists and parallel downloading/processing of the block-lists.
- Supports hosts files and domains lists for blocking.
- Everything is configurable from Web UI.
- Allows you to easily add your own domains to allow-list or block-list.
- Allows you to easily add URLs to your own blocked hosts or domains lists to allow/block-list (just put allowed domains one per line in the file you're linking).
- Supports multiple modes of AdBlocking implementations with DNSMASQ and Unbound.
- Doesn't stay in memory -- creates the list of blocked domains and then uses DNSMASQ/Unbound and firewall rules to serve NXDOMAIN or 127.0.0.1 reply or to reject access (depending on settings) for blocked domains.
- As some of the default lists are using https, reliably works with either wget/libopenssl,  uclient-fetch/libustream-mbedtls or curl.
- Very lightweight and easily hackable, the whole script is just one ```/etc/init.d/simple-adblock``` file.
- Retains the downloaded/sorted AdBlocking list on service stop and reuses it on service start (use ```dl``` command if you want to force re-download of the list).
- Has an option to store a compressed copy of the AdBlocking list in persistent memory which survives reboots.
- Blocks ads served over https (unlike PixelServ-derived solutions).

This file has been truncated. show original

anon50098793 · August 9, 2020, 10:05am

thanks for the tip... , try;

opkg update && opkg install luci-app-simple-adblock && /etc/init.d/adblock stop && /etc/init.d/adblock disable

should more people also need it ( 3+ ), will definitely consider adding within the image.

dinsdale · August 9, 2020, 6:27pm

Any chance we can get a rootfs tar (similar to this)? I am running OpenWRT inside an LXD container on the Pi, so can't really use img files.

anon50098793 · August 9, 2020, 6:39pm

done (10 characters)

storm1er · August 10, 2020, 12:16pm

Hi,

I would prefer squashfs images as path upgrade is way easier.
Using ext4 only allow a complex upgrade path:

export config
upload update
-- possible troubleshoot as config is now the default one again
import config

Using squashfs is way easier, the only troubleshooting is eventually specific package without retro-compatibility.

anon50098793 · August 10, 2020, 12:20pm

give them a try... start with the community squashfs factory... from there to begin with, ignore 'sysupgrade -p' ... regular sysupgade should be ok... be sure to let us know how it goes

krazeh · August 10, 2020, 12:29pm

Nope, you can upgrade an ext4 image in just the same way as a squashfs image.

anon50098793 · August 10, 2020, 12:41pm

new builds have all zoneinfo-* ... was feeling selfish with just mine... ( + wpa_cli, netperf... button-hotplug )

Thebroughfamily · August 11, 2020, 6:59am

Do you have a .config file for the community build? I build my images with all my data built in, so it would be handy to enable me to use this build

anon50098793 · August 11, 2020, 7:07am

i'm using the imagebuilder in the git repo you will find;

ibbuildinformation.txt
change the FILES variable to your files folder
remove or change the BIN_DIR variable
change BOOTPART and ROOTFSPART sizes in .config

and add the line;

make image rpi-4 FILES="$FILES" DISABLED_SERVICES="$DISABLED_SERVICES" PACKAGES="$PACKAGES"

place this within your extracted IB folder and fire away!

( for anyone else, i'd recommend just uploading a restore.tar.gz... then ensuring changes to be preserved during upgrade are added to sysupgrade.conf... note: exclude rc.local from your vanilla backup or overwrite it with ours once restored )

Thebroughfamily · August 11, 2020, 7:11am

Oh my God that's well over my level of knowledge... I thought I was doing well getting the build image working lol

anon50098793 · August 11, 2020, 7:14am

go with option 2 then... just upload the restore.tar.gz after....

another option is to mount partition two after writing... and put you files there prior to placing the sdcard into the pi...

I just did that as I swapped the gateway device i'm using, so after writing the factory... setup a simple dhcp network file for the pi.

jnachtigall · August 12, 2020, 6:52am

Same problem here. Only wireless "legacy" mode creates a visible AP that I can connect to with my smartphone. "N" or "AC" do not create a visible AP.

Also the luci UI says "Mode: client" instead of "Mode: AP" then. Very strange:

(this is for "N" and "AC" - for "Legacy" it works and says "Mode: AP")

I have no idea what I could do.
I followed the advice of first using raspbian to set the wireless country code to "DE Germany". Does not seem to make a difference.

Any ideas?

Edit: This is with openwrt-bcm27xx-bcm2711-rpi-4-ext4-factory.img.gz from the rpi-4_snapshot_1.1.50-15_r13974_lts folder.

I also tried using the https://downloads.openwrt.org/snapshots/targets/bcm27xx/bcm2711/ instead of this build but there even the ethernet ping to 192.168.1.1 is flaky and wireless is not working at all (also not luci http interface as it seems)

anon50098793 · August 12, 2020, 7:52am

uci show wireless | grep -v 'key='

generally tho'

key longer than 8 chars
40 ( repeat with 20 if all else fails )
Country DE
Save > Luci > disable + wait + enable + wait ( and finally a reboot if that fails)

Are all 'mandatory', wifi is a WIP at them moment tho' in the general sense. I don't really use it... but i've tested a little and made some tweaks for others...

Thanks for the feedback!