Hop 4 & Hop 5 still being accepted

[ITS A SCAM !]

Hello,
Even though i place { 0:0:3 } after the peers c line i still get Hops 4 & 5.. I have tried looking to see if i have made a typing error, but i am unable to solve it .....ant ideas ??

 

[B16MCC]

In order to use filtering you must insert yes or no at the end of the C line before the filters.

EG :- C: dyndns.org 12000 user pass no { 0:0:3 }

The yes or no refers to the use of EMM's.

 

[Burnham Beech]

Whenever I am stuck on CCcam it's worth re-reading the all the intructions in the default cccam.cfg file. It's amazing how often the answer is there already. Here is the relevant section:

# add yes on end to use friends emus (non public private key/emu,etc...),
# optional limits just like F line, but for incoming shares (ignore shares more than 'uphops' away)
#
#C: <hostname> <port> <username> <password> <wantemus> ( { caid:id(:uphops), caid:id(:uphops), ... } )
#
#note: if {} limits are added, <wantemus> cannot be omitted. Use either yes or no.

 

[ITS A SCAM !]

Hello, The end of every C line i have in my cfg file exacly the same....All 60 of them end with NO { 0:0:3 }
I have tried this line with many different alterations to you end of it...but i still keep getting Hop 4 & 5 from just one particular person..it cannot be possible that this person CAN force Hop 4 & 5 ??

 

[ITS A SCAM !]

Ok problem solved......My Bad.....There was 2 lines for the same person !! Don't ask me how there was 2, but i have deleted one and it now seems ok.......many thanks to whole who took time out to help

 

[J700]

It's entirely up to the client to report how many hops away the query is coming from. With a small patch to CCcam the client could change the hop reported to the server to something else.