Fork 380.57 HGG-FINAL

[bits]

Just wondering do you code and build your own fw?

I develop a win32 application with roughly 250k lines of code of which I guesstimate I personally have written or altered 5%, I guess at another 80% from other direct team members and the remaining is external code that is directly included. Most of the external code (and there is a lot) is dynamically linked in and not included in the source code line count.
All our code is released under BSD license which is much more relaxed than GPL. Hgg could take our code, use it and not need to release the source code.

 

[bits]

Compelling arguments on both sides, not being sarcastic.

Some understand the risks and some are trying to protect others who are less knowledgeable and get proper accreditation to individual authors.

My main argument is the GPL violation. This firmware is breaching the GPL license and stealing from the charitable people that make this firmware possible.

If these people dont want to release their code they can remove all GPL code, rewrite as their own and release a closed source module.

EFF does request we try our best to resolve the GPL violation without including their legal teams. It is nicer and easier that way.

 

[Undesirable]

How do you get the country blocking script on the Wiki working with this fork? https://github.com/RMerl/asuswrt-merlin/wiki/Using-ipset

I get errors:

/jffs/scripts$ sh /jffs/scripts/firewall-start
iptables v1.4.14: Set TorNodes doesn't exist.

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.14: Set BlockedCountries doesn't exist.

