-
Notifications
You must be signed in to change notification settings - Fork 325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mark Ubiquiti Rocket M5 as Deprecated or Broken #2070
Comments
Hmm, the Rocket M2 and M5 share the same image. We currently can't deprecate only a single alias of a device (and allowing to do so would further complicate our already very complex target definition handling), so I guess we should just remove the alias? (turning it into a manifest_alias to make sure existing installations can still get updates) |
Is it really "must not be used anymore"? As I read it, it's not allowed to give it to somebody else (selling or even as a present). Even it's not written by the words it seems a logical consequence not to operate the device anymore. Probably this will announced in the next months. |
I agree that the publication does not prohibit the operation alone of these devices. But regardless of the interpretation of the order, it is not in our interest to promote the operation of hardware that is known to interfere with other devices. |
The hardware allows for very high transmit power (>=1W) if configured for regulatory domains which allow that. I assume that some people have just abused it in that way and it became "famous" among "TX-power fanatics"... It may hence also very well be that the device (if operating within legal ETSI power levels and with well-designed antennas) is just fine. |
@dangowrt the wording is:
I assume that the french authority did correct measurements and used a conforming setup. |
I imagine them repeatedly confiscating that model emitting crazy transmit power and/or ignoring radar avoidance rules (supposedly setting wrong country code or by using 3rd-party-firmware). |
They explicitly mentioned "suspicious emissions" and "adjacent channel interference" not something easy like "to high EPIR" or "not conforming to DFS-rules". The 2 latter would have made it much easier to regulate. At the end of the order they put the official way to contact them and "blame" them. |
I just read that now and yes, that's better, because if it's really the hardware being noisy (or becoming noisy over the years) case ubnt is less likely to blame that incident on the use of 3rd-party-firmware and increase their locking efforts... (and in that case it's also legitimate to argue that gluon, OpenWrt and so on should stop shipping binaries for that hardware) |
The authorities
So if the further use of the device for a client is not illegal, why should we not deliver firmware updates? |
@Neoraider wrote explicitly about turning the alias into a manifest_alias so that no image with the ROcket M5 name is generated but existing devices still get updates served. |
This follow up the discussion done in freifunk-gluon#2070 by not creating a symlink for the Rocket M5. Images for the Rocket M2 can still be flashed on a Rocket M5. This change will prevent the Rocket M5 from appearing in Firmware selectors. Existing devices will still receive updates, as the device name is still referenced for the device name expected by the M5. Closes freifunk-gluon#2070
* ar71xx-generic: only create manifest alias for Rocket M5 This follow up the discussion done in #2070 by not creating a symlink for the Rocket M5. Images for the Rocket M2 can still be flashed on a Rocket M5. This change will prevent the Rocket M5 from appearing in Firmware selectors. Existing devices will still receive updates, as the device name is still referenced for the device name expected by the M5. Closes #2070 * docs: remove Rocket M5 from supported devices
The German Bundesnetzagentur has announced that the "UBIQUITI ROCKET M5" must not be used within Europe any more. From https://www.bnetza-amtsblatt.de/download/36 section "Vfg Nr. 73/2020":
Note that this actually affects all of Europe (not just Germany); probably other countries have made similar proclamations.
Therefore I propose that this hardware is marked as deprecated or broken, so that the firmware is no longer built by default.
The text was updated successfully, but these errors were encountered: