@LuKePicci I am actually using a DGA4132, and I installed the NFS Packages but they aren't containing the kernel modules. I wasn't sure if thats a mistake, or if it is not possible because of the missing sources.
@LuKePicci It seems that the DGA4131 is actually one of the several models of gateways that Fastweb sells in Italy under the name "Fastgate" (the other two are from Askey and Huawei).
Going back on topic, I asked Technicolor to provide all the modules that they themselves listed on their website, since some seem to be missing, plus some instructions on how to build the code they sent me, since it seems to be just a bunch of folders and there's no clear way to turn that into a .rbi (binary) file similar to the ones they use to distribute firmware updates.
While there are some hints here and there that Buildroot can be used to build something, that isn't enough. If anything, since Buildroot would be a part of the "scripts used to control compilation and installation of the software" mentioned in the GPL, they must include its sources too.
Heck, even Chinese companies (at least those that comply with the GPL) have the common sense to include a text file with build instructions in broken English.
Think they will never tell you how to produce a flashablle rbi as every firmware have is own platform key and signed key...
@Ansuel Well, they need to provide all the scripts needed to compile the code and install the resulting binaries and the kernel. See here: https://www.softwarefreedom.org/resources/2008/compliance-guide.html at section 4.2.2 in particular, where software in embedded devices is explicitly mentioned.
They might not provide the key itself, but they must nonetheless provide the scripts that allow to make an .rbi file signed with my own key (or any other key I input).
If, later on, someone can find the key somehow, such as by inspecting the bootloader, this would turn out to be useful.
Publishing a modified bootloader based on the one from Technicolor would be illegal, but if someone finds a way to bypass its security measures without modifying it, nothing can be done to stop him or her.
I agree with your position, it’s a principle (legal and moral) and although there’s some question about enforceability, there’s a clear breach of community standards.
I don’t like the chances of the company being obliged to meet their obligations though.
1 Like
I am about to contact them for source regarding:
DJA0230 & DJA0231
Any recommendations?
1 Like
@kevdagoat
Some tips:
- Ask for a specific software version in the format 17.2.278-0901008 (for example).
They insist on using this format even though in most cases it can't be seen by an average user, as the UI just displays 17.2 or uses an ISP-chosen version number that doesn't match with Technicolor's and they pretend to not know about it, even though they do (as can be seen in their own source code). - If they don't respond within a week, email them again.
- If they respond that they "are working on it" or some other vague statement, ask them for an ETA.
Waiting more than a month is, in my opinion, unreasonable, since they use version control systems. - If the archive they give you is incomplete or doesn't have a text file that tells you how to compile the source code to get a working image, keep "pestering" them (politely but very firmly) until they provide the missing files.
- If they keep delaying/not cooperating you can email the SFC as I did, they have more leverage than a random user.
2 Likes
Thanks for that.
1 Like
@Zen96
THANKS A LOT for your fight for the right things!
For all people: Here is a talk about OpenWrt+GPL violations: https://www.youtube.com/watch?v=r4lCMx-EI1s
This is just a example video. If you want more, you can search for further also on https://media.ccc.de
@Zen96 Ehi can you help me? technicolor won't release 4.1 code of thei new base
I have specific version and all but i really don't know how to contact them (the hard way as they don't answer to the open source email)
pm me if you want
No claim of that sort was made in this thread.
The issue is that the source code which IS covered by the GPL - such as the kernel itself - is not being released.
Edit: Whoa... Didn't realize how far back this thread went...
Also, @lleachii mentioned issues with Hamnet and AREDN near the beginning of this thread - that surprised me, hams are usually more about sharing, collaboration, and openness...
To be honest, I never followed the HSMM-Broadband developer community much. I couldn't even get someone to tell me how to flash my router back to vanilla OpenWrt. I don't think it was well-established (i.e. decisions on what hardware would be supported in the future); and they may have be using code that they wouldn't/couldn't easily share (e.g. the OLSR software - hence my need to flash standard OpenWrt).
This is a small excerpt of what I was told by a developer after many code inquires:
I’ve seen your post on BBHN about Development that has not been responded too.
Unfortunately BBHN has not been maintained since it separated from its developers team who now work on the AREDN project ( http://www.aredn.org )
BBHN’s SVN Repo is way out of date and it was never updated to match the code as it follows under recent versions as access to the Repo was never granted to the me during the years I worked on it so we continued under a git REPO.
So...information on the "old code" was eventually provided to me: http://www.broadband-hamnet.org/developer-documentation/86-svnrepos.html
AREDEN has improved:
@Ansuel Do you have access to the new Technicolor base? Could you please share a copy with me? I want to compile some kernel modules for the DGA4132.
I wouldn't mind have a look (new user, I don't think I can send messages yet, but you can find me on Github (deece), Twitter (@EvilDeece), or just Google my name to get my email).
1 Like
Hi @Zen96!
Please can you send me the source code you got?
My mail is suxsem at live.com or you can find me on ilpuntotecnico @Suxsem
Thank you!!
I asked they the gnu gpl code for a device almost 60 days ago, they answered at my first email but then they disappeared. I'm sending a reminder email every week but they doesn't send to me the code that I have the right to receive.
Is their behaviour normal? Can we report this situation somewhere?