Kaffeine Forum :: View topic - Sasc-ng and CCcam.

Kaffeine Forum :: View topic - Sasc-ng and CCcam.: "Someone sent me a private message asking my help about getting CCcam to work with Sasc-ng i remember i had a
very frustrating problem to get CCcam to replay Sasc-ng requests although CCcam protocol support was added to sasc-ng.
so i thought i would post here for everyone who is having the same issue.

To install sasc-ng take a look at my other post here : http://hftom.free.fr/phpBB2/viewtopic.php?t=532
I will be using vdr-sc HG Repositor from this URL http://85.17.209.13:6100/sc for this post.
to download it just run this command in your shell
Code:

hg clone http://85.17.209.13:6100/sc

After installing sasc-ng as mentioned in the above post. cd to ./sc/contrib/ in the folder downloaded from the repositer
above. then run this command :

Code:

make


if everything worked as it suppose to you will get a library cccam_ca.so
cp that library somewhere you are gonna use it from. let's say /usr/local/lib/ for example.

Code:

cp cccam_ca.so /usr/local/lib/


now download latest CCcam version from here : http://www.cccamforum.com/forums/download/index.php?dir=CCcam%20Emus/

in the archive there is gonna be 6 different executable files CCcam.something each one for a different type of processor
a CCcam configuration file CCcam.cfg and a change log file ChangeLog.
for example i have a x86_64 linux machine.
so i will copy CCcam.x86_64 to one of my binary directories. let's say /usr/local/bin/

Code:

cp CCcam.x86_64 /usr/local/CCcam


copy the CCcam configuration file to /var/etc/ that's where CCcam will search for it you can use any other directory.
unless you specified the configuration file path with the CCcam switch -C .
Code:

cp CCcam.cfg /var/etc/


Download CCcam.channelinfo and CCcam.providers from the following links:
http://www.cccamforum.com/forums/download/files/CCcam%20Tools/CCcam.channelinfo
http://www.cccamforum.com/forums/download/files/CCcam%20Tools/CCcam.providers

copy CCcam.channelinfo CCcam.providers to the same directory where your CCcam.cfg is located normally /var/etc/

if you are gonna use softcam.key or need to use it you will have to download the following files:

http://hacksat.org/deneme6.php?file=SoftCam.Key
http://hacksat.org/deneme6.php?file=AutoRoll.Key
http://hacksat.org/deneme6.php?file=constant.cw

then copy the three of them to the directory /var/keys/ that's where CCcam will them from.

now you can start CCcam with the following command

Code:

LD_PRELOAD=/usr/local/lib/cccam_ca.so /usr/local/bin/CCcam


or you can use a startup script like this one i wrote.

Code:

#!/bin/sh
#
start()
{
if ps -C CCcam > /dev/null
then
echo -e 'CCcam already running\n'
exit
fi
rm /tmp/.CCcam.nodeid > /dev/null
rm /tmp/camd.socket > /dev/null
sleep 2
echo -e 'Starting cccam.\n'
LD_PRELOAD=/usr/local/lib/cccam_ca.so /usr/local/bin/CCcam $1
}

stop()
{
echo -e 'Stopping cccam.\n'
killall CCcam
rm /tmp/.CCcam.nodeid
rm /tmp/camd.socket
}

case $1 in
start )
start
;;
stop )
stop
;;
restart )
echo -e 'restarting cccam.\n'
stop
sleep 1
start
;;
nodaemon )
start -d
;;
* )
echo -e 'Usage `basename $0` {start | stop | restart | nodaemon }\n'
;;
esac




you can customize it to fit your need depending on which Linux distribution you are using.

now let's add our newly installed CCcam server to Sasc-ng card client configuration file. and here it comes the tricky part.
depending on what directory you have chosen for your sasc-ng --cam-dir option.
you should have a file named cardclient.conf there.
to connect your sasc-ng to your newly installed CCcam. add the following like the file cardclient.conf mentioned before.

Code:

cccam:127.0.0.1:9000:0/ffff:/tmp/camd.socket

now you will notice that your CCcam doesn't answer your sasc-ng requests or sasc-ng doesn't send the proper requests
to solve this problem you have to specify the provider you are gonna decrypt. to do so open the CCcam.providers file you have
installed before and search for the provider name you need to decrypt for example let's say we are gonna decrypt Cyfra+
there is a line like this 01000065 '[S2] Cyfra+ (13E)[Full]' in the file CCcam.providers what we need is the hexadecimal
eight characters number 01000065 we will split it into two parts each one with four characters like this 0100 and 0065
now let's add it to our sasc-ng cardclient.conf configuration file. which will now become like this :
Code:

