cant get incubus server work

[mrlezbp]

Guys,

I need help setting up the new incubus server, ive tried everything, but cant get any of my partners connected. all ports are forwarded to the STB but still cant make it work

 

[api]

Guys,

I need help setting up the new incubus server, ive tried everything, but cant get any of my partners connected. all ports are forwarded to the STB but still cant make it work

README':
"you can use the incubusCamd as a server):
you can also reshare your local card if connected as newcamd/radegast..."

 

[mrlezbp]

well here is my config then

background_execution=0
debug_level=3
log_to_console=1
log_to_file=0
logfile_name=/var/bin/incubusCamd.log
softcamfile_name=/var/keys/SoftCam.Key
priofile_name=/var/keys/incubusCamd.prio
on_screen_messages_show=0
on_screen_messages_username=root
on_screen_messages_password=
on_screen_messages_key_update=0
on_screen_messages_wait_for_key_update=0
on_screen_messages_ecm=0
on_screen_messages_emm=0
console_logs_broadcast=0
console_logs_broadcast_port=666
webif=1
webif_port=668
clients_port=14000
#minimum_clients_version=2.1.3
extra_emm_level=0

# Option to set global share limits
#
# global_limits={ caid:iddownhops), caid:iddownhops), ... }
#
#example:
#
#global_limits={ 0100:000080, 0622:000000:1, 0500:000000:2 }
#
# all users get no 0100:000080.
# and our 0622:000000 cards only for themself (1 hop down),
# and 0500 cards for themself plus one additional hop down.
# global limits are overridden by client specific limits (see [Clients] section)


[Prov:000000:CaID:0000]
check_priority=cs,emu,card
cs_protocol_order=cccam,cccam
process_emms_on_cs_mode=0
process_emm_g=0
process_emm_s=0
process_emm_u=0
seca3_handler=0

# This is the ChannelID wich will be used as first value
# on irdeto channels. Value "-1" means no preferred channel id will be used.
# You can use more than one pref chid, you have to separe them with a comma ',' (see example 2).
# The value is expressed as 4 digits hex value (2 bytes). Automatic change will be done.
# example: chid=0015
# example 2: chid=0015,002A
#chid=-1

# This is the max value wich will be used as comparing value
# for card's uphops. If a less or equal uphops will be found then the card will be used,
# the cards with greater uphops value will be ignored.
# The value is expressed as decimal value, by default a value equal to 5 is set by the cam
#max_check_uphops=5

[Prov:000000:CaID:0D02]
check_priority=card,card,cs
cs_protocol_order=newcamd,cccam,
process_emms_on_cs_mode=0
process_emm_g=0
process_emm_s=0
process_emm_u=0
seca3_handler=0
chid=-1
max_check_uphops=5

########################### servers configuration ############################
[Servers]
#
# This is the section for the multi-server configuration.
#
# URL of card-server to use, formats are as follows:
#
# newcamd://<username_31>:<password_31>@<hostname>:<port>:<caid_4>:<prov_id_6>/<des_key_14>/[EMM]/<nr_of_hops_away>
# aroureos://@<hostname>:<port>:<caid_4>:<prov_id_6>/[EMM]/<nr_of_hops_away>
# radegast://@<hostname>:<port>:<caid_4>:<prov_id_6>/[EMM]/<nr_of_hops_away>
# camd33://<username_10>:<password_10>@<hostname>:<port>:<caid_4>:<prov_id_6>/[aes_key_16]/[EMM]/<nr_of_hops_away>
# camd35://<username_32>:<password_32>@<hostname>:<port>:<caid_4>:<prov_id_6>/[EMM]/<nr_of_hops_away>
# gbox://<localhost>:<localport>:<password_8>@<peer_address>:<peer_port>:<peer_pass_8>/[EMM]
#
# cccam://<username_20>:<password_32>@<hostname>:<port>/[receive_emu_shared]/[EMM]
# where [receive_emu_shared] should assume value "yes" (without quotes, if you like to receive emus data shared by the server) or "no" (this is assumed by default)
# and it's an optional parameter.
#
# where [EMM] should assume value "EMM" (without quotes, if you like to send EMMs data to the server) or just do not add anything if you do not want EMM
#
# where <nr_of_hops_away> is the number of hopdown you want to share your card: by default is set to 1 (only one share down enabled from you)
#
# NOTE: The "EMM" suffix is optional and tells the card-server client whether
# to send EMM's to the card-server or not. Enabling or disabling this only
# has effect if the card-server is configured to accept emms from this client.
#
# NOTE 2: You can set value 0000 for caid and value 000000 for provider id on newcamd server if you want an all codifies working server
# or simply if you don't know wich value to set on, just put 0 value
#
# i.e:
#
card_server_url=cccam://???:???@???:12000
card_server_url=cccam://????:????@???????:12000
#card_server_url=newcamd://pkt0[email protected]:10000:0000:000000/0102030405060708091011121314
card_server_url=newcamd://pkt1[email protected]:10001:0D02:000000/0102030405060708091011121314

