nginx现在的最新开发版本是0.8.40 ,一些网友就是喜欢最新版本,都问我的LNMP一键安装包怎么升级 Nginx 到最新版本 ,现在,只要你简单的执行几句命令,就可以将 Nginx 升级到最新版本 ,只适合我的LNMP一键安装包,如果你知道你的LNMP安装启动的路径,也可以用这个方法的.

首先下最新版本,解压缩编译

一定不要make install !!!!!

接着备份原来的 nginx 文件

然后复制编译好的 nginx 文件到/usr/local/nginx/sbin/nginx

检测nginx文件配置

直接重启Nginx

或者

效果:http://vps.imcat.in/
BTW

如果需要更改header信息的话,可以修改nginx.h文件

找到

上面的版本号和nginx可以自己修改,例如:

BTW
关闭debug模式可以减少nginx文件的大小

找到这行,注释掉

这是现在最好的下载网盘资源工具了： １、可以自动更改IP，免掉你下载等待的时间； ２、验证码自动识别，免除你需要守候的问题。 只需要一次性复制所有连接到剪贴板，剩下的从下载到解压它可以一条龙帮你完全搞定。 呵呵唯一的要求是需要安装JAVA支持，需要使用这个工具的朋友可以 到http://www.java.com/zh_CN/download/index.jsp下载安装，装过后就可以使用这个工具了。 下面讲一下安装和设置的过程（具体到不同的版本，可能会稍有不同）： 1、解压以后，运行目录中JDownloader.exe， 2、选择安装的语言 这里可以选择中文Chinese(Simplified)，找到它单击 选择语言后的界面，在此也可设置默认下载目录，单击“确定” 3、在这个界面会安装一个插件，点“确定” 再“确定” 4、单击“确定”，添加信息到注册表 再“确定” 5、之后就会自动启动JD了，此时会进行软件更新，每次”确定”即可。请耐心的等一会，或去喝杯茶…… 下面是下载更新界面 6、更新完毕以后，需对软件进行一点基本的设置（见下图），点击“设置”选项卡，打开基本设置界面，根据需要进行一些基本的设置。如下图： 下面以最常用的网盘rapidshare为例子，进行设置，具体见下图： 设置完毕后，就可以使用了（当然，还有好多功能等待我们去挖掘） 比如：软件可以对压缩包自动解压： 如果压缩包有密码，在下图所示位置填上解压密码 下面讲解一下工具的基本使用： 1、启动JDownloader后，找到需要下载的国外网盘资源链接地址，右键复制，就会自动弹出“添加”下载界面，如果未弹出，也可按下图进行操作。 下面是弹出的添加下载链接界面： 2、添加完成下载链接后的界面 3、选择需要下载的资源后，单击“开始”按钮即可

CentOS 5.5 1CD x86_64 (20100516)版
CentOS-5.5-x86_64-1CD_20100516.iso

CentOS 5.5 1CD i386 (20100515)版
CentOS-5.5-i386-1CD_20100515.iso

CentOS 5.4 1CD i386 (20100110)版
CentOS-5.4-i386-1CD_20100110.iso

CentOS 5.4 1CD x86_64 (20091102)版
CentOS-5.4-x86_64-1CD_20091102.iso

CentOS 5.4 1CD i386 (20091024)版
CentOS-5.4-i386-1CD_20091024.iso

CentOS5.3 1CD 20090524版
CentOS5.3_1CD_20090524.iso

CentOS5.3 1CD 20090418版
CentOS_5.3_1CD_20090418.iso

CentOS5.2 1CD
CentCore52_20081209.iso

CentOS5 1CD導入ディスク
CentOS5_one.iso

http://www.srchack.org/index.php?topic=CentOS1CD

系统是Ubuntu 9.04,用root登录,然后操作如下;

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

apt-get remove apahce2 //因为VPS预安装了Apache,所以我先把Apache删了;
apt-get update //然后更新下系统;
apt-get install mysql-server-5.1 //安装MySQL,会提示设置root用户密码;
apt-get install php5-cgi php5-mysql php5-gd //安装PHP
apt-get install cpp gcc g++ make //编译Cherokee所必要的软件;
cd /tmp
wget http://www.cherokee-project.com/cherokee-latest-tarball -O -| tar zxvf - //下载Cherokee到tmp目录
mv cherokee-0.99.31 cherokee  //懒的总是打版本号,所以重命名下;
cd cherokee
./configure –localstatedir=/var –prefix=/usr –sysconfdir=/etc –with-wwwroot=/var/www //基本配置
make //编译;
make install //安装;
cp contrib/cherokee /etc/init.d/cherokee //复制启动脚本;
chmod 755 /etc/init.d/cherokee //更改权限;
/etc/init.d/cherokee start //然后启动Cherokee;
update-rc.d cherokee defaults

启动,停止,重启命令;

1
2
3

/etc/init.d/cherokee start
/etc/init.d/cherokee stop
/etc/init.d/cherokee restart

启动Cherokee的管理面板;

1

cherokee-admin -b

然后用显示的密码登录http://IP:9090

快速安装cherokee

apt-get install cherokee

安裝了ubuntu server版可是apt-get install XXXX 出现E: Couldn't find package XXX
首先执行sudo apt-get update
以更新软件列表

重新启动网络
sudo /etc/init.d/networking restart

安装图形界面：
1.sudo apt-get install xinit
执行这个，会安装一个图形的命令行窗口
(在我的机器上这个步骤完成以后UI就没有任何响应了.我不太了解图形界面在linux上是个什么机制)
2.安装环境管理器
sudo apt-get install gdm
KDE和Xface则分别改为KDM和XDM
3.安装桌面环境
sudo apt-get install ubuntu-desktop


svn在将Ubuntu的语言修改为英文之后，出现错误警告：
svn: warning: cannot set LC_CTYPE locale
svn: warning: environment variable LANG is en_US.UTF-8
svn: warning: please check that your locale name is correct
Type 'svn help' for usage.

解决方法:修改/etc/profile:sudo vi /etc/profile
加入一行：
export LC_ALL=C

执行source /etc/profile
svn就可以正常工作了

安装ftp:
sudo apt-get install vsftpd

转自http://linux2904.blog.163.com/blog/static/109134192201001192534867/
一. samba的安装:

一. samba的安装:
sudo apt-get insall samba
sudo apt-get install smbfs

二. 创建共享目录:
mkdir /home/phinecos/share
sodu chmod 777 /home/phinecos/share

三. 创建Samba配置文件:

1. 保存现有的配置文件
sudo cp /etc/samba/smb.conf /etc/samba/smb.conf.bak

2. 修改现配置文件
sudo gedit /etc/samba/smb.conf

在smb.conf最后添加
[share]
path = /home/phinecos/share
available = yes
browsealbe = yes
public = yes
writable = yes

四. 创建samba帐户
sudo touch /etc/samba/smbpasswd
sudo smbpasswd -a phinecos

然后会要求你输入samba帐户的密码

［如果没有第四步，当你登录时会提示 session setup failed: NT_STATUS_LOGON_FAILURE］

五. 重启samba服务器
sudo /etc/init.d/samba restart

六. 测试
smbclient -L //localhost/share

七，使用
可以到windows下输入ip使用了，在文件夹处输入 "\\" + "Ubuntu机器的ip或主机名" + "\\" + "share"

修改Ubuntu Server的区域语言设置
1.修改/var/lib/locales/supported.d/local的内容为en_US.UTF-8 UTF-8
2.执行sudo locale-gen –purge重生成locale文件
3.修改/etc/default/locale内容为
LANG="en_US.UTF-8"
LANGUAGE="en_US:en"
4.sudo reboot

deb http://mirrors.163.com/ubuntu/ lucid main universe restricted multiverse
deb-src http://mirrors.163.com/ubuntu/ lucid main universe restricted multiverse
deb http://mirrors.163.com/ubuntu/ lucid-security universe main multiverse restricted
deb-src http://mirrors.163.com/ubuntu/ lucid-security universe main multiverse restricted
deb http://mirrors.163.com/ubuntu/ lucid-updates universe main multiverse restricted
deb http://mirrors.163.com/ubuntu/ lucid-proposed universe main multiverse restricted
deb-src http://mirrors.163.com/ubuntu/ lucid-proposed universe main multiverse restricted
deb http://mirrors.163.com/ubuntu/ lucid-backports universe main multiverse restricted
deb-src http://mirrors.163.com/ubuntu/ lucid-backports universe main multiverse restricted
deb-src http://mirrors.163.com/ubuntu/ lucid-updates universe main multiverse restricted

Debian 系统的

Ubuntu 系统的

Centos的

- UPDATED -
Changelog :

Hi,

this set of scripts will help you protect your cccam server against various events (bad command and illegal logins) generated by your peers in order to increase cccam service stability.
The basic idea is to use the linux firewall (iptables) in "realtime" to block cccam traffic for specific peers (ip) based on cccam debug output.

This work was initialy inspired by discussions on this thread "How to solve the disconnecting client issue" and is a partial answer to that specific cccam problem.