cccam:127.0.0.1:9000:0/ffff:0100/ffff:0065/ffff:/tmp/camd.socket

you can add as many providers as you need just make sure you will do the same thing for each provider here is the configuration i'm using for my CCcam server in the cardclient.conf file.
Code:

cccam:127.0.0.1:9000:0/ffff,0100/ffff,0604/ffff,0500/ffff,1702/ffff,1815/ffff,0d02/ffff,0919/ffff,1801/ffff,2111/ffff,2011/ffff,0000/ffff,0D03/ffff,0D00/ffff,0030/ffff,0091/ffff:/tmp/camd.socket

After you make any changes to the cardclient.conf file you have to restart your sasc-ng to apply them.The only thing left that i didn't cover in this post is how to configure CCcam to connect to your Cams if you have any. I don't have any Cams because i use CCcam just for softcam so i can't give you any details about how to do that but i think there should alot of other tutorials online about how to do that.

- Sent using Google Toolbar"

Sasc-ng and CCcam

Someone sent me a private message asking my help about getting CCcam to work with Sasc-ng i remember i had a
very frustrating problem to get CCcam to replay Sasc-ng requests although CCcam protocol support was added to sasc-ng.
so i thought i would post here for everyone who is having the same issue.

To install sasc-ng take a look at my other post here : http://hftom.free.fr/phpBB2/viewtopic.php?t=532
I will be using vdr-sc HG Repositor from this URL http://85.17.209.13:6100/sc for this post.
to download it just run this command in your shell

Code:

hg clone http://85.17.209.13:6100/sc

After installing sasc-ng as mentioned in the above post. cd to ./sc/contrib/ in the folder downloaded from the repositer
above. then run this command :

Code:

make

if everything worked as it suppose to you will get a library cccam_ca.so
cp that library somewhere you are gonna use it from. let's say /usr/local/lib/ for example.

Code:

cp cccam_ca.so /usr/local/lib/

now download latest CCcam version from here : http://www.cccamforum.com/forums/download/index.php?dir=CCcam%20Emus/

in the archive there is gonna be 6 different executable files CCcam.something each one for a different type of processor
a CCcam configuration file CCcam.cfg and a change log file ChangeLog.
for example i have a x86_64 linux machine.
so i will copy CCcam.x86_64 to one of my binary directories. let's say /usr/local/bin/

Code:

cp CCcam.x86_64 /usr/local/CCcam

copy the CCcam configuration file to /var/etc/ that's where CCcam will search for it you can use any other directory.
unless you specified the configuration file path with the CCcam switch -C .

Code:

cp CCcam.cfg /var/etc/

Download CCcam.channelinfo and CCcam.providers from the following links:
http://www.cccamforum.com/forums/download/files/CCcam%20Tools/CCcam.channelinfo
http://www.cccamforum.com/forums/download/files/CCcam%20Tools/CCcam.providers

copy CCcam.channelinfo CCcam.providers to the same directory where your CCcam.cfg is located normally /var/etc/

if you are gonna use softcam.key or need to use it you will have to download the following files:

http://hacksat.org/deneme6.php?file=SoftCam.Key
http://hacksat.org/deneme6.php?file=AutoRoll.Key
http://hacksat.org/deneme6.php?file=constant.cw

then copy the three of them to the directory /var/keys/ that's where CCcam will them from.

now you can start CCcam with the following command

Code:

LD_PRELOAD=/usr/local/lib/cccam_ca.so /usr/local/bin/CCcam

or you can use a startup script like this one i wrote.

Code:

#!/bin/sh # start() { if ps -C CCcam > /dev/null then echo -e "CCcam already running\n" exit fi rm /tmp/.CCcam.nodeid > /dev/null rm /tmp/camd.socket > /dev/null sleep 2 echo -e "Starting cccam.\n" LD_PRELOAD=/usr/local/lib/cccam_ca.so /usr/local/bin/CCcam $1 } stop() { echo -e "Stopping cccam.\n" killall CCcam rm /tmp/.CCcam.nodeid rm /tmp/camd.socket } case $1 in start ) start ;; stop ) stop ;; restart ) echo -e "restarting cccam.\n" stop sleep 1 start ;; nodaemon ) start -d ;; * ) echo -e "Usage `basename $0` {start | stop | restart | nodaemon }\n" ;; esac

