@geerlingguy hmm, one of the reasons wifi chipset vendors (for example to provide #OpenWrt support) more and more grown to refuse not just source code but also hardware/programming specifications because of a blind reference to the #FCC not allowing it. It’s understood that with documentation *anyone* can then modify it to use frequencies or modulations not permitted by the #FCC

This is now a completely useless argument, if the FCC doesn’t approve routers anyway, so I’ll say, let them release the full specs! It would actually benefit the router ecosystem to bring up everyone to at least the security of OpenWrt…

@obbardc Well I'm home.. I've got my test harness updated with #Openwrt 25.12.1 and its running (so the scripts etc on openwrt are all looking good - but - oh yeah you actually need to move the zone file to the cloud API right.. Ops. No problem - unless of course you are right in the middle of a #brownout during the #hetznerdnsapi shutdown..

This does actually point to another issue. I'm going to have to move all devices that use same zone file at the same time. (Obvious in retrospect) - Luckily I run a few domains so I can test a bit with one first.

Upgrading with "my configuration" to the official 25.12.x image works for whatever reason, so it seems to be a combination of my configuration and my self-built image **together**. Funny...

#OpenWRT #SelfHosting #HomeLab #AdminLife #HellYeah #AVM #FritzRepeater1750E

OK, for some reason my self-built image works when the device was factory-reset. Or the configuration works on 24.10.6, but the device breaks when upgrading to 25.12.0 or 25.12.1 with "my" configuration.

For now I am staying on 24.10.6, as I got sick of debugging and resetting and flashing for hours today...

#OpenWRT #SelfHosting #HomeLab #AdminLife #HellYeah #AVM #FritzRepeater1750E