Although all of it was designed on a debian standlone cccam server having a local firewall, it should also work if your firewall is on a remote machine on your local network.

The Dreambox setup is still NOT working at the moment and will be discussed at the end of the tutorial.


I have been using the scripts for many months with cccam 2.0.10 / 2.1.0 / 2.1.2. I didn't notice any cccam crashes or problems with peers. My server has 50-70 peers and gets between 30 and 100 bad commands a day but their effect is barely noticeable.

Concerning CCcam 2.1.2, my tests showed increased problems with peers regarding the login process, leading to numerous peer bans and peers disconnections. Something has definitely changed in that cccam version that was not present in cccam < 2.1.2.

I personally reverted to cccam 2.1.0 (you can probably use 2.1.1 safely too) and won't be using 2.1.2, i'll wait for 2.1.3 and see what happens then, i suggest you do the same unless you're satisfied with 2.1.2.

The only advantage i can see with 2.1.2 is that it lets my script ban login floods, i'll work on that feature for cccam < 2.1.2 when i have time, for it is the last missing protection i can think of regarding cccam problems, i also noticed some ecm requests floods but i probably never will filter thoses.

Features :
- block peers based on a specific number of bad commands or slow "cards" commands, for any number of minutes.
- block peers doing "illegal logins" (no account or bad password) for any number of minutes.
- protect cccam accounts or ips from being blocked or give them a different error count.
- filter main log and keep only relevant information (reduce log size) and split logs (monitoring, ecm, logins).
- modify monitoring behaviour, turn on/off firewall blocking or logs without having to restart cccam.
- iptables rules use user defined chains in order to keep your iptables firewall fast, clean and safe.



Prerequires :
- cccam running in debug mode with timestamps (-d -t)
- iptables (optional - can be disabled to use only logs)
- sudo to access iptables for your cccam user, with or without password (optional - sudo can be omitted or use of ssh to manage an external firewall)
- cron to perform iptables flush rules (unban) (optional if iptables is not used)
- bash/sh/ash(/busybox) POSIX shell script (read the dreambox section for more info on the scripting problems with ash/busybox shells) and some basic shell commands cat, echo, cut, grep..



Install :
There's not much to do if you know that your system matches the prerequires above.

Open a command line window and make sure you are running your cccam user.
Put the scripts start.sh config.sh fork.sh monitor.sh iptables.sh, in your cccam directory along with the two "protected_account" "protected_ip" files if you need them.

Make sure the scripts can run on your shell, to do that first find out which shell you are running, there's a great change your linux system has links to simulate the precense of sh or bash but you can check your installed shells with the "whereis" command ("#whereis sh", "#whereis ash"...).
The scripts should be POSIX compatible to run on most shells and are configured to run on ash which is supposed to be faster than sh/bash, with the exception of "fork.sh" which MUST run on sh/bash or any shell that will release terminated child scripts and won't generate zombie processes (defunct).
If you don't want to install or use "ash" you can edit each script and change their top line :

#!/bin/ash

with something matching your shell, like :

#!/bin/bash

You need to edit/copy config.example.sh to config.sh, and make config.sh match your setup, each config line has comments.
Make sure you get the iptables parameters right if you intend to use it.

Be very careful to properly set CCCMODE to match your cccam version !

fork.sh will try to create the necessary directories LOGDIR and WORKDIR (see config.sh), but if for some reason it doesn't work and shows errors, create two subdirectories to put logs and work files, default directories are "logs" and "monitor", path are defined in config.sh and can be set to whatever you'd like :

cd /path/to/cccam
mkdir monitor
mkdir logs
chmod 0775 logs monitor

Make sure the scripts are executable :

chmod +x  start.sh config.sh fork.sh monitor.sh iptables.sh

You can test your iptables setup by running the init command :

./iptables.sh init

iptables init is always run when the fork.sh script starts so you don't actually need to run the init command manually but if your get some errors you will have to fix them.
If you run the init multiple times you will have two errors "iptables: Chain already exists", this is not a problem.

Errors are redirected to you main log file (default "logs/monitor.log") so read it to see if errors appear.

Make sure cccam output looks like this :

12:15:21.499 CCcam: deleting client xx.xx.xxx.xxx(userX), bad command
12:15:21.501 CCcam: deleting client yy.yyy.yyy.yy(userY), read result -1
12:15:27.896 CCcam: 1498 cards --> client yy.yyy.yyy.yy(userY) (took 0.2730 seconds)

you can test that by running cccam in the foreground with :

./CCcam.x86 -d -t -C ./CCcam.cfg

according to cccam --help, the only thing that could be missing is the timestamp. Although i think that -d activates debug mode, not only foreground, and then outputs everything including timpestamps, also overriding cccam config options like DEBUG..


Finally when you're all set you can run cccam with the following command from the cccam directory :

./CCcam.x86 -d -t -C ./CCcam.cfg | ./fork.sh >> /path/to/cccam/logs/monitor.log &

Or use the start.sh script :

./start.sh start

start.sh has to be placed in the same directory as the other scripts and has the following commands "start / stop / restart". It uses regular ps/kill commands so it should be compatible with most systems. And can be used to monitor cccam status and restart it if necessary so you can use the "start" command in your cron to check if cccam has crashed and restart it.


You can then check out the main log with :

tail -n30 -f logs/monitor.log

if everything works fine and you are using the firewall, you have to add a cron command to flush rules when they expire.

*/1 * * * * /path/to/cccam/iptables.sh flush >> /path/to/cccam/logs/monitor.log 2>&1

It will run the iptables flush script every minute and delete rules that have expired (exceeded the ban duration)




Usage :

CCCam 2.1.0/2.1.1 specific :
Those two versions produce a lot more "bad command" events than other versions because some events were renamed as bad commands and were not before, knowing that i'd suggest being a little more tolerant regard the bad command counts and bans if you notice a large number of bans, so you could use settings like the following :

BADDELAY=2               # bad command count duration in minutes
BADCOUNT=5              # bad command count
BADCOUNT_IG=10        # bad command count for protected accounts
BAN=60                      # ban duration in minutes

- CCCMODE : defines your cccam version, important if you want this script to work. Basically there's one mode "0" for all cccam but 2.1.2, and one mode "1" for cccam 2.1.2 and probably upcoming cccam revisions.

- BADCOUNT/BADCOUNT_IG : Knowing that any peer can generate a bad command it is probably not a good idea to ban them at the first one. A good peer will most likely succeed to connect on its second attempt.

- BADDELAY/BAN : bad commands being mostly caused by networking problems (probably very slow lines) it can be something temporary. That's why a 120min ban is usually enough to let the peer try again at a later time when the network conditions have changed. Using a short ban duration like 30min or less will simply let the bad peer send more commands and cripple your cccam server. If you let a peer send more than one bad command then the error count spreads accross the BADDELAY duration.

- BANLOGIN : banning illegal logins is optional but after exchanging Clines with many peers you will find out that a bunch of them won't remove your Cline, getting your cccam server to handle a large amount of login attempts that are all doomed to failure. I just thought that filtering that traffic wouldn't hurt (read bugs and limitations below). It should also protect your server from brute force login attacks although i doubt anyone would try to do such a visible hack.

- LOGUNKNOWN/UKNOWNMAINLOG : are used to help cccam identify accounts that produce some events. LOGUNKNOWN will tell cccam to look for missing account names for the event processed by looking at current work/temp files. In addition, the optional UKNOWNMAINLOG will let cccam look into the main log file, this can be very helpful but can also produce some nasty side effects if your main log is big. So you should make sure to manage (rotate/purge on a daily basis) your main log file if you intend to use that option.

- CARDSDELAY/CARDSBAD : for CCcam 2.0.x-2.1.1 - has no impact on cccam 2.1.2 . That one is a bit more tricky, it tells the monitoring script to interpret "xxxx cards --> client" commands as a bad command based on its duration. I have indeed noticed that peers taking very long time (a few seconds) to receive the cards info will disconnect active peers in the exact same way a bad command does ! Unfortunately i wasn't really able to identify a very precise duration above which diconnections happen so i used a two levels trigger to manage those commands.
CARDSDELAY is the max durations in seconds above which the peer will get a "bad command" added to its log, but it will never trigger a ban action, the trigger will only log the event and when a "real" bad command occurs at a later time then it will count as a bad command. The use of this option is quite restrictive, the default is 4 seconds.
CARDSBAD is the max number of seconds allowed for a "xxxx cards --> client" command, above which a ban action is triggered, as if a real bad command was seen. CARDSBAD is probably more important than CARDSDELAY because it will actively try to ban peers with a very slow network, it will act in the exact same way as a bad command action does, respecting the same ban trigger options (BADCOUNT/BADDELAY). CARDSBAD should always be greater than CARDSDELAY.

- DEBUG : adds some debug data to a $LOGDIR/debug.log file. Probably of no interest to you and should stay disabled (=0).

- Understand that when a peer is banned, he will see your server as offline but you will still be able to connect to his, you know what that means.



