OpenWrt 21.02.0 second release candidate

[anon50098793]

@mpa any chance of gathering serial state?

ifconfig -a; dmesg | tail -n 100

would help alot... otherwise just;

cat /tmp/board.json

will help... or feel free to test this;

sample-workaround

--- a/lib/preinit/10_indicate_preinit	2021-06-07 05:21:51.000000000 +1000
+++ b/lib/preinit/10_indicate_preinit	2021-06-17 01:44:44.331353701 +1000
@@ -73,9 +73,11 @@
 	json_select network
 		json_select "lan"
 			json_get_vars ifname
+			json_get_vars device
 		json_select ..
 	json_select ..
 
+	[ -z "$ifname" ] && [ -n "$device" ] && ifname=$device
 	[ -n "$ifname" ] || return
 
 	# only use the first one

[anon72830772]

Release Candidate 3 for Archer C2600 and corresponding software such as irqbalance, available for download. Testing a C2600 currently.

[robho]

I can't reboot my Netgear R6220 when running 21.02.0-rc2. Running "reboot" on the console does nothing. Rebooting through luci does nothing. Anyone else seeing this?

Oh, btw.. No information in kernel or openwrt logs.

[mpratt14]

@robho

Running "reboot" on the console does nothing

do the network interfaces disable and processes close? or literally nothing happens?

[robho]

Interfaces remain up, processes are not terminating.

[shakin89]

i have the same exact problem with rc3.
The weird thing is that i have 3 tp-link archer c6 v2 eu version, one has the problem that doesn't reboot, the other two acts regularly.
reboot, poweroff, halt -> no action executed.

Reboot command doesn't reboot

Hi all, i have 3 tp-link archer c6 v2 eu version, all with openwrt 21.02-rc3. On one of these (shakWifi_p0), the reboot command from luci doesn't work, so doesn't from command line. from the non-working router root@shakWifi_p0:~# ls -al /sbin/reboot lrwxrwxrwx 1 root root 14 May 28 16:04 /sbin/reboot -> ../bin/busybox root@shakWifi_p0:~# uptime 22:37:48 up 5:10, load average: 0.04, 0.07, 0.03 root@shakWifi_p0:~# date Tue Jun 15 10:09:23 CEST 2021 root@shakWifi_p0:~# halt…

[mpa]

@mpa

In failsafe mode, the device is not reachable via the network.

@anon50098793

feel free to test this;

sample-workaround

--- a/lib/preinit/10_indicate_preinit	2021-06-07 05:21:51.000000000 +1000
+++ b/lib/preinit/10_indicate_preinit	2021-06-17 01:44:44.331353701 +1000
@@ -73,9 +73,11 @@
 	json_select network
 		json_select "lan"
 			json_get_vars ifname
+			json_get_vars device
 		json_select ..
 	json_select ..
 
+	[ -z "$ifname" ] && [ -n "$device" ] && ifname=$device
 	[ -n "$ifname" ] || return
 
 	# only use the first one

I applied a variant of your workaround.
Now the network configuration in failsafe mode is fine - thank you.

modified workaround

--- a/lib/preinit/10_indicate_preinit	2021-06-12 17:36:52.597146354 +0200
+++ b/lib/preinit/10_indicate_preinit	2021-06-16 23:27:57.485615919 +0200
@@ -72,10 +72,11 @@
 
 	json_select network
 		json_select "lan"
-			json_get_vars ifname
+			json_get_vars device
 		json_select ..
 	json_select ..
 
+	ifname="$device"
 	[ -n "$ifname" ] || return
 
 	# only use the first one

[lknz]

Same problem here with rc3. Can't reboot the device.

Router: ZBT-WE826 (32M)

[aparcar]

When building with the ImageBuilder a usign aka signify key is created which can be used for signing the images. Signed images allow verification before installation, so a running device checks if it trusts the signature an image is signed with. Officially released images contain OpenWrt signing keys, but if you build and sign your own image, you can use ADD_LOCAL_KEY so your running device will trust your own ImageBuilder as well.

All of this is only active if ucert is installed and export REQUIRE_IMAGE_SIGNATURE=1 is set before running sysupgrade on the device.

[anon50098793]

@aparcar

only active if ucert is installed and export REQUIRE_IMAGE_SIGNATURE=1 is set before running sysupgrade

@aparcar

you can use ADD_LOCAL_KEY so your running device will trust your own ImageBuilder as well

cool feature... thanks!

validation is a great backstop when it comes to man in the middle or other remote vectors

[tmomas]

Please head over to OpenWrt 21.02.0 third release candidate