you can customize it to fit your need depending on which Linux distribution you are using.

now let's add our newly installed CCcam server to Sasc-ng card client configuration file. and here it comes the tricky part.
depending on what directory you have chosen for your sasc-ng --cam-dir option.
you should have a file named cardclient.conf there.
to connect your sasc-ng to your newly installed CCcam. add the following like the file cardclient.conf mentioned before.

Code:

cccam:127.0.0.1:9000:0/ffff:/tmp/camd.socket

now you will notice that your CCcam doesn't answer your sasc-ng requests or sasc-ng doesn't send the proper requests
to solve this problem you have to specify the provider you are gonna decrypt. to do so open the CCcam.providers file you have
installed before and search for the provider name you need to decrypt for example let's say we are gonna decrypt Cyfra+
there is a line like this 01000065 "[S2] Cyfra+ (13E)[Full]" in the file CCcam.providers what we need is the hexadecimal
eight characters number 01000065 we will split it into two parts each one with four characters like this 0100 and 0065
now let's add it to our sasc-ng cardclient.conf configuration file. which will now become like this :

Code:

cccam:127.0.0.1:9000:0/ffff:0100/ffff:0065/ffff:/tmp/camd.socket

you can add as many providers as you need just make sure you will do the same thing for each provider here is the configuration i'm using for my CCcam server in the cardclient.conf file.

Code:

cccam:127.0.0.1:9000:0/ffff,0100/ffff,0604/ffff,0500/ffff,1702/ffff,1815/ffff,0d02/ffff,0919/ffff,1801/ffff,2111/ffff,2011/ffff,0000/ffff,0D03/ffff,0D00/ffff,0030/ffff,0091/ffff:/tmp/camd.socket

After you make any changes to the cardclient.conf file you have to restart your sasc-ng to apply them.The only thing left that i didn't cover in this post is how to configure CCcam to connect to your Cams if you have any. I don't have any Cams because i use CCcam just for softcam so i can't give you any details about how to do that but i think there should alot of other tutorials online about how to do that.

RouterTech • View topic - Allow WOL through Router

RouterTech • View topic - Allow WOL through Router

I setup my speedtouch 780 to accept/forward WOL packest to my Home PC from Work..

I believe that the BT HomeHub is a speedtouch 7G and configuring it is basically the same, although I can't confim it.

From memory All I had to do was
Telnet into the Speedtouch.
and at CLI execute

:ip arpdelete intf=LocalNetwork ip= hwaddr=

:ip arpadd intf=LocalNetwork ip= hwaddr=

This creates a static arp entry otherwise the Speedtouch seams to forget where the PC is conncted.

then execute

:service rule add name="Wake on LAN" protocol=tcp portrange=7-9
:service rule add name="Wake on LAN" protocol=udp portrange=7-9
:service assign name="Wake on LAN" host= log=disabled

These last 3 can be setup from the web interface "Game & Application Sharing" if prefered.

Details on how to send the WOL packet can be found here
http://www.depicus.com/wake-on-lan/woli.aspx

The PC will also need to be setup with a static IP Address or to always get the same address from DHCP.

Hope this helps

Karmic no /dev/dvb/adapter0

The problem was solved by creating a /etc/udev/rules.d/50-udev.rules containing:

Installing XBMC and Ubuntu 9.10 (Karmic Koala) desktop on Acer Aspire Revo 3610 - XBMC Community Forum

Installing XBMC and Ubuntu 9.10 (Karmic Koala) desktop on Acer Aspire Revo 3610 - XBMC Community Forum

Upgrade Alsa

cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.20.

sudo /etc/init.d/alsa-utils stop 

cd ~
rm -rf ~/alsa* ~/.pulse*


sudo apt-get update
sudo apt-get upgrade

sudo apt-get install wget build-essential linux-headers-`uname -r`
wget ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.21.tar.bz2
tar -xf alsa-driver-1.0.21.tar.bz2
cd alsa-driver-1.0.21
./configure
make
sudo make install
sudo ./snddevices
sudo apt-get install alsa-utils
#Reboot Here!!!
alsamixer
sudo alsactl store

other link is

http://monespaceperso.org/blog-en/2009/10/29/upgrade-alsa-1-0-21-on-ubuntu-karmic-koala-9-10/

Multimedia Keys - Gentoo Linux Wiki

Multimedia Keys - Gentoo Linux Wiki