Files :
Version 2g : Download
("protected_account" and "protected_ip" are two empty files in which you can put account names and ips, one by line, that you want to "protect" from basic ban rules, see the documentation above for details)



Advanced :
- you can rotate logs, all redirects use "append" (>>).

- no sudo password
you can allow access to iptables for your cccam user (if not root) without sudo password by adding the following line to your "/etc/sudoers" file.

cccamuser   ALL=NOPASSWD:/sbin/iptables

That way you don't have to give a large sudo access to your cccam user and you don't have to put a sudo password in config.sh SUPASS option. The cccam user only requires sudo (root) access to iptables, nothing else.

- using a remote firewall
To use a remote iptables firewall on your local network you will have to replace the sudo command with a ssh one. ssh will try to connect to a remote linux system and execute the iptables command there, then return the command output to the script making the iptables command run exactly as if it was executed localy.
I will guide you quickly through a basic ssh setup but if you don't know what you are doing i'd suggest googling some SSH HOWTOs.

A proper SSH setup would be as follows :
As root, generate a key pair using your "cccam" system's (where cccam monitoring script runs) ssh key generator (ssh-keygen on debian), if any, with the following command :

ssh-keygen -t dsa

When asked for a "passphrase", we won't enter one. Just press enter twice.
That should produce two files in your root home directory : "~/.ssh/id_dsa.pub" and "~/.ssh/id_dsa"

Copy the one line content of the new "~/.ssh/id_dsa.pub" file to the following file on your remote server root user directory : /root/.ssh/authorized_keys2
Depending on your remote server ssh configuration, the file could also be : /root/.ssh/authorized_keys

Now from the cccam system you should be able to ssh your remote server with the command :

ssh root@remoteip

If it asks you to keep a footprint of the new remote system, say yes and it shouldn't bother you with that later, you can "exit" ssh now.
If it worked you can also try accessing the remote iptables firewall with that command, from the cccam system :

ssh root@remoteip /usr/bin/iptables -L -n

It should display your firewall configuration for INPUT OUTPUT FORWARD chains.

Then set the SUDO option in config.sh, like this :

SUDO="/usr/bin/ssh -x root@remoteip"

you can also empty the SUPASS option.

in order to make sure you have a working remote iptables setup you can try running the iptables.sh init command from the cccam system, as follows :

./iptables.sh init

If you run it twice it should display two errors : "iptables: Chain already exists"
That means the cccam chains have been created on your firewall and your setup works.

You can now run cccam as described in the main install guide above.




Known bugs and limitations

- log file output lines may be missplaced, some commands take longer to execute than others and the command output then gets into the log file a bit late, but this is usually something very localized and every line having a timestamp you can always understand what happened.

- some iptables rules may be insterted more than once when a event is not processed fast enough, but it doesn't matter because iptables won't mind and the flush script makes sure duplicate rules are removed.

- reloading your firewall should delete cccam init. you will have to init cccam iptables manually to fix that, with "./iptables.sh init". The good thing is that it should not get the scripts or cccam to crash, so cccam will not really care but you will get lots of errors in your cccam monitoring log..

- banning illegal logins will most certainly ban the new peers you have exchanged Clines with if you haven't activated their accounts before sending them the Clines. You will then have to remove the ban manually or wait for the iptables flush to purge it for you if you haven't banned illegal logins permanently, otherwise new peers may never be able to connect !



Dreambox

Although the scripts should run (with ssh and remote firewall) on dreambox busybox default shell (ash), as they do on my debian stable busybox (1.1.3) binary, the problem i have with that shell, or with ash (dash on debian), is that a parent script will not "release" child scripts that have ended and will then generate tons of zombie processes also known as defunct processes.

If you know a way around that busybox ash shell problem, please contact me, it will most certainly be very helpfull to dreambox users.

I must stress out the fact that running the scripts as they are on the dreambox will work for a short period of time and then stop working when the large number of defunct processes will have filled the system's proc table. It will also most certainly make the dreambox system pretty unstable or even make it crash..

ASUS WL500gP

good instructions on how to install Linux on the Asus;
http://wl500g.info/showthread.php?t=10307

instructions on how to install oscam on the Asus
http://oscam.ump2002.net/board/thread.php?threadid=236

required (attached to previous link)
1. pcsc-lite_155_thE29.ipk
ipkg install pcsc-lite_155_thE29.ipk

2. ccid_1311_thE29.ipk
ipkg install ccid_1311_thE29.ipk

3. oscam-0.99.4svn2178-streamnonusb-oleg-thE29.ipk

save settings;
flashfs save && flashfs commit && flashfs enable && reboot

1. Start pcscd
2. Start oscam (oscam -d)

Open the ports in the router !

Sample configuration files;
/opt/etc/oscam/oscam.user
#
# user configuration
#
[account]
user = user
pwd = password
monlevel = 0
uniq = 1
group = 1
au = reader1
services = services1
ident = 0100:00006a
caid = 0100

/opt/etc/oscam/oscam.server
#
# USB serial reader
[reader]
label = reader1
# pcsc for -a.o. Omnikey 3121 pcsc readers
protocol = pcsc
detect = CD
# /dev/ttyS1 is the second USB port
device = /dev/ttyS1
aeskey = 3BF711000140967070370E6CB6D60000
cardmhz = 357
mhz = 357
group = 1
emmcache = 1,3,2
services = services1
caid = 0100

/opt/etc/oscam/oscam.conf
#
# main configuration
#
[global]
nice = -1
WaitForCards = 1

# logging
pidfile = /var/run/oscam.pid
logfile = /var/log/oscam/oscam.log
usrfile = /var/log/oscam/oscamuser.log
cwlogdir = /var/log/oscam/cw

# monitor
[monitor]
port = 988
aulow = 120
monlevel = 1

[cccam]
port = 12000
version = 2.1.4
build = 1234
reshare = 2

CCcam.x86 -C configfile1
CCcam.x86 -C configfile2

hello all,
i have written/modify a check script for all the CCcam's there are running,
to run every */5 * * * * (ore what time you want)
in crontab for when One of the CCcam should stops.
*/5 * * * * /var/script/MoreCCcamCheck.sh
it checks all CCcam, in this case there are 3 running CCcam's
if you have more or less CCcam
just modify by add or remove a last part ( it shown i blue)
and you may have to change the file/folder/directory (this is my setup)

it writes in /var/cccamlog a cccam.check if CCcam is oke ore when it is restarted

this script works on Ubuntu (maybe someone can test it on Debian, i think
it will work)

I have written this script for the ones who want to use it
feel free to modefy the script, it is finally or hobby to share.
xxxxxx = inlogname from distro

if you want date and time in log ad the red lines.
then you can see when it has restarted and what CCcam it was.
--------------------------------------------------------------------------
MoreCCcamCheck.sh
--------------------------------------------------------------------------
#!/bin/sh
process=`ps auxwww | grep CCcam_1.x86 | grep -v grep | awk '{print $1}'`
if [ -z "$process" ]; then
echo "Couldn't find CCcam_1.x86 running. Show user Nodeid then removing nodeid and Restarting CCcam Server" >> /var/cccamlog/cccam.check
echo && date >> /var/cccamlog/cccam.check
chown xxxxxxx /tmp/.CCcam.nodeid
nohup rm /tmp/.CCcam.nodeid && /usr/local/bin/CCcam_1.x86 -C /var/etc/CCcam_1.cfg
else echo "CCcam_1.x86 is still OK!" >> /var/cccamlog/cccam.check
fi
process=`ps auxwww | grep CCcam_2.x86 | grep -v grep | awk '{print $1}'`
if [ -z "$process" ]; then
echo "Couldn't find CCcam_2.x86 running. Show user Nodeid then removing nodeid and Restarting CCcam Server" >> /var/cccamlog/cccam.check
echo && date >> /var/cccamlog/cccam.check
chown xxxxxxx /tmp/.CCcam.nodeid
nohup rm /tmp/.CCcam.nodeid && /usr/local/bin/CCcam_2.x86 -C /var/etc/CCcam_2.cfg
else echo "CCcam_2.x86 is still OK!" >> /var/cccamlog/cccam.check
fi
process=`ps auxwww | grep CCcam_3.x86 | grep -v grep | awk '{print $1}'`
if [ -z "$process" ]; then
echo "Couldn't find CCcam_3.x86 running. Show user Nodeid then removing nodeid and Restarting CCcam Server" >> /var/cccamlog/cccam.check
echo && date >> /var/cccamlog/cccam.check
chown xxxxxxx /tmp/.CCcam.nodeid
nohup rm /tmp/.CCcam.nodeid && /usr/local/bin/CCcam_3.x86 -C /var/etc/CCcam_3.cfg
else echo "CCcam_3.x86 is still OK!" >> /var/cccamlog/cccam.check
fi

for all who like the post feel free to hit the thanks button.

youknowhoo