#card_server_url=cccam://username[email protected]:15000
#card_server_url=gbox://yourname.dyndns.org:6666[email protected]:6666eer_pass
#card_server_url=cccam://usernameassword@hostnameort/no # cccam without emu shared
#card_server_url=cccam://usernameassword@hostnameort/yes # cccam with emu shared
#card_server_url=cccam://usernameassword@hostnameort/yes/EMM # cccam with emu shared and with EMM enabled
#card_server_url=gbox://192.168.1.24:5555[email protected]:4444eer_pass
#card_server_url=newcamd://username[email protected]:10550:0500:028800/0102030405060708091011121314
#card_server_url=radegast://@192.168.0.100:10550:0100:000065
#card_server_url=aroureos://@yourhostname.dyndns.org:10666:0500:007C00
#card_server_url=camd35://username[email protected]:14150:0603:000000
#card_server_url=camd33://username[email protected]:10550:0603:000000 # cam33 without AES encryption
#card_server_url=camd33://username[email protected]:10500:0604:000000/01020304050607080910111213141516 # cam33 with AES encryption
#card_server_url=newcamd://username[email protected]:10550:0500:028800/0102030405060708091011121314/EMM/2 # EMM is enabled for this server and will share this card 2 hops away from us
#card_server_url=newcamd://username[email protected]:10551:0000:000000/0102030405060708091011121314/EMM/0 # this server will be used with all codifies because of value 0 for caid and provid, no share for this card

########################### clients configuration ############################
[Clients]

card_client_url=cccam://userass@

card_client_url=cccam://userass/yes/yes/2


#
# This is the section for the multi-client configuration.
# The port used to make other clients connected is declared in the general section like "clients_port".
#
# URL of card-client to use, formats are as follows:
#
# cccam://<username_20>:<password_32>@[hostname]/[allow_emu_shared]/[receive_EMM]/[uphops] { caid:iddownhops), caid:iddownhops), ... } { caid:id:sid, caid:id:sid, ... } { begintime-endtime, ... }
# where [hostname] should assume value of your client ip address if you want to make limitation on address connections for an account
# where [allow_emu_shared] should assume value "yes" (without quotes, if you like to share emus data with clients, this is assumed by default) or "no"
# where [receive_EMM] should assume value "yes" (without quotes, if you like to receive EMM data from clients, this is assumed by default) or "no"
# where [uphops] is the max number of uphops of cards that can be shared to the client
# 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
#
# i.e:



#card_client_url=cccam://username[email protected]/no # this client can not receive emu but can send emm to us
#card_client_url=cccam://username[email protected]/no/no # this client can not receiver emu and can't send emm to us
#card_client_url=cccam://username[email protected]/no/yes # this client can not receive emu but can send emm to us
#card_client_url=cccam://username[email protected]/yes/no # this client can receive emu but can't send emm to us
#card_client_url=cccam://username[email protected] # this client will receive emu and can send emm to us
#card_client_url=cccam://usernameassword@ # this client will receive emu and can send emm to us and has no restriction on the hostname address, previous examples have all restriction on one address
#card_client_url=cccam://usernameassword@/yes/no # this client will receive emu but can't send emm to us and has no restriction on the hostname address
#card_client_url=cccam://usernameassword@/no/no/2 # this client can't receive emu and can't send emm to us and has no restriction on the hostname address and gets all our shares at max 2 hops from us

