Node and NodeID

[Satphoenix]

I have a question about the NodeID.

What is the meaning of it and how is it put together?
I see the NodeID in the cccam webinterface but I don't know the meaning of it.

Thanks in advance

[Jerry2020]

Re: Node and NodeID

I think it is a random number given to the node

[Satphoenix]

Re: Node and NodeID

I think it is a random number given to the node

Ohh, I don't think it's pure random.

When I compare this two nodeIDs:

113355661e7eed7b

113355665ed2f035

from different servers at the same time, I don't believe that they are completly different.
There must be a system in the structure of this number!?

[Jerry2020]

Re: Node and NodeID

Looks like the second part is random. The first part may depend on the start up time or so. There has to be some randomness since they are generated by independent sources.

[vimmers]

Re: Node and NodeID

its the receiver there share the card equal to box id
and it can change if you restart the box or the share box restart

[Satphoenix]

Re: Node and NodeID

...and it can change if you restart the box or the share box restart

Actually I have tested with 4 (free-) lines in the config and all had the same nodeID after a box reset/restart. Satlover server3 and 4 had exactly the same nodeID.
Is it possible that the NodeID is a identification-number of the server the box is connected to?
And if the first half of the node is the same (like in pst 3) it's a reshare line from one to another server?

[vimmers]

Re: Node and NodeID

maybe luck but i have seen them change
you can actually use those nodes to block a card
like this

# Option to ignore all shares that go through a certain node
#
#Ignore node: <nodeid>
#
#example, ignore two nodes:
#
#Ignore node: ccd536ab515767ad
#Ignore node: aad536ab515761af

[Satphoenix]

Re: Node and NodeID

maybe luck but i have seen them change

I think it's only an identification number from the server.

I've expanded the test up to 2 different receivers with different cccam versions (switched one off and the other one on to keep the lines alive).

The result was that the NodeIds were exactly the same than in the first receiver.

I don't think it's luck or random, but as you said a good possibility to disable a certain node.