The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped automatically by the mailing list software.
--- Begin Message ---On Sunday, July 12th, 2026 at 05:02, José Luis Gutiérrez <[email protected]> wrote: > Recent GL.iNet firmware releases (tested with version 4.5.22) > identify the GL-X300B as "glinet,gl-x300b-nor" instead of > "glinet,gl-x300b". > > As a result, sysupgrade rejects official OpenWrt images when > upgrading directly from the vendor firmware. > > Add "glinet,gl-x300b-nor" as an additional supported device alias > to allow seamless upgrades while preserving compatibility with > existing installations. > > Signed-off-by: José Luis Gutiérrez <[email protected]> > --- > target/linux/ath79/image/generic.mk | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/target/linux/ath79/image/generic.mk > b/target/linux/ath79/image/generic.mk > index c5eb5895e6..6c9d72d039 100644 > --- a/target/linux/ath79/image/generic.mk > +++ b/target/linux/ath79/image/generic.mk > @@ -1766,6 +1766,7 @@ define Device/glinet_gl-x300b > DEVICE_MODEL := GL-X300B > DEVICE_PACKAGES := kmod-usb2 > IMAGE_SIZE := 16000k > + SUPPORTED_DEVICES := glinet,gl-x300b glinet,gl-x300b-nor Looks good to me. You may want to mention in the commit message that a workaround is to temporarily overwrite the board name to allow sysupgrade to work: $ echo 'glinet,gl-x300b' >| /tmp/sysinfo/board_name $ sysupgrade ... Eric > endef > TARGET_DEVICES += glinet_gl-x300b > > -- > 2.43.0 > > > _______________________________________________ > openwrt-devel mailing list > [email protected] > https://lists.openwrt.org/mailman/listinfo/openwrt-devel >
--- End Message ---
_______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