#card_client_url=cccam://usernameassword@/no/no/2 { 0100:000080, 0622:000000:1, 0500:000000:2 }
# this client can't receive emu and can't send emm to us and has no restriction on the hostname address and gets all our shares at max 2 hops from us
# gets no 0100:000080 and our 0622:000000 cards only for himself (1 hop down),
# and 0500 cards for himself plus one additional hop down.

#card_client_url=cccam://usernameassword@/no/no/2 { 0:0:3, 0100:000080:1 }
# this client can't receive emu and can't send emm to us and has no restriction on the hostname address and gets all our shares at max 2 hops from us
# 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.

#card_client_url=cccam://usernameassword@/no/no/2 { 0:0:3, 0100:000080:1 } { 0100:000080:15df }
# this client can't receive emu and can't send emm to us and has no restriction on the hostname address and gets all our shares at max 2 hops from us
# 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 is also not allowed to view channel 0100:000080:15df

#card_client_url=cccam://usernameassword@/no/no/2 { } { } { 12:00-17:00, 19:00-20:00 }
# this client can't receive emu and can't send emm to us and has no restriction on the hostname address and gets all our shares at max 2 hops from us
# 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

########################### CaIDs tunneling configuration ############################
[CaIDTunnel]

1833:1702:000000:0080 #History HD
1833:1702:000000:0081 #Sky Sport HD
1833:1702:000000:0082 #Discovery HD
1833:1702:000000:0083 #Sky Cinema HD
1833:1702:000000:0084 #EuroSport HD
1833:1702:000000:007E #Disney Cinemagic HD
1833:1702:000000:007F #National Geography HD

#
# All values are in hex notation
# In this file you can configure what CAIDs/PIDs incubusCamd should tunnel to another CAID
#
# situation 1: this caid, all idents, on all channels will use the tunnel_caid
# caid:tunnel_caid
#
# situation 2: this caid/ident pair will use the tunnel_caid
# caid:tunnel_caid:ident
#
# situation 3: this caid/ident pair, on channel 'sid' will use the tunnel_caid
# caid:tunnel_caid:ident:sid
#
# i.e:
#
#1833:1702:000000:0082 # this one should tunnel premiereHD nagra3 into betacrypt cards
#1833:1702:000000:0081 # this one should tunnel premiereHD nagra3 into betacrypt cards

 

[triplex1]

 

[mrlezbp]

i deleted the spaces, what do u mean by home cs and net cs ?

 

[mrlezbp]

this is how the server / client part looks now

[Servers]
card_server_url=newcamd://pkt1[email protected]:10001:0D02:000000/0102030405060708091011121314
card_server_url=cccam://username[email protected]:12000

[Clients]
card_client_url=cccam://user[email protected]/yes/yes

I can connect his server but he can not connect mine, incubus web interface shows that my server is running but nobody is connected.

now what ? :S

 

[triplex1]

 

[mrlezbp]

I can connect my card reader and my cccam partners as client, the problem is that THEY can NOT connect MY server.

 

[triplex1]

Sorry but I can not help you more in this matter because I do not know what works and what you want to do.

 

[mrlezbp]

:S thx anyway for your effort

I have a U#P Dixrect Card in my newcs which i can watch for myself and i want to shate it with my friend, who is sharing his Hello HD card with me

 

[Philphil]

Try Oscam it does all this and works!

 

[mrlezbp]

use it as cccam server and client ?

really ?

 

[jamie-warez]

yea oscam works great as both client and server.......

incubus server is still bugy at moment and only works with some cards..

Oscam is much more stable and supports most cards...