Namidairo
Joined 11 years ago
Joined 11 years ago
Unfortunately for them, the implementation of it is broken because it only verified the first 32 bits of the signature, so thingino (a 3rd party firmware replacement) now just calculates it during build for that device.[1]
As for the camera being dead, do find out if it's just corrupt or something. Those line of cameras are fairly forgiving in regards to re-flashing broken images. (They have both microsd fallback and an ISP mode, I believe.)
Wyze as a company however have pulled their own firmware images from their support site, which kind of makes brick recovery painful. I don't know why they would do this.
Wifi antennas would typically be internal and unrelated to the one F-Type coaxial connector one would typically think of as the "antenna" input.
Can't really stop the internal module from scanning and connecting to open access points unless you control the software.
There's a couple ISP branded units that fit those parameters, with caveats. (Mostly around OpenWrt installation difficulty and the always in development state of brand-new 11be platforms)
However due to the price (Depending on availability in the 2nd hand market, it's very possible to get tri-band 11be routers for USD$50-100, usually with one or two 10GBaseT interfaces), there are still quite a few that overlook some of the difficulties involved.
> triggered to run every 10 seconds because the PPPoE interface doesn't provide an 'on change' event hook.
Normally this should be handled by a hotplug.d script in /etc/hotplug.d/ but I'm not familiar with the stock Mikrotik firmware.
Many Epomaker boards are just licensed to be sold under their brand name, most of them fairly transparently. (Ie. Epomaker x Aula, Leobog etc.)
Quite a few of their configuration software packages end up looking quite horrible as a result, as I don't believe they have a unified software package for all the brands they sell. Many Windows Forms looking programs that look like a time machine back to the era of Windows XP.
Unfortunately they've also been caught up in quite a few scandals over the years: QMK license violations Customer support/Quality control issues Attempts to dodge customs by deliberately under-declaring the value of their packages... Got into a legal fight when another company also licensed an identical board design and beat them to market (The other company aren't angels either) Platform banned from Reddit for astroturfing
Which kind of just results in Epomaker in being a hard discourage.
Another issue is semi-compliant ONVIF implementations for PTZ cameras and/or not having relative movement implemented. Or you know, just lacking RTSP and ONVIF entirely.
> Coupled with the fact that many brands are just using the same recycled white-label Chinese firmware, I'm not surprised.
SDKs for many of the SoCs not being available is really annoying as well. Some of the Ingenic, Sigmastar, Goke etc. are available, but I think many were just leaks from customers rather than intentional releases.
Soon?
I've already seen multiple of TP-Link's firmware engineers leave their LLM history public and indexed by search engines.
It's quite obviously them as well.
Australia has a national test of it's phone alert system in 10 days at 27/07/26, 2PM AEST. (People in North America would know it as Cell Alerts/Presidential Alerts etc.)
There have been warnings that hidden phones will almost certainly sound, and their recommendation is to ether power off the phone or put it into airplane mode at least an hour before the test...
Quite a few of the modules went out without their eeprom programmed correctly, and all of them appear to be plagued by quite mediocre performance from (alleged) inadequate RF shielding on the card.
It looks like they've revised the design, but it's peeved off quite a few of the Banana Pi/Sinovoip customers who have bought them with the intention of using it as a router/ap with their R4. (It's dual-PCIe fingers with unique spacing and requires out of spec PCIe voltages, so it's only practically usable with a BPi R4.)
At the very least, the customers using them as wired-only routers are likely to be having a slightly better experience.
It went down as well as about you would think it would.
[1] https://www.eff.org/deeplinks/2017/07/australian-pm-calls-en... (2017)
If I recall, I had a fairly decent view of their various checks because it was delivered completely unminified, including a couple amusing sections and unimplemented features. (A gesture detector with the middle finger gesture in the enumerable commented out, for example...)
Another attack vector that I speculated upon was intercepting and replacing their tflite model with ones own, returning whatever results required.
Additionally, I believe they had a check for virtual camera names in place, as checks would quietly fail with a generic message in the interface, but show the reason as being virtual camera within responses. (Camera names are mutable though, so...)
Yeah we've had a similar thing happen in Australia. Most VoIP services require you to either tick a box or verbally waive one's rights to said requirements in regards to reliability and fault rectification timelines.
However, there hasn't been too much of an issue with transition to VoIP here, apart from the unreliability of some services they're being run on, and keeping emergency contact details up to date. The latter resulting in fines for providers here and there.
Mostly, it's just pushed mobile/cell services to the forefront, along with reliability concerns during major outages. (There have been a couple major outages to cellular/mobile connectivity where access to emergency services have been lost)
Surveyed usage of landlines for calls at home is about 12% here, down from about 54% in 2017.[1]
[1] https://www.acma.gov.au/publications/2026-02/report/communic...