Try `iptables -h' or 'iptables --help' for more information.
iptables v1.4.14: Set MicrosoftSpyServers doesn't exist.

When I try to launch it.

 

[shooter40sw]

media fire is kind of working really bad, cant download anything, just downloads 2Mb and stalls and stops, no other links to the firmware?

 

[kvic]

"You agree to not use the Service to submit or link to any Content which is defamatory, abusive, hateful, threatening, spam or spam-like, likely to offend, contains adult or objectionable content, contains personal information of others, risks copyright infringement, encourages unlawful activity, or otherwise violates any laws."
http://www.snbforums.com/help/terms
http://www.gnu.org/licenses/gpl-violation.en.html

Forum reputation is important but it's not our forum. The Admin either allows this or not - won't matter what any of us have to say.

This thread could have been 7 pages shorter.

I agree with your assessment.

@thiggins you may want to spend some time understanding the legal issue of this fork out of your busy schedule.

 

[Nullity]

I agree with your assessment.

@thiggins you may want to spend some time understanding the legal issue of this fork out of your busy schedule.

The only legal issue is the public posting of the links, which is already known to be frowned upon, I thought (the original thread by hgg was edited to remove all links).

We can talk about practically anything, including the fork, hopefully...

 

[GGavan]

I have a question... I created also for this one a new thread but no answer yet. I can't even remove it from there.
Because I use this FW maybe the right place for the question is here..

It is possible to use DLNA with shared folders from network and not just with attached drives?
I have more sources available as windows shared folders and I would like to use DLNA from my router AC87U
Any idea?

Thank you in advance!

 

[bits]

The only legal issue is the public posting of the links, which is already known to be frowned upon, I thought (the original thread by hgg was edited to remove all links).

We can talk about practically anything, including the fork, hopefully...

The file(s) in a publicly available folder on a public file sharing host which the public are downloading from.
How on earth is this binary not released to the public?

Ps let us talk about the gpl violation, it is extremely important.

 

[lepa71]

People. Please, PLEASE stay on topic. Stop discussing legal things here. Open your own thread and go away.

 

[Nullity]

The file(s) in a publicly available folder on a public file sharing host which the public are downloading from.
How on earth is this binary not released to the public?

Ps let us talk about the gpl violation, it is extremely important.

My post was regarding the legal culpability of this forum, not hgg.

PS - I personally do not care that hgg is violating the terms of the GPL. If you want to get mad there are companies who are violating the GPL while actually making profits from the pilfered code.

 

[Nullity]

People. Please, PLEASE stay on topic. Stop discussing legal things here. Open your own thread and go away.

It would make more sense for you to start your own thread. The topic of this thread is well-established now (and on-topic, in my opinion) regardless of the original intent.

 

[lepa71]

It would make more sense for you to start your own thread. The topic of this thread is well-established now (and on-topic, in my opinion) regardless of the original intent.

Do you have this fw installed? The topic of this thread is to inform that there is a new version is available and it's not posted by HGG. You are enforcing your opinion on legality for this fw on other. IT IS NOT ON TOPIC OF THIS THREAD. GO AWAY. BUILD YOUR ONW(BETTER) FW AND PUBLISH IT THAN TALK ABOUT OTHERS.

btw my post was to respond to people who is talking about legality of this fw.

 

[got_milk]

Do you have this fw installed? The topic of this thread is to inform that there is a new version is available and it's not posted by HGG. You are enforcing your opinion on legality for this fw on other. IT IS NOT ON TOPIC OF THIS THREAD. GO AWAY. BUILD YOUR ONW(BETTER) FW AND PUBLISH IT THAN TALK ABOUT OTHERS.

btw my post was to respond to people who is talking about legality of this fw.

Take a deep breath and calm down, please. The title of this thread is "Fork 380.57 HGG-FINAL". I think a discussion on the legality of the firmware is in scope of this thread.

 

[BreakingDad]

Anyone else think it's a little strange that the man himself has yet to make a comment in this thread ?

 

[lepa71]

Take a deep breath and calm down, please. The title of this thread is "Fork 380.57 HGG-FINAL". I think a discussion on the legality of the firmware is in scope of this thread.

You see, I would respectfully disagree with you. The only reason people talk about legality of HGG fw in this thread is that everybody would ignore them in any other threads. They, who wants to talk about legality, have a choice NOT to install it. Look at this thread, out 9 pages 95% of it is about legal things. You can write it once, make your statement, warn people and they let it be. If moderator wants to delete this thread because it does not fit within guidelines of this forum, then so be it.

 

[Nullity]

Anyone else think it's a little strange that the man himself has yet to make a comment in this thread ?

Not really. Regarding the GPL fiasco, there is not much that can be said. It is either GPL compliant or not.

 

[Nullity]

You see, I would respectfully disagree with you. The only reason people talk about legality of HGG fw in this thread is that everybody would ignore them in any other threads. They, who wants to talk about legality, have a choice NOT to install it. Look at this thread, out 9 pages 95% of it is about legal things. You can write it once, make your statement, warn people and they let it be. If moderator wants to delete this thread because it does not fit within guidelines of this forum, then so be it.

Right, and I respectfully disagree with you. So, I will allow you say what you think is on-topic, and you allow me the same courtesy.

Seems fair to me.

 

[bmn1]

questions:

1) any noticeably difference between HGG 380.57 and HGG 378.51-55 releases ?

2) does this 380.57 HGG release have setup script for entware-ng?
(RMerlin includes entware-ng instead of entware since 2015-11-23)

3) anyone here using with RT-N16 , how noticable improvemnt will be RT-N16_378.55.3_HGG-FINAL.zip comparing to older RMerlin RT-N16 builds 374.43 (wiouth radio limitation)

suggestion:

1) IF hgg uses other authors patches (aside from ASUS and RMerlin) - at least credit them, may be ask them to cross license their patches in bsd

hypothesis:

1) may be hgg do not want to share his patches YET because it can be blocked by asus in future versions of driver blobs?

(hgg uses newer driver, as you can see in RT-N16 folder "Firmare RT-N16_380.57.1_HGG-FINAL version will be delayed and will be out only when ASUS release the new binary blob files missing on this model." )

 

[GGavan]

questions:

1) any noticeably difference between HGG 380.57 and HGG 378.51-55 releases ?

2) does this 380.57 HGG release have setup script for entware-ng?
(RMerlin includes entware-ng instead of entware since 2015-11-23)

3) anyone here using with RT-N16 , how noticable improvemnt will be RT-N16_378.55.3_HGG-FINAL.zip comparing to older RMerlin RT-N16 builds 374.43 (wiouth radio limitation)

suggestion:

1) IF hgg uses other authors patches (aside from ASUS and RMerlin) - at least credit them, may be ask them to cross license their patches in bsd

hypothesis:

1) may be hgg do not want to share his patches YET because it can be blocked by asus in future versions of driver blobs?

(hgg uses newer driver, as you can see in RT-N16 folder "Firmare RT-N16_380.57.1_HGG-FINAL version will be delayed and will be out only when ASUS release the new binary blob files missing on this model." )

1. I can say compared with 378.55.3 that the current one is much better in range, better bandwidth and much better wireless stability on AC87U

There are many improvements but these ones are most important for me. The others were ok also before. Many new updates and fixes.

 

[Undesirable]

So has anyone developed a firewall blocking script for bad IP ranges / MS Telemetry with this fork, cos I can't get any of the example ones to work.