(10-October-2009 20:09)
and a config update script it is written by CC_Share but i modified it a little.
the script works great.
you can use it also for 1 config as i do, you only have to cut the blue part.
and rename the FILE & CONFIGOLD
--------------------------------------------------------------------------
MoreConfigUpdate.sh
--------------------------------------------------------------------------
#!/bin/bash
#Script to process new config and backup old one
#Script designed and written by CC_Share and modified by Youknowhoo
SOURCE=/var/config
TARGET=/var/etc
FILE=CCcam_1.cfg
BACKUPDIR=/var/backup
CONFIGOLD=CCcam_1.old
if test -f $SOURCE/$FILE ; then
echo "New Config Present"
if test -d $BACKUPDIR ; then
if test -f $BACKUPDIR/$CONFIGOLD ; then
echo "Removing OLD config file from backup directory"
rm $BACKUPDIR/$CONFIGOLD
else
echo "No OLD config to remove."
fi
if test -f $BACKUPDIR/$FILE ; then
echo "Renaming Backup to old config"
cp $BACKUPDIR/$FILE $BACKUPDIR/$CONFIGOLD
rm $BACKUPDIR/$FILE
else
echo "No Backupfile present yet"
fi
if test -f $TARGET/$FILE ; then
echo "Copying Original config to Backup directory"
cp $TARGET/$FILE $BACKUPDIR
rm $TARGET/$FILE
else
echo "No Original Config File Present!?!?"
fi
else
echo "Backup directory does not exist."
echo "making new directory"
mkdir $BACKUPDIR
if test -f $TARGET/$FILE ; then
echo "Copying Original config to Backup directory"
cp $TARGET/$FILE $BACKUPDIR
else
echo "No Original Config File Present!?!?"
fi
fi
echo "Moving New config file to "$TARGET
cp $SOURCE/$FILE $TARGET
rm $SOURCE/$FILE
else
echo "No New Config present, Nothing to process"
fi
SOURCE=/var/config
TARGET=/var/etc
FILE=CCcam_2.cfg
BACKUPDIR=/var/backup
CONFIGOLD=CCcam_2.old
if test -f $SOURCE/$FILE ; then
echo "New Config Present"
if test -d $BACKUPDIR ; then
if test -f $BACKUPDIR/$CONFIGOLD ; then
echo "Removing OLD config file from backup directory"
rm $BACKUPDIR/$CONFIGOLD
else
echo "No OLD config to remove."
fi
if test -f $BACKUPDIR/$FILE ; then
echo "Renaming Backup to old config"
cp $BACKUPDIR/$FILE $BACKUPDIR/$CONFIGOLD
rm $BACKUPDIR/$FILE
else
echo "No Backupfile present yet"
fi
if test -f $TARGET/$FILE ; then
echo "Copying Original config to Backup directory"
cp $TARGET/$FILE $BACKUPDIR
rm $TARGET/$FILE
else
echo "No Original Config File Present!?!?"
fi
else
echo "Backup directory does not exist."
echo "making new directory"
mkdir $BACKUPDIR
if test -f $TARGET/$FILE ; then
echo "Copying Original config to Backup directory"
cp $TARGET/$FILE $BACKUPDIR
else
echo "No Original Config File Present!?!?"
fi
fi
echo "Moving New config file to "$TARGET
cp $SOURCE/$FILE $TARGET
rm $SOURCE/$FILE
else
echo "No New Config present, Nothing to process"
fi
SOURCE=/var/config
TARGET=/var/etc
FILE=CCcam_3.cfg
BACKUPDIR=/var/backup
CONFIGOLD=CCcam_3.old
if test -f $SOURCE/$FILE ; then
echo "New Config Present"
if test -d $BACKUPDIR ; then
if test -f $BACKUPDIR/$CONFIGOLD ; then
echo "Removing OLD config file from backup directory"
rm $BACKUPDIR/$CONFIGOLD
else
echo "No OLD config to remove."
fi
if test -f $BACKUPDIR/$FILE ; then
echo "Renaming Backup to old config"
cp $BACKUPDIR/$FILE $BACKUPDIR/$CONFIGOLD
rm $BACKUPDIR/$FILE
else
echo "No Backupfile present yet"
fi
if test -f $TARGET/$FILE ; then
echo "Copying Original config to Backup directory"
cp $TARGET/$FILE $BACKUPDIR
rm $TARGET/$FILE
else
echo "No Original Config File Present!?!?"
fi
else
echo "Backup directory does not exist."
echo "making new directory"
mkdir $BACKUPDIR
if test -f $TARGET/$FILE ; then
echo "Copying Original config to Backup directory"
cp $TARGET/$FILE $BACKUPDIR
else
echo "No Original Config File Present!?!?"
fi
fi
echo "Moving New config file to "$TARGET
cp $SOURCE/$FILE $TARGET
rm $SOURCE/$FILE
else
echo "No New Config present, Nothing to process"
fi
exit

name startscript: MoreCCcamstart.sh
--------------------------------------------------------------------------

#!/bin/bash
#Script to start more then one CCcam's with different nodeid
#Script is written by Youknowhoo.
echo "Starting first CCcam server"
/usr/local/bin/CCcam_1.x86 -C /var/etc/CCcam_1.cfg
echo "chown owner nodeid"
chown xxxxx /tmp/.CCcam.nodeid
echo "Removing nodeid and starting second CCcam server"
rm /tmp/.CCcam.nodeid && /usr/local/bin/CCcam_2.x86 -C /var/etc/CCcam_2.cfg
echo "chown owner nodeid"
chown xxxxx /tmp/.CCcam.nodeid
echo "Removing nodeid and starting third CCcam server"
rm /tmp/.CCcam.nodeid && /usr/local/bin/CCcam_3.x86 -C /var/etc/CCcam_3.cfg


xxxxx = user/inlog name from the linux distro
--------------------------------------------------------------------------
name stopscript : MoreCCcamstop.sh
--------------------------------------------------------------------------
#!/bin/bash
#Script to stop all CCcam that are running.
#Script written by Youknowhoo
echo "stop first CCcam server"
killall CCcam_1.x86
echo "stop second CCcam server"
killall CCcam_2.x86
echo "stop third CCcam server"
killall CCcam_3.x86

CCcam Monitoring / Firewalling - Protect your cccam server

- UPDATED -
Changelog :

Hi,

this set of scripts will help you protect your cccam server against various events (bad command and illegal logins) generated by your peers in order to increase cccam service stability.
The basic idea is to use the linux firewall (iptables) in "realtime" to block cccam traffic for specific peers (ip) based on cccam debug output.

This work was initialy inspired by discussions on this thread "How to solve the disconnecting client issue" and is a partial answer to that specific cccam problem.

Although all of it was designed on a debian standlone cccam server having a local firewall, it should also work if your firewall is on a remote machine on your local network.

The Dreambox setup is still NOT working at the moment and will be discussed at the end of the tutorial.


I have been using the scripts for many months with cccam 2.0.10 / 2.1.0 / 2.1.2. I didn't notice any cccam crashes or problems with peers. My server has 50-70 peers and gets between 30 and 100 bad commands a day but their effect is barely noticeable.

Concerning CCcam 2.1.2, my tests showed increased problems with peers regarding the login process, leading to numerous peer bans and peers disconnections. Something has definitely changed in that cccam version that was not present in cccam < 2.1.2.

I personally reverted to cccam 2.1.0 (you can probably use 2.1.1 safely too) and won't be using 2.1.2, i'll wait for 2.1.3 and see what happens then, i suggest you do the same unless you're satisfied with 2.1.2.

The only advantage i can see with 2.1.2 is that it lets my script ban login floods, i'll work on that feature for cccam < 2.1.2 when i have time, for it is the last missing protection i can think of regarding cccam problems, i also noticed some ecm requests floods but i probably never will filter thoses.

Features :
- block peers based on a specific number of bad commands or slow "cards" commands, for any number of minutes.
- block peers doing "illegal logins" (no account or bad password) for any number of minutes.
- protect cccam accounts or ips from being blocked or give them a different error count.
- filter main log and keep only relevant information (reduce log size) and split logs (monitoring, ecm, logins).
- modify monitoring behaviour, turn on/off firewall blocking or logs without having to restart cccam.
- iptables rules use user defined chains in order to keep your iptables firewall fast, clean and safe.



Prerequires :
- cccam running in debug mode with timestamps (-d -t)
- iptables (optional - can be disabled to use only logs)
- sudo to access iptables for your cccam user, with or without password (optional - sudo can be omitted or use of ssh to manage an external firewall)
- cron to perform iptables flush rules (unban) (optional if iptables is not used)
- bash/sh/ash(/busybox) POSIX shell script (read the dreambox section for more info on the scripting problems with ash/busybox shells) and some basic shell commands cat, echo, cut, grep..



Install :
There's not much to do if you know that your system matches the prerequires above.

Open a command line window and make sure you are running your cccam user.
Put the scripts start.sh config.sh fork.sh monitor.sh iptables.sh, in your cccam directory along with the two "protected_account" "protected_ip" files if you need them.

