SamyGO

3 pages in a day about updates blocking !!!
Anyway, forget about blocking with firewall/string rules; it won't work with https requests.
Excluded web proxy, the only way is using (cheating) dns.
To make it short, if you are on static ip, an external dns service (such as OpenDns) will do the job.
If you are on dynamic ip (the most of us, I guess) tv should point to an internal "poisoned" dns, and dnsmask is the most common feature we can find in our cheap home routers.
In 2 months using this technique no one update passed to my sammy.

mihd wrote:

sectroyer wrote: You probably blocked by string ("block url containing" or something like that), blocking by ip is ALSO bad idea. You can only block by ports or by dns. NO OTHER WAY.

Why blocking by ip is bad idea ?
block by dns - it is understandable..
"..block by ports.." - How ?

Because they change ip all the time. It's called "load balancing" Some times ports are called "services" in router config. Try blocking all ports and see if it helps

gianni253 wrote:3 pages in a day about updates blocking !!!
In 2 months using this technique no one update passed to my sammy.

Yeah because many people tried blocking by string/url and thought it works so I tested it myself. I didn't get ANY updates for almost a YEAR:P So yeah we are and will be talking about updates and won't release a shit until we figure out what works and what doesn't

sectroyer wrote:

gianni253 wrote:3 pages in a day about updates blocking !!!
In 2 months using this technique no one update passed to my sammy.

Yeah because many people tried blocking by string/url and thought it works so I tested it myself. I didn't get ANY updates for almost a YEAR:P So yeah we are and will be talking about updates and won't release a shit until we figure out what works and what doesn't

As you keep repeating many times, it's not developer's responsibility to block updates and find what works and what don't in the thousands of routers out there.
And there is no need to wait 2 days or two years to see if blocking is effective or not ... just type the https url from browser !
For instance ... try blocking *.facebook.com ... your family will tell you in a few minutes !!!

sectroyer wrote: Because they change ip all the time. It's called "load balancing" Some times ports are called "services" in router config. Try blocking all ports and see if it helps

They change only "downloading ip", but "authorization ip" remains the same.
"authorization ip" - 157.55.184.57 ( www.samsungotn.net)
"downloading ip"'s - 68.232.34.240,93.184.221.240 (az43064.vo.msecnd.net), 2.22.237.26,2.22.237.9,95.101.72.215, 217.212.252.86, 217.212.252.72, 2.21.246.57 and other (otn.samsungcloudcdn.com)
az43064.vo.msecnd.net now is not used.
After reading the article Samsung OTN protocol and after testing with other users I came to a conclusion, that there is no sense to block "downloading ip"'s. They are periodically changed when requesting from authorization server (www.samsungotn.net). But blocking the authentication server makes sense.
However, do not block the domain name. Block IP-address is necessary. It is a constant and never changes.
That is to say, 157.55.184.57 on all ports !!! Only this address!

I am gathering some info about this unwanted updates. Please let me know if you had blocked updates on router and got updated to 1470 or 1471.

I have blocked the updates on router. And i still have 1470.

Still 1440.8

still 1422

(Blocking with hosts file on openwrt)

Will have my JU7005 her tomorrow, so any Christmas present for us sectroyer ?
Blocking in router made ready for deploy

/Spawn