Hello everybody,

In addition to CapNCooK's post.

Please stick to the facts when describing your server and your cache:
There is no point in using adjectives e.g. "big, huge, massive, strong ...".
These are only words and they are quiete useless.
If you want to describe your server then stick to some usefull technical facts e.g.
cache-size/provider (all providers)/cacheex_maxhop
By means, How big is the cache size that you will deliver per provider (package) or per all of your packages at a specific cacheex_maxhop level.

Fresh cache/Non fresh cache/Second hand cache/Bugs Bunny cache:
Please do not tell stories about some magic "fresh cache" coming directly from a proxy or a card at hop 1.
If your proxy/card sends the CW's late then your cache is also late (bad cache).
At the opposite if your cache comes through several hops but in time then it's a good cache no mater how many hops.

How can i see if my peer is good or cheating:
Some "very inteligent" peers set the cccam node ID in "oscam.conf" manually.
They use two Oscam instances with same node ID. One receives your cache and the other sends it back to you.
This way they will send a resonable "at least an equal" amount of cache without having real own cache or other good peers on their server.
You can check that by
- turning down your reader and see if your peer is still delivering the same amount of cache with your reader connected to him.
- asking your peer to NOT set the Node ID in "oscam.conf". You can note the Node ID of your peer (client Node ID in WebUI). After your client reconnects he MUST have a different Node ID (this happens when he restarts his Oscam).

Happy share
#####################
Do not forget to press the thanks
button if you find this helpfull
#####################