Skip to content
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

FS#3377 - Add support for Technicolor routers which use customized OpenWrt #8276

Closed
openwrt-bot opened this issue Oct 10, 2020 · 3 comments
Closed
Labels

Comments

@openwrt-bot
Copy link

fvc:

Most new Technicolor routers have firmware based on OpenWrt. It's probably relatively easy to support these routers.

Their source code can be requested by email [[contact-ch.opensource@technicolor.com]], the email address can be found on https://www.technicolor.com/distribute/home-experience/regulatory-information

There's an OpenWrt user who successfully requested the source code by email https://forum.openwrt.org/t/technicolor-gpl-source-code-request/16233/62

There are OpenWrt users who own Technicolor routers who may be able to help with testing https://forum.openwrt.org/t/technicolor-dwa0120-tg589-vac-v2-openwrt-support/47440. I also own a Technicolor DWA0120 and am able to help with testing.

@openwrt-bot
Copy link
Author

fvc:

A number of ISP broadband packages include a free Technicolor router. So there're probably many users, I have two Technicolor routers from my ISPs, DWA0120 and TG589 VAC v2

@openwrt-bot
Copy link
Author

adrianschmutzler:

Thanks for letting us know. However, eventually somebody will still have to do the implementation. This probably is best handled/discussed at the forum (as seems to be the case already), until a device support PR/submission can be presented via the usual channels.

Since this is filed as a bug report, I'm closing it now.

@openwrt-bot
Copy link
Author

dedeckeh:

I'm afraid it will be impossible to support Technicolor routers as the software image is signed and the signature is verified by the bootloader at startup.
As long as the private key is not known this will be a no go

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant