hi guys just a quick one please if your have got a good share of a package is there a way of pointing your cccam to get it from that person before picking
someone else or if your have got more that one share of that package how does your cccam choise?
shares
-
- Various Support
- rigrat1
- Thread is marked as Resolved.
-
-
I put mine to the top, but cccam will always normally pick the quickest ecm m8 ;)
Mutz
-
hi mutz when you say the top do u mean top of the confq
-
Yeah m8 put them at the top of your cfg ;)
-
ok m8 thank u will give it ago
-
The best way is just to block the provider on the cline you do not want to receive it from.
e.g C: exampledns 12000 user pass no { 0:0:2, 0963:0 }
-
if somone gives you a share with a reshare but you dident want others to be able to use that reshare is there a way to stop this ?
-
if somone gives you a share with a reshare but you dident want others to be able to use that reshare is there a way to stop this ?
Like this
F: user pass 2 0 0 { 0:0:1 } { } { } peers dns
This allows to view your local, hop1&2 but not reshareF: user pass 2 0 0 { 0:0:2, 0963:0:0 } { } { } peers dns
this allows your local, hop1&2 but stops him receiving provider 0963F: user pass 2 0 0 { 0:0:2, 0963:0:1 } { } { } peers dns
this allows your local, hop1&2, he can view provider 0963 only & not reshare itAll this info is already on the forum mate, try using the search & reading what you find.
-
hi ten thanks for the reply so if i want to block some of my shares from getting s*ly what number do i use 0963?
-
and do i have to put the peers dns at the end of the line?
-
F: user pass 2 0 0 { 0:0:2, 0963:0:0 } { } { } peers dns
F: user pass 2 0 0 { 0:0:2, 0963:0:0 } This blocks him getting sly...
{ } { } peers dns - This is locking the line to there dns so it cannot be used if there cfg is hacked and clines stolen! it is good practise to lock all Flines to your peers dns! -
hi ten thanks for the reply so if i want to block some of my shares from getting s*ly what number do i use 0963?
and do i have to put the peers dns at the end of the line?
Those examples were for the white card yes, putting the dns at the end of the line means the only person that can use the line is who you gave it to. Without this your line can be used by anybody.
Always lock the fline to your peers dns.
-
thanks guys for the help chears
-
apart from this info already posted on the forum, if you look at a "full .cfg" you´ll see all the options:
######################################################################
# friends #
######################################################################
# syntax for to add a friend user to CCcam with the max up hops limit (default = 5)
# sharing of emus (default = 1), allow emm (default = 1), and optional
# downshare limits per share (default = no limits) and optional
# downshare limits per share based on caid:id:sid
# and optional timeslots in which share is valid (to block channels on box of children after 19:00 for instance)
# if no timeslot is defined 24 hrs a day is used
# emus are shared only one level down, even if no limits given
#
# max username length 20
# password length 'unlimited'
#
#F: <username> <password> <uphops> <shareemus> <allowemm> ( { caid:id(:downhops), caid:id(:downhops), ... } { caid:id:sid, caid:id:sid, ... } { begintime-endtime, ... } ) hostname/ip address
#
# example:
#
# F: user1 pass1
#
# user1 gets all our shares at max 5 hops from us
# (our local cards + max five hops away). He can share down to his own
# clients. He also receive emu shares (if he has 'yes' behind his C: entry),
# and is allowed to send us emm.
#
# F: user2 pass2 0 1 0 { 0100:000080, 0622:000000:1, 0500:000000:2 }
#
# user2 gets only our local cards but no 0100:000080.
# and our 0622:000000 cards only for himself (1 hop down),
# and 0500 cards for himself plus one additional hop down.
# He also gets our emus, and is NOT allowed to send us emm (updates).
#
# F: user3 pass3 5 0 1 { 0:0:3, 0100:000080:1 }
#
# user3 gets all cards at a maximum of 5 hops away from us,
# and get's to share them down two further levels beyond his own level.
# But he is not allowed to share 0100:000080 down to other users.
# He gets no emus from us, and he is allowed to send us emm.
#
# F: user4 pass4 5 0 1 { 0:0:3, 0100:000080:1 } { 0100:000080:15df }
#
# user4 gets all cards at a maximum of 5 hops away from us,
# and get's to share them down two further levels beyond his own level.
# But he is not allowed to share 0100:000080 down to other users.
# He gets no emus from us, and he is allowed to send us emm.
# He is also not allowed to view channel 0100:000080:15df
#
# F: user4 pass4 5 0 1 { } { } { 12:00-17:00, 19:00-20:00 }
#
# user4 gets all cards at a maximum of 5 hops away from us,
# and get's to share them down two further levels beyond his own level.
# the share is only valid between 12:00 and 17:00 and between 19:00 and 20:00
# outside these hours the share will not give cw's to the client
#
#
# F: user5 pass5 5 1 1 { } { } { } 192.168.1.1
#
# user5 gets all cards at a maximum of 5 hops away from us
# user5 is only allowed to connect from the host 192.168.1.1
#
CCcam Support Forum
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!
