When a client has a different node as the reader from the same user > does it mean you get cache-loopback ??? or ??
I try to figure out how this is possible, because I do only see 1 setting for node in cccam.
When a client has a different node as the reader from the same user > does it mean you get cache-loopback ??? or ??
I try to figure out how this is possible, because I do only see 1 setting for node in cccam.
Like you said, each oscam has one CC-Cam NodeID. Oscam never returns cache to the same nodeid as it came from.
So i don't understand the question..
Use one (1) group for correct de-duplication... (multiple groups on cache users in mode 3, will create double load since cache is registered/de-duped for each single group).
What I mean is this:
allmost all users show same node in the cacheex, for example:
Client number1 xxx.xxx.xxx.xxx 16570290882298068652X REVERSE CACHE PUSH 0 975274
But some of them show different nodes, like:
Reader number1 xxxx.xxxx.xxxx.xxxx 16570290882298068652X REVERSE CACHE PUSH 4686249
Client number2 xxxx.xxxx.xxxx.xxxx 16570290882298068652X REVERSE CACHE PUSH 0 975274
Reader number2 xxxx.xxxx.xxxx.xxxx 4A376288882298467896X REVERSE CACHE PUSH 4686249
Since each oscam has only one CC-Cam NodeID, I really don't understand this ?
It looks like the reader connects to a different oscam server ???
Well, i dont know how the NodeID displayed on the cache-ex page is generated exactly, but it is directly related to the CC-Cam nodeID setup in CC-Cam config.
When the CC-Cam NodeID is changed manually, the CacheEX NodeID changes with it.
Back looking at your stats.. I do understand your question now, and on first sight.., I don't have what you're having.. I have unique nodeid's for each unique oscam host.
Are you sure that both clients (number1/2) have different CC-Cam id's setup ?
It's interesting though.., i would ask this in the streamboard forum.
Thx
Posting Permissions
Reply With Quote