Sbox as a server upgrade (not emu) by evocamd.
I commented a possible configuration for processing EMMs using sbox as server only, not as emu, using evocamd. Vale do both locally and remotely. Once you take the next revision EDK understand that doing this locally becomes meaningless, but it is useful to remote servers if (linux).
Sbox is about connecting with cccam cccam as always to send him the ECMs (see for cccam), and another user to send the EMMs evocamd him. (sbox client will evocamd)
In the example all was in the same deco, for doing so in remote simply change the ip and ready:
Well we miss in the EMMs sbox.conf (logical not?)
Code:
As users have to create a user for evocamd, with permission to send EMMs:
Okay now for evocamd. Installing evocamd_2.17 in deco. The camd_cfg not put mu integer that is long, but attached to the post. The point is:
Okay now newcamd-client:
In case you want to send a remote server, instead of [127.0.0.1] the ip or dyndns account, we want to update
Since this. So when we started evocamd sbox passes the data from the card:
And when comes an S or U EMM_G it sends sbox, which processes it perfectly.
A couple of comments:
Once started evocamd must complete at least one channel for change to Logear coemience emms
If you restart without restarting sbox evocamd, this does not find out and stop sending emms
Not affected much, for the case of the 3 local emus have sbox + cccam + evocamd in the script and goes, and in case you want to remotely actaulizar in the deco has evocamd programs with cron to restart every 5 evocamd -6 hours, if the server is to reboot, and go.
Both the 142 and with the 180 purchase and upgrade without makeshift. Not if you go with the gray, as you say.
Subo sample configuration, with a little reading this and can adapt to any situation and so image.
Gracias a labascal
I commented a possible configuration for processing EMMs using sbox as server only, not as emu, using evocamd. Vale do both locally and remotely. Once you take the next revision EDK understand that doing this locally becomes meaningless, but it is useful to remote servers if (linux).
Sbox is about connecting with cccam cccam as always to send him the ECMs (see for cccam), and another user to send the EMMs evocamd him. (sbox client will evocamd)
In the example all was in the same deco, for doing so in remote simply change the ip and ready:
Well we miss in the EMMs sbox.conf (logical not?)
Code:
Code:
[2D2D2D2D] # Nagra2 camid
rsa =... # Rsa "n" from this card (like newcs)
boxkey =... # Boxkey from this card
emm = 0 # 0 = accept all 1 = block 2 = block emmu emms 4 = block emmg
Portlist = 1 # use Portlist or not
portlistpath = / var /****/ port.list # path from port.list
Code:
[slot0]
user = cccam
pass = cccam
au = 0
[B][slot0]
user = [COLOR="#ff0000"]emm[/COLOR]
pass = [COLOR="Red"]emms[/COLOR] [/B]
au = 1
Code:
# AU
# 00 is ignored (default)
# 01 enable AU
# 02 AU Auto
A: (01)
# Key update
# 01 update only new ****, default setting
# 02 update all **** (used for valid PMK checking)
U: (01)
# Share Mode
# 00 Pure emu
# 01 Pure emu
# 02 Pure emu
# 03 alle network clients
# 04 newcamd share
# 05 radegast share
# 06 camd35 share (not in use)
G: (04)
Okay now newcamd-client:
Code:
[127.0.0.1]
port = 11,001
key = 01 02 03 04 05 06 07 08 09 10 11 12 13 14
username = [COLOR="#ff0000"]emm [/COLOR]
password = [COLOR="#ff0000"]emms[/COLOR]
Since this. So when we started evocamd sbox passes the data from the card:
Code:
================================================== ==========
(compiled Dec 31 2007 14:44:44)
styled by TBT Team, Next Level Christmas special version (ALL | Im a HD DVD supporter, and you? |)
================================================== ==========
~> Kaid: ****
[EMM ENABLED]
Cardno: 2D2D2D2D
prov: ****: 2D2D2D2D
prov: ****: 2D2D2D2D
prov: ****: 2D2D2D2D
Got CaID **** from 127.0.0.1, TCP / IP Port: 11001
Code:
[Card client] emm send to server OK!
A couple of comments:
Once started evocamd must complete at least one channel for change to Logear coemience emms
If you restart without restarting sbox evocamd, this does not find out and stop sending emms
Not affected much, for the case of the 3 local emus have sbox + cccam + evocamd in the script and goes, and in case you want to remotely actaulizar in the deco has evocamd programs with cron to restart every 5 evocamd -6 hours, if the server is to reboot, and go.
Both the 142 and with the 180 purchase and upgrade without makeshift. Not if you go with the gray, as you say.
Subo sample configuration, with a little reading this and can adapt to any situation and so image.
Gracias a labascal