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 28 Jun 2018, at 08:26, m...@adrianschmutzler.de wrote: > >>> >>> >> >> It may be that board name has changed, what's your cat >> /tmp/sysinfo/board_name ? >> >> Now on ath79 should be tplink,tl-archer-c7-v2 so if doesn't match this is > the >> problem >> >> You can safely try with -F, but you'll be needed to recreate the >> /etc/config/wifreless file >> >> Regards >> >> >> _______________________________________________ >> openwrt-devel mailing list >> openwrt-devel@lists.openwrt.org >> https://lists.openwrt.org/mailman/listinfo/openwrt-devel > > The old boardname was indeed just "archer-c7" (for the v2). > > Maybe the SUPPORTED DEVICES for the tl-archer-c7-v2 in ath79 should be > updated to enable upgrades? It sounds an attractive idea, unfortunately the reality is that both the wireless config and led config change, so this ‘side-grade’ isn’t directly compatible. Personally I think the fact you have to force the install (sysupgrade -F) acts as a reminder that certain things need a gentle tweak afterwards. If a sysupgrade just went through, no warning, then I can see a lot of queries ‘I upgraded and now I can’t get wireless to work’. Often we advise people to beware upgrades from prior releases to consider starting configs afresh, this is changing build architecture as well. The fact that a forced upgrade works as well as it does is an unexpected bonus. Kevin
signature.asc
Description: Message signed with OpenPGP
--- End Message ---
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
