Satellite dish signal was down at 75 all weekend and experienced regular freezing. Now back up at 90 (typical) and not
experienced single freeze in the last 2 hours. All a bit odd.
Hi all,
Im not usually on this section of the website, but my line provider sent me the link.
Me & the relatives have 3 lines - Paisley, Glasgow & North Lanarkshire, with 2 of us on Sky BB and one on Virgin, and the channels have been glitching like hell all weekend, with 2 lines actually going down between 2:30 and 4:30 today, even though they were fine at the server end.
Im kinda relieved that Im not going nuts and this is clearly a nation wide problem, but Im also concerned that clearly, Sky are up to something.
There are too many people on different servers all with the same issue for this not to be an issue at the "source".........
to all who are on sky broadband on zgemma boxes
Menu
setup
system
network
adapter settings
click blue for edit DNS
change nameserver 1 to 208.67.222.222
change nameserver 2 to 208.67.220.220
press save
sky themselves have changed to iptv6 which everybody on sky internet needs to do this
could work on other providers that are having the same problems
turn off dchp if that doesnt work then type it in
hope that helps??
I'll give a brief explanation - I hope it makes some sense.
I'd say the majority sat servers (not all) share the same cache since just running on local cards isn't viable due to the load put on the cards, although, most servers just run on cache without any local cards at all.
What's happening most likely is that some bad cache is reporting bad keys such as 44332211 rather than 11223344 as an example. This will be fixed once the source of the bad cache is found and removed which will then fix the bad key reporting leading for the ECMs to reach without the bad source resulting in no glitching.
These days it's very rare to find a server with actual local cards - they could just turn the cache off until the issue is resolvd. Another point to mention on Sateliite is that the QAM256 trick can be used by servers running OScam to fool boxes that report CAIDs that they have locals when they actually do not - it's like a phantom card.
To sum it up, cache is amazing when it works but when it has issues, it's hard to track down the source. Cache exchanging (as these keys cannot be controlled or their reliability guaranteed) can lead to freezing if the channel clears from the cache-exchange but doesn't reach within the ECM timeout.
Edit: One IMPORTANT fact - Just because a server is more expensive than others, it doesn't mean it has local cards either.
So what your saying is the servers that are having problems have no cards ?? or they would have disabled there cache peers 1 by one until they sorted out the bad cache peer is that right????
It all comes down to cost. No server will buy many local cards since they are obviously expensive and they would most likely make a loss.. I was just saying there that running with 1 card WITHOUT any cache would put heavy loads on the card (depending on the amount of clients). Not to mention the servers who just run on cache completely without locals.As for it not been viable to run on just locals because of load on card not really true. The cost would have more of an affect on the server running on just locals as a medium or large server would build up enough local cache rather than remote cache to ease the load on card/cards ,and would be able to split the load between cards .
That is correct.As for the 256 that been going years also multics shows servers as having loads of cards where they only have cache peers.
Have to agree with you on that one a server that is more expensive don't mean he have local cards best thing anyone should do is test a few out see what one they happy with money wise and glitch wise and never take a years sub.