Make sure the scripts can run on your shell, to do that first find out which shell you are running, there's a great change your linux system has links to simulate the precense of sh or bash but you can check your installed shells with the "whereis" command ("#whereis sh", "#whereis ash"...).
The scripts should be POSIX compatible to run on most shells and are configured to run on ash which is supposed to be faster than sh/bash, with the exception of "fork.sh" which MUST run on sh/bash or any shell that will release terminated child scripts and won't generate zombie processes (defunct).
If you don't want to install or use "ash" you can edit each script and change their top line :

#!/bin/ash

with something matching your shell, like :

#!/bin/bash

You need to edit/copy config.example.sh to config.sh, and make config.sh match your setup, each config line has comments.
Make sure you get the iptables parameters right if you intend to use it.

Be very careful to properly set CCCMODE to match your cccam version !

fork.sh will try to create the necessary directories LOGDIR and WORKDIR (see config.sh), but if for some reason it doesn't work and shows errors, create two subdirectories to put logs and work files, default directories are "logs" and "monitor", path are defined in config.sh and can be set to whatever you'd like :

cd /path/to/cccam
mkdir monitor
mkdir logs
chmod 0775 logs monitor

Make sure the scripts are executable :

chmod +x  start.sh config.sh fork.sh monitor.sh iptables.sh

You can test your iptables setup by running the init command :

./iptables.sh init

iptables init is always run when the fork.sh script starts so you don't actually need to run the init command manually but if your get some errors you will have to fix them.
If you run the init multiple times you will have two errors "iptables: Chain already exists", this is not a problem.

Errors are redirected to you main log file (default "logs/monitor.log") so read it to see if errors appear.

Make sure cccam output looks like this :

12:15:21.499 CCcam: deleting client xx.xx.xxx.xxx(userX), bad command
12:15:21.501 CCcam: deleting client yy.yyy.yyy.yy(userY), read result -1
12:15:27.896 CCcam: 1498 cards --> client yy.yyy.yyy.yy(userY) (took 0.2730 seconds)

you can test that by running cccam in the foreground with :

./CCcam.x86 -d -t -C ./CCcam.cfg

according to cccam --help, the only thing that could be missing is the timestamp. Although i think that -d activates debug mode, not only foreground, and then outputs everything including timpestamps, also overriding cccam config options like DEBUG..


Finally when you're all set you can run cccam with the following command from the cccam directory :

./CCcam.x86 -d -t -C ./CCcam.cfg | ./fork.sh >> /path/to/cccam/logs/monitor.log &

Or use the start.sh script :

./start.sh start

start.sh has to be placed in the same directory as the other scripts and has the following commands "start / stop / restart". It uses regular ps/kill commands so it should be compatible with most systems. And can be used to monitor cccam status and restart it if necessary so you can use the "start" command in your cron to check if cccam has crashed and restart it.


You can then check out the main log with :

tail -n30 -f logs/monitor.log

if everything works fine and you are using the firewall, you have to add a cron command to flush rules when they expire.

*/1 * * * * /path/to/cccam/iptables.sh flush >> /path/to/cccam/logs/monitor.log 2>&1

It will run the iptables flush script every minute and delete rules that have expired (exceeded the ban duration)




Usage :

CCCam 2.1.0/2.1.1 specific :
Those two versions produce a lot more "bad command" events than other versions because some events were renamed as bad commands and were not before, knowing that i'd suggest being a little more tolerant regard the bad command counts and bans if you notice a large number of bans, so you could use settings like the following :

BADDELAY=2               # bad command count duration in minutes
BADCOUNT=5              # bad command count
BADCOUNT_IG=10        # bad command count for protected accounts
BAN=60                      # ban duration in minutes

- CCCMODE : defines your cccam version, important if you want this script to work. Basically there's one mode "0" for all cccam but 2.1.2, and one mode "1" for cccam 2.1.2 and probably upcoming cccam revisions.

- BADCOUNT/BADCOUNT_IG : Knowing that any peer can generate a bad command it is probably not a good idea to ban them at the first one. A good peer will most likely succeed to connect on its second attempt.

- BADDELAY/BAN : bad commands being mostly caused by networking problems (probably very slow lines) it can be something temporary. That's why a 120min ban is usually enough to let the peer try again at a later time when the network conditions have changed. Using a short ban duration like 30min or less will simply let the bad peer send more commands and cripple your cccam server. If you let a peer send more than one bad command then the error count spreads accross the BADDELAY duration.

- BANLOGIN : banning illegal logins is optional but after exchanging Clines with many peers you will find out that a bunch of them won't remove your Cline, getting your cccam server to handle a large amount of login attempts that are all doomed to failure. I just thought that filtering that traffic wouldn't hurt (read bugs and limitations below). It should also protect your server from brute force login attacks although i doubt anyone would try to do such a visible hack.

- LOGUNKNOWN/UKNOWNMAINLOG : are used to help cccam identify accounts that produce some events. LOGUNKNOWN will tell cccam to look for missing account names for the event processed by looking at current work/temp files. In addition, the optional UKNOWNMAINLOG will let cccam look into the main log file, this can be very helpful but can also produce some nasty side effects if your main log is big. So you should make sure to manage (rotate/purge on a daily basis) your main log file if you intend to use that option.

- CARDSDELAY/CARDSBAD : for CCcam 2.0.x-2.1.1 - has no impact on cccam 2.1.2 . That one is a bit more tricky, it tells the monitoring script to interpret "xxxx cards --> client" commands as a bad command based on its duration. I have indeed noticed that peers taking very long time (a few seconds) to receive the cards info will disconnect active peers in the exact same way a bad command does ! Unfortunately i wasn't really able to identify a very precise duration above which diconnections happen so i used a two levels trigger to manage those commands.
CARDSDELAY is the max durations in seconds above which the peer will get a "bad command" added to its log, but it will never trigger a ban action, the trigger will only log the event and when a "real" bad command occurs at a later time then it will count as a bad command. The use of this option is quite restrictive, the default is 4 seconds.
CARDSBAD is the max number of seconds allowed for a "xxxx cards --> client" command, above which a ban action is triggered, as if a real bad command was seen. CARDSBAD is probably more important than CARDSDELAY because it will actively try to ban peers with a very slow network, it will act in the exact same way as a bad command action does, respecting the same ban trigger options (BADCOUNT/BADDELAY). CARDSBAD should always be greater than CARDSDELAY.

- DEBUG : adds some debug data to a $LOGDIR/debug.log file. Probably of no interest to you and should stay disabled (=0).

- Understand that when a peer is banned, he will see your server as offline but you will still be able to connect to his, you know what that means.



Files :
Version 2g : Download
("protected_account" and "protected_ip" are two empty files in which you can put account names and ips, one by line, that you want to "protect" from basic ban rules, see the documentation above for details)



Advanced :
- you can rotate logs, all redirects use "append" (>>).

- no sudo password
you can allow access to iptables for your cccam user (if not root) without sudo password by adding the following line to your "/etc/sudoers" file.

cccamuser   ALL=NOPASSWD:/sbin/iptables

That way you don't have to give a large sudo access to your cccam user and you don't have to put a sudo password in config.sh SUPASS option. The cccam user only requires sudo (root) access to iptables, nothing else.

- using a remote firewall
To use a remote iptables firewall on your local network you will have to replace the sudo command with a ssh one. ssh will try to connect to a remote linux system and execute the iptables command there, then return the command output to the script making the iptables command run exactly as if it was executed localy.
I will guide you quickly through a basic ssh setup but if you don't know what you are doing i'd suggest googling some SSH HOWTOs.

A proper SSH setup would be as follows :
As root, generate a key pair using your "cccam" system's (where cccam monitoring script runs) ssh key generator (ssh-keygen on debian), if any, with the following command :

ssh-keygen -t dsa

When asked for a "passphrase", we won't enter one. Just press enter twice.
That should produce two files in your root home directory : "~/.ssh/id_dsa.pub" and "~/.ssh/id_dsa"

Copy the one line content of the new "~/.ssh/id_dsa.pub" file to the following file on your remote server root user directory : /root/.ssh/authorized_keys2
Depending on your remote server ssh configuration, the file could also be : /root/.ssh/authorized_keys

Now from the cccam system you should be able to ssh your remote server with the command :

ssh root@remoteip

If it asks you to keep a footprint of the new remote system, say yes and it shouldn't bother you with that later, you can "exit" ssh now.
If it worked you can also try accessing the remote iptables firewall with that command, from the cccam system :

ssh root@remoteip /usr/bin/iptables -L -n

It should display your firewall configuration for INPUT OUTPUT FORWARD chains.

Then set the SUDO option in config.sh, like this :

SUDO="/usr/bin/ssh -x root@remoteip"

you can also empty the SUPASS option.

in order to make sure you have a working remote iptables setup you can try running the iptables.sh init command from the cccam system, as follows :

./iptables.sh init

If you run it twice it should display two errors : "iptables: Chain already exists"
That means the cccam chains have been created on your firewall and your setup works.

You can now run cccam as described in the main install guide above.




Known bugs and limitations

- log file output lines may be missplaced, some commands take longer to execute than others and the command output then gets into the log file a bit late, but this is usually something very localized and every line having a timestamp you can always understand what happened.

- some iptables rules may be insterted more than once when a event is not processed fast enough, but it doesn't matter because iptables won't mind and the flush script makes sure duplicate rules are removed.

- reloading your firewall should delete cccam init. you will have to init cccam iptables manually to fix that, with "./iptables.sh init". The good thing is that it should not get the scripts or cccam to crash, so cccam will not really care but you will get lots of errors in your cccam monitoring log..

- banning illegal logins will most certainly ban the new peers you have exchanged Clines with if you haven't activated their accounts before sending them the Clines. You will then have to remove the ban manually or wait for the iptables flush to purge it for you if you haven't banned illegal logins permanently, otherwise new peers may never be able to connect !



Dreambox

Although the scripts should run (with ssh and remote firewall) on dreambox busybox default shell (ash), as they do on my debian stable busybox (1.1.3) binary, the problem i have with that shell, or with ash (dash on debian), is that a parent script will not "release" child scripts that have ended and will then generate tons of zombie processes also known as defunct processes.

If you know a way around that busybox ash shell problem, please contact me, it will most certainly be very helpfull to dreambox users.

I must stress out the fact that running the scripts as they are on the dreambox will work for a short period of time and then stop working when the large number of defunct processes will have filled the system's proc table. It will also most certainly make the dreambox system pretty unstable or even make it crash..

#!/bin/sh
###########################
## Auto Ban script       ##
## Illegal CCcam Users   ##
## Written By CC_Share   ##
## Thanks to Unlocker-AL ##
## For the Basic idea    ##
###########################
workdir="/"                        #This is there the debug info from CCcam is dumped
firewall="/"          #The saved firewall rules
logdir="/emu/log"                       #The logfile directory
EMAIL=""                 #Email adres to mail result to
SUBJECT="Illegal Userlist CCcam"        #Subject title of the email
EMAILMESSAGE="/emu/log/illegaluser.txt" #List that contains the Illegal users
rm $workdir/debug.old
cp $workdir/debug.txt $workdir/debug.old
cp $logdir/iptables-save.new $logdir/iptables-save.old
cat $workdir/debug.old|grep illegal > $logdir/illegaluser.log
grep 'illegal' $logdir/illegaluser.log | awk -F" " '{print $5,$7}' > $logdir/illegaluser.txt
grep 'illegal' $logdir/illegaluser.log | awk -F" " '{print $7}' | grep -o '^[0-9]\{1,3\}\.[0-9]\{1,3\}\.[0-9]\{1,3\}\.[0-9]\{1,3\}' > $logdir/badIP.out
awk '
{s[$0]++}
END {
for(i in s) {
if(s[i]>1) {
print i
}
 }
 }' $logdir/badIP.out > $logdir/badIP.block
while IFS= read -r EachLine
do
command="iptables -A INPUT -s "$EachLine" -j DROP"
echo $command
$command
done < $logdir/badIP.block
rm $logdir/badIP.block
if [ -s $logdir/illegaluser.txt ] ; then
iptables-save -c > $logdir/iptables-save.new
/usr/bin/nail -s "$SUBJECT" "$EMAIL" < $EMAILMESSAGE
else
echo "No Illegal Users found right now"
fi
sleep 1
> $workdir/debug.txt
exit 0

./CCcam.x86 -dv > /home/debug.txt

workdir="/"

workdir="/home"

firewall="/"

firewall="/emu/log/"

00 */1  * * * root /emu/script/./illegal.sh

apt-get install nail
apt-get install exim4
dpkg-reconfigure exim4-config

EMAIL=""

This how-to will cover the basic installation of Debian linux and getting CCcam up and running on it.

This How-to is still WIP by CC_Share

--Todo--

---------------------------------------

First download the netinstall cd of debian linux
You can download it from the following URL:
Link http://cdimage.debian.org/debian-cd/...86-netinst.iso

This will install the basic debian linux system on you're harddisk.
Boot the computer from the CD you just created.

Just press enter here to start the installation


Select the language you prefer


Select the country you're in. Based on the language it selects a default country


Here you can choose the keyboard layout. Make sure you select the proper layout otherwise installation might prove to be quite tricky.


Set up the hostname of you're server here. I prefer to set up the first part of my DYNDNS account info here.


Here you must enter the domain name. In the example above, you can see i put dyndns.org here


Next up is the partition guide. Here you must choose



Select the right harddisk. Usually in a stand-alone server, there will just be one entry


Debian will let you choose to have everything in 1 partition, or have seperate partitions for the important directory's. One advantage of having seperate partitions, You cannot fill the root system by accident if you upload a lot to the home directory. Linux will NOT boot correct , if the root filesystem is full


In the overview, You can check to see if all is set up correct before writing the changes to harddisk. Once you press finish, it will show you the next screen if you are really sure .


Once you select yes, It will write the changes to harddisk and format all partitions.


If Debian cannot guess you're timezone by looking at the bios, it will ask you for the timezone


Next you will have to enter the root password. Do not choose an easy to guess password if you want the server to be reachable from the internet. (if you want to use SSH for example to manage the server from work)



Next is setting up an account to use for FTP transfer.


Again, do not use a simple to guess password. This account can also be used for SSH


If you have the option, allways choose a network server.
Make sure you select a fast and stable one.
Usually univercity servers prove to be fast and stable


In the software selection screen, select base system and webserver


One of the last things it needs to know, is where to place the grub bootloader. Usually it is safe to place it on the MBR


Congratulations, You just installed a fresh new DEBIAN server.


As you might have noticed, during installation, debian uses dhcp to aquire an ip adress.
For a cardserver, it's not recommened to have it's IP adress handled by DHCP.
First thing we need to do is remove the DHCP and assign a static IP to the linux server

Assigning static IP
Log in as root with the right password
then type in the following command

vim /etc/network/interfaces

now remove the following line

iface eth0 inet dhcp

and replace it with

auto eth0
iface eth0 inet static
address 192.168.1.225
netmask 255.255.255.0
broadcast 192.168.1.255
gateway 192.168.1.1

These IP adresses might be different for you're situation.
Remember to replace them with the numbers you need.
You can save the file with the following commands

:wq

Once the file is saved, you can restart the network and check if you're linux server is running with it's new IP adress

/etc/init.d/networking restart
ifconfig

ifconfig should now look something like this

Installing SSH
Next thing that needs to be done is install a SSH deamon.
This will allow you to log into the cardserver from you're own computer and the server does not require a keyboard and monitor if you want to change something.

apt-get install openssh-server

Once SSH is installed, you can logout of the server,remove the keyboard and monitor as we don't need it anymore.

Getting Putty
We need to download putty so we can log in with SSH
http://the.earth.li/~sgtatham/putty/.../x86/putty.exe

Remove the CD-ROM drive from the apt-get mirror list:
To make sure the server does not need the CD-ROM anymore to update or install software, we need to remove it from the mirror list of apt-get.

vim /etc/apt/sources.list

now remove the lines that point to the CD-ROM drive and save the file.

Update apt-get software list
To make sure, you locally have a good software list available, you have to update the apt-get database

apt-get update

Installing FTP server
To be able to transfer files between you're computer and the linux server, a FTP server is needed.
During the installation it will ask you one question,. Answer it with "stand-alone"
This will consume a bit more memory but will prevent linux from spawning a new process every time you log in.

apt-get install proftpd

The server is now installed and all the needed files are in place.
Now it's time to get it ready for CCcam.
First thing we need to do is make 6 directory's and adjust the parameters.

mkdir /emu
mkdir /emu/cccam
mkdir /emu/script
mkdir /emu/log
mkdir /var/etc
mkdir /var/keys
chmod 777 /emu
chmod 777 /emu/*
chown  /emu
chown  /emu/*

The username started above is the username you created during the installation. This name is going to be used for file transfer.

Startup script for CCcam
To prevent from having to change directory all the time we're gonna place a script on the server so CCcam can be started from any directory on the server.

vim /emu/script/cccam

#!/bin/sh
CAMNAME="CCcam Server"
# end
 
# This method starts CCcam
start_cam ()
{
/emu/cccam/CCcam.x86 &
sleep 2
}
# This method stops CCcam
stop_cam ()
{
pkill CCcam.x86
}
case "$1" in
start)
echo "[SCRIPT] $1: $CAMNAME"
start_cam
;;
stop)
echo "[SCRIPT] $1: $CAMNAME"
stop_cam
;;
restart)
echo "Restaring $CAMNAME"
stop_cam
start_cam
;;
*)
"$0" stop
exit 1
;;
esac
exit 0

chmod 755 /emu/script/cccam
ln /emu/script/cccam /bin/cccam

Now you can simply start, stop or restart CCcam from any directory by simply typing

cccam start
cccam stop
cccam restart

Upload CCcam
Now use a FTP program to upload CCcam.x86 and CCcam.cfg to /emu/cccam

Making CCcam executable
Use putty again to give CCcam.x86 execution rights

chmod 755 /emu/cccam/CCcam.x86

Config update script
When you're running a big server, restoring connections can take some time then you change you're config file. I like to do my config changes once a day. I use this script to backup the old config and put the new config in place. This is done at 3am so my peers don't notice it and they don't suffer from a freezing picture every time you make a change.

vim /emu/script/configupdate.sh

#!/bin/sh
#Script to process new config and backup old one.
#Script designed and written by CC_Share
SOURCE=/emu/cccam
TARGET=/var/etc
FILE=CCcam.cfg
BACKUPDIR=/var/backup
CONFIGOLD=CCcam.old
if test -f $SOURCE/$FILE ; then
 echo "New Config Present"
 if test -d $BACKUPDIR ; then
  if test -f $BACKUPDIR/$CONFIGOLD ; then
  echo "Removing OLD config file from backup directory"
  rm $BACKUPDIR/$CONFIGOLD
  else
  echo "No OLD config to remove."
  fi
 
                if test -f $BACKUPDIR/$FILE ; then
                echo "Renaming Backup to old config"
                cp $BACKUPDIR/$FILE $BACKUPDIR/$CONFIGOLD
                rm $BACKUPDIR/$FILE
                else
                echo "No Backupfile present yet"
                fi
                if test -f $TARGET/$FILE ; then
                echo "Copying Original config to Backup directory"
                cp $TARGET/$FILE $BACKUPDIR
                rm $TARGET/$FILE
                else
                echo "No Original Config File Present!?!?"
                fi
 else
 echo "Backup directory does not exist."
 echo "making new directory"
 mkdir $BACKUPDIR
                if test -f $TARGET/$FILE ; then
                echo "Copying Original config to Backup directory"
                cp $TARGET/$FILE $BACKUPDIR
                else
                echo "No Original Config File Present!?!?"
                fi
 fi
 echo "Moving New config file to "$TARGET
 cp $SOURCE/$FILE $TARGET
 rm $SOURCE/$FILE
else
echo "No New Config present, Nothing to process"
fi
exit

chmod 755 /emu/script/configupdate.sh

Putting configupdate in crontab
To make sure the config update script will run at 3 am everynight, we can place it in the crontab.

cd /etc
vim crontab

and add the following line to it

00 3 * * * root /emu/script/./configupdate.sh >>/emu/log/configupdate.log 2>&1

This will run the script every day at 3am, and it's output will be writen in /emu/log/configupdate.log so you can check on occasion if all went well.

Putting CCcam in bootsequence

There's only one more thing to do. Add CCcam to the startup so it will start on the next reboot.

vim /etc/rc.local

and add the following line at the bottom

/bin/cccam start &

test the config update script created earlier to see if that works

/emu/script/./configupdate.sh

If it works, you can reboot the server and check if CCcam is running.

Howto NewCS on debian based on "Howto: Building Debian Linux server with CCcam" written by CC_share (useful for N3 cards with hd-channels because hd channels from this cards won´t run on actual cccam so you should use mgcamd as newcs client)

This howto ´ll show the installation for Debian linux with newcs.
You should use it in combination with the "Howto: Building Debian Linux server with CCcam" written by CC_share with needed basic-installation tutorial for debian linux.
You can also combine this tutorial with his one to install a cccam server with
newcs as cardserver.
If you´ve installed your debian system on the CC_share way you should have all needed basics on place.
To use cccam and newcs together you should first install debian with cccam with the tutorial of CC_Share.
If you need only newcs on your system, use CC_share´s tutorial from the start to "Startup script for CCcam"
After that you should use the following commands via telnet.
For systems with complete "CC_share like" installation you ´ll need only the
following additional steps.
You can copy and paste the following commands in your putty console.
Code:

mkdir /emu/newcs
vim /emu/script/newcs

Now you must push "i" on your keyboard and insert the following
Code:

#!/bin/sh
CAMNAME="NewCS Server"
# end

# This method starts CCcam
start_cam ()
{
/emu/newcs/newcs.i686 &
sleep 2
}
# This method stops NewCS
stop_cam ()
{
pkill newcs.i686
}
case "$1" in
start)
echo "[SCRIPT] $1: $CAMNAME"
start_cam
;;
stop)
echo "[SCRIPT] $1: $CAMNAME"
stop_cam
;;
restart)
echo "Restaring $CAMNAME"
stop_cam
start_cam
;;
*)
"$0" stop
exit 1
;;
esac
exit 0

Save it by pushing "Esc" followed by "ZZ" on your Keyboard.
Next commands are
Code:

chmod 755 /emu/script/newcs
ln /emu/script/newcs /bin/newcs

Now you can simply start, stop or restart newcs in putty by typing
Code:

newcs start
newcs stop
newcs restart

Now use a FTP program to upload newcs.i686 and newcs.xml to /emu/newcs ,but dont forget to rename the newcs.xml.phoenix to newcs.xml before you upload it.
May be you have to edit your newcs.xml to change the "node" entry from
"/dev/tts/0" into "/dev/ttyS0" for com1 or
"/dev/ttyS1" for com2.

Making NewCS executable
Use putty again to give newcs.i686 execution rights
Code:

chmod 755 /emu/newcs/newcs.i686

Config update script
When you're running a big server, restoring connections can take some time when you change your config file. I like to do my config changes once a day. I use this script to backup the old config and put the new config in place. This is done at 3am so my peers don't notice it and they don't suffer from a freezing picture every time you make a change.

Code:

vim /emu/script/configupdate_newcs.sh

Now you must push "i" on your keyboard and insert the following
Code:

#!/bin/sh
#Script to process new config and backup old one.
SOURCE=/emu/newcs
TARGET=/etc
FILE=newcs.xml
BACKUPDIR=/var/backup
CONFIGOLD=newcs.old
if test -f $SOURCE/$FILE ; then
echo "New Config Present"
if test -d $BACKUPDIR ; then
if test -f $BACKUPDIR/$CONFIGOLD ; then
echo "Removing OLD config file from backup directory"
rm $BACKUPDIR/$CONFIGOLD
else
echo "No OLD config to remove."
fi

if test -f $BACKUPDIR/$FILE ; then
echo "Renaming Backup to old config"
cp $BACKUPDIR/$FILE $BACKUPDIR/$CONFIGOLD
rm $BACKUPDIR/$FILE
else
echo "No Backupfile present yet"
fi
if test -f $TARGET/$FILE ; then
echo "Copying Original config to Backup directory"
cp $TARGET/$FILE $BACKUPDIR
rm $TARGET/$FILE
else
echo "No Original Config File Present!?!?"
fi
else
echo "Backup directory does not exist."
echo "making new directory"
mkdir $BACKUPDIR
if test -f $TARGET/$FILE ; then
echo "Copying Original config to Backup directory"
cp $TARGET/$FILE $BACKUPDIR
else
echo "No Original Config File Present!?!?"
fi
fi
echo "Moving New config file to "$TARGET
cp $SOURCE/$FILE $TARGET
rm $SOURCE/$FILE
else
echo "No New Config present, Nothing to process"
fi
exit

Save it by pushing "Esc" followed by "ZZ" on your Keyboard.

Next commands are
Code:

chmod 755 /emu/script/configupdate_newcs.sh


To make sure the config update script will run at 3 am everynight, we can place it in crontab.

Code:

cd /etc
vim crontab

Now you must push "i" on your keyboard and insert the following
Code:

00 3 * * * root /emu/script/./configupdate_newcs.sh >>/emu/log/configupdate_newcs.log 2>&1

Save it by pushing "Esc" followed by "ZZ" on your Keyboard.

Add NewCS to the startup so it will start on the next reboot.
Code:

vim /etc/rc.local

Now you must push "i" on your keyboard and insert the following
Code:

/bin/newcs start &

Save it by pushing "Esc" followed by "ZZ" on your Keyboard.
Now you should reboot the server and check that NewCS and (or) CCcam is running.

This how-to will cover the installation of Debian linux Version5 and Install CCcam.

As a new Debian version was released, i thought is was also time for a fine tuned how-to.
Some screens have changed and i noticed from the previous thread some folks were struggeling to get a few things working.

This is why i put together a complete and automated installation package for CCcam.
After installing Debian, all you have to do is download and run the installation script.
Once that is finished, the server will have apache, ftp, SSH, CCcam version 2.1.4 and PHPwebinfo from TOOGOODY (version 1.02) running on it.
It will also convert the server from DHCP to a static IP.

This script is intended to run on both the 32 aswel as the 64 bit version of Linux.


This How-to is still WIP by CC_Share

-- Todo --

-- Fixed --
Improper restart of vsftpd after installation
Config update script adjusted. It will flush IPTABLES when activating new config now
cccam start stop script updated. Restart option did not function properly on some systems.
New config for vsftpd included. Fixed permission denied problem for some installations
Fixed Illegal user script and CCcam start/stop script. Thanks to smurfer

-- Added --
Oscam download and compilation
Oscam scripts (can be started like CCcam with oscam start|stop|restart)

---------------------------------------

First download the netinstall cd of debian linux
You can download it from the following URL:
32 Bit version
Link ftp://ftp.nl.debian.org/debian-cd/5....86-netinst.iso
64 Bit version
Link ftp://ftp.nl.debian.org/debian-cd/5....64-netinst.iso

This will install the basic debian linux system on you're harddisk.
Boot the computer from the CD you just created.

Just press enter here to start the installation


Select the language you prefer


Select the country you're in. Based on the language it selects a default country


Here you can choose the keyboard layout. Make sure you select the proper layout otherwise installation might prove to be quite tricky.


Set up the hostname of you're server here. I prefer to set up the first part of my DYNDNS account info here.


Here you must enter the domain name. In the example above, you can see i put dyndns.org here


Next up is the partition guide. Here you must choose



Select the right harddisk. Usually in a stand-alone server, there will just be one entry


Debian will let you choose to have everything in 1 partition, or have seperate partitions for the important directory's. One advantage of having seperate partitions, You cannot fill the root system by accident if you upload a lot to the home directory. Linux will NOT boot correct , if the root filesystem is full


In the overview, You can check to see if all is set up correct before writing the changes to harddisk. Once you press finish, it will show you the next screen if you are really sure .


Once you select yes, It will write the changes to harddisk and format all partitions.


Next you will have to enter the root password. Do not choose an easy to guess password if you want the server to be reachable from the internet. (if you want to use SSH for example to manage the server from work)




Next is setting up an account to use for FTP transfer.Use username cccam for this.
It's very important you use the correct username as some scripts depend on this name!!


Again, do not use a simple to guess password. This account can also be used for SSH


When selecting a mirror, make sure you select a good, fast one






In the software selection screen, select base system


One of the last things it needs to know, is where to place the grub bootloader. Usually it is safe to place it on the MBR


Congratulations, You just installed a fresh new DEBIAN server.


---

Installing and running the script

Log into the server using username root

type in:

wget http://tiny.cc/f9kKY
chmod 755 installation.sh
./installation.sh

**Update **
A newer revision with Oscam support is available
You can download it by replacing the URL above with :

wget http://tiny.cc/QfzpU

Edit CnbYag:
In case that download link is down, you can get the files here:
http://www.eurocardsharing.com/downl...l-scripts-295/
.... end edit


And you're allmost done. An installation package will be downloaded, scripts will be installed. The script will keep you informed of what it is doing.


All it needs as userinput at the end of the installation if the following:

New STATIC ip adress
subnet mask
gateway
DNS server

Once this is finished, You can use a FTP client to upload you're CCcam config to the server and reboot it.

After the first reboot, the server will put the config in the right place and start CCcam.

Just remember the server is allready reachable with it's NEW static IP



If you included oscam emu, the config files should be placed in /emu/oscam. This way you allways know where they are.
The logfiles from oscam can be found in /emu/log

There are allready a sample config, userfile and serverfile present in /emu/oscam

一个博客,一个网站最重要的就是数据库,所以经常备份数据是必须的.尽管 WordPress 有定时备份数据的插件,但只能备份当前的博客,不够灵活.适合个人小小博客,对于一些网站来说,就不适合了.现在很多人都拥有多个网站.每个网站都装个插件就比较麻烦了.况且不是每个网站都是 WordPress 的 .

所以写了个自动备份mysql数据库的脚本,再加上gmail这个G级邮箱,备份多少数据都可以了...下面是代码:

mysqldump -uuser -ppassword --databases db1 db2 db3 > /home/website/backups/databackup.sql
tar zcf /home/website/backups/databackup.sql.tar.gz /home/website/backups/
echo "主题:数据库备份" | mutt -a /home/website/backups/databackup.sql.tar.gz -s "内容:数据库备份" www@gmail.com
rm -r /home/website/backups/*

将上面的代码保存为automysqlbackup.sh
然后利用crontab 实现动备份,在ssh下,

crontab -e

输入以下内容:

00 00 * * * /home/website/automysqlbackup.sh

这样就实现了每天00:00自动备份mysql数据库并发送到Email

简单的说明下吧.
第一句是一次性备份多个数据库,这个要你用root权限的用户才可以的..-u后面的是数据库用户名 -p后面的是数据库密码 无需空格 db1 db2 db3为你需要备份的数据库名.
如果你的数据库用户名没有root这个权限,可以改为这样

mysqldump -uuser -ppassword db1 > /home/website/backups/db1.sql
mysqldump -uuser -ppassword db2 > /home/website/backups/db1.sql
mysqldump -uuser -ppassword db3 > /home/website/backups/db1.sql

第二句是将 backups 文件夹里面的数据文件压缩为文件名:databackup.sql.tar.gz

第三句是将压缩了的数据库文件发送到指定的邮箱.....

其中的主题:数据库备份 ,就是邮件的主题, 内容:数据库备份,就是邮件的内用,

/home/website/backups/databackup.sql.tar.gz 为附件

www@gmail.com为要发送的Email

功能简介：
可以对FTP里，从根目录起的所有数据进行备份

使用限制：
无，只要是cPanel都可以使用

详细步骤：

一、设置cp_full_backup.php

文件代码：

// 此PHP程序配合Cron jobs使用可以定期自动产生cPanel备份,
// 以max.hedroom在cpanel.net论坛的文章为程序基础,
// 这个程序包含密码, 请注意档案安全.
// 中文翻译修正：Fred, http://www.ifred.cn/cp-full-backup
// ********* 下列项目需要设定 *********
// cPanel登入信息
$cpuser = ""; // 登入cPanel的账号
$cppass = ""; // 登入cPanel的密码
$domain = ""; // cPanel绑定的域名(或ip)
$skin = ""; // 设定正在使用的cPanel模板(例如:x, x3, rvblue)
// FTP上传的信息
$ftpuser = ""; // FTP账号
$ftppass = ""; // FTP密码
$ftphost = ""; // FTP服务器网址(或ip)
$ftpmode = ""; // FTP模式("ftp"或"passiveftp")
// 通知信息
$notifyemail = ""; // 寄发执行结果的e-mail位置
// 安全模式
$secure = 0; // 0为标准http, 1为ssl(需要主机支持ssl功能)
// 设定值为1时会在排程记录中产生网页报告
$debug = 0;
// *********** 以下不需更改 *********
if ($secure) {
$url = "ssl://".$domain;
$port = 2083;
} else {
$url = $domain;
$port = 2082;
}
$socket = fsockopen($url,$port);
if (!$socket) { echo "Failed to open socket connection... Bailing out!\n"; exit; }
// Encode authentication string
$authstr = $cpuser.":".$cppass;
$pass = base64_encode($authstr);
$params = "dest=$ftpmode&email=$notifyemail&server=$ftphost&user=$ftpuser&pass=$ftppass&submit=Generate Backup";
// Make POST to cPanel
fputs($socket,"POST /frontend/".$skin."/backup/dofullbackup.html?".$params." HTTP/1.0\r\n");
fputs($socket,"Host: $domain\r\n");
fputs($socket,"Authorization: Basic $pass\r\n");
fputs($socket,"Connection: Close\r\n");
fputs($socket,"\r\n");
// Grab response even if we don't do anything with it.
while (!feof($socket)) {
$response = fgets($socket,4096);
if ($debug) echo $response;
}
fclose($socket);
?>

请勿使用Windows自带的记事本编辑设置。推荐使用UltraEdit等文本编辑软件进行设置，并保存格式为UTF-8

二、上传cp_full_backup.php

三、Cron jobs设置

四、备份成果

一旦完成了备份，你会收到一封标题为“Full Backup Completed”的邮件，FTP里也会有经过压缩的备份文件包。

TTVNC的目的是帮助用户远程进行远程电脑维护。该软件通过服务器中转可以跨越NAT网络，让任何能够上网的计算机都能够远程管理，因而使用更加方便。该软件改造自 TightVNC VNC RealVNC 等远程终端控制软件。

http://www.ttvnc.com/cn/

http://www.blog.163.com/ttvnc/

Centos下安装X Window+GNOME Desktop的一键包，希望能方便那些需要在centos下安装图形界面的客户！
特别说明：本站只提供安装的一键包，不再提供任何与之相关的技术支持；本站不承担安装此一键包后出现影响生产环境之类等一切严重后台，故建议客户是在一个干净的centos系统里安装，另建议内存在768以上的客户安装及建议安装在32位的centos系统上！
本安装包本站已在centos5.5 32bit上安装成功，软装不成功可能与你之前安装的有软件上冲突之类的，请重装系统重试！
安装过程：
wget http://www.vpsyou.com/sh/xwindow.sh;sh ./xwindow.sh;
将上面1行复制，粘贴到您的linux ssh控制台里，回车，全自动安装，等待5-30分钟即可完成！
出现如下图时，按回车就行，表明你已经安装成功

如何登陆：
1.用winscp登陆你的vps，下载/backup/www.vpsyou.com/client.id_dsa.key到本地
2..下载FreeNX Windows 客户端并安装，下载地址：
http://www.nomachine.com/download-client-windows.php
3..安装FreeNX后打开，输入root，密码及vps的IP，并导入刚才下载回来的client.id_dsa.key，具体请看图：