Showing posts with label GBOX-MBox Tutorials. Show all posts
Showing posts with label GBOX-MBox Tutorials. Show all posts

Friday, August 6, 2010

new sky white card update mgcamd and newcs, omnikey

Well peeps i tested it some time i can confirm it works
1.you need install mgcamd 1.31 and mgcamd config on your dreambox
2. rename newcamd.list.example to newcamd.list
3. in newcamd list you need change line
CWS = yournewcsserverip your newcs port dummy1 dummy1
01 02 03 04 05 06 07 08 09 10 11 12 13 14 lan newcs
3. Add new user with webinterface to your newcs server or just
paste it to xml
dummy1dummy1
on
offoff0access

4. Make sure ur xml have au enabled
No
No
No
5. When your card entitlements need to be updated you
need switch default cam on your dreambox to mgcamd and to force updates you need set ur tv on channel what you don't have in your local card example Racing UK

Let it run all night and then check is there card entitlements up to date

Few other things im 2 lazy explain what is what in mgcamd_cfg and im using default as it is you don't need change any of the parameters there.
just make sure G: { 01 } and that's it

Howto: Building Debian Linux server with Gbox/cs2gbox

This how-to is basicly the same as the CCcam how-to. It will cover the basic installation of Debian linux and getting Gbox up and running on it.

This How-to is still WIP by CC_Share

--Todo--
Correct typo's (if any are made)
---------------------------------------

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

This will install the basic debian linux system on you're harddisk.
Just follow the steps on CD to get the system up and running.
During the installation process, it will ask you several questions
Hostname and domain are not really of much importance right now as you can change it lateron. Here you can input a hostanem and domain of you're choice.

Another question is if it can use the entire harddisk. As it is going to be a dedicated server, you can use the entire harddisk

Quote:
Guided - use entire disk
When it's asking you for a network mirror, make sure you choose a fast and stable server.
Usually univercity servers are fast and stable.

When you've completed the network mirror, it's going to download the software list.
Now you can deselect everything to keep the server as small as possible.
All you have to select is webserver.
After a while it will eject the CD and it will start to reboot.

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
Code:
vim /etc/network/interfaces
now remove the following line
Code:
iface eth0 inet dhcp
and replace it with
Code:
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
Code:
: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
Code:
/etc/init.d/networking restart
ifconfig
ifconfig should now look something like this
Quote:
cardserverBackup:/home# ifconfig
eth0 Link encap:Ethernet HWaddr 00:00:00:10:D0:70
inet addr:192.168.1.225 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::250:4ff:fe1d:d27b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8931 errors:0 dropped:0 overruns:0 frame:0
TX packets:6028 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:7585683 (7.2 MiB) TX bytes:916823 (895.3 KiB)
Interrupt:10 Base address:0x4000
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.
Code:
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.
Code:
vim /etc/apt/sources.list
now remove the lines that point to the CD-ROM drive and save the file.
Quote:
deb cdrom:[Debian GNU/Linux 4.0 r0 _Etch_ - Official i386 NETINST Binary-1 20070407-11:29]/ etch contrib main
Update apt-get software list
To make sure, you locally have a good software list available, you have to update the apt-get database
Code:
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.
Code:
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 Gbox.
First thing we need to do is make 6 directory's and adjust the parameters.
Code:
mkdir /emu
mkdir /emu/gbox
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 gbox
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.
Code:
vim /emu/script/gbox
Code:
CAMNAME="Gbox"
INFOFILE="ecm.info"
# end

# This method cleans up /tmp folder of gbox files
remove_tmp ()
rm -rf /tmp/*info* /tmp/*gbox* /tmp/*online* /tmp/*share* /tmp/atack* /tmp/debug*

# This method Gbox (That order)
start_cam ()
/emu/cs2gbox.x86 &
/emu/gbox/gboxx86 &
# This method stops gbox and then calles the tmp cleanup method
stop_cam ()
touch /tmp/gbox.kill
pkill cs2gbox.x86
pkill gboxx86
remove_tmp

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
Code:
chmod 755 /emu/script/gbox
ln /emu/script/gbox /bin/gbox
Now you can simply start, stop or restart gbox from any directory by simply typing
Code:
gbox start
gbox stop
gbox restart
Upload gbox
Now use a FTP program to upload gboxx86 and cs2gbox to /emu/gbox
Upload the config files cwshare.cfg, softcam.cfg, gbox_cfg and cs2gbox.cfg to /var/keys

Making gbox and cs2gbox executable
Use putty again to give gboxx86 and cs2gbox.x86 execution rights
Code:
chmod 755 /emu/gbox/gboxx86
chmod 755 /emu/gbox/cs2gbox.x86
Putting gbox in bootsequence

There's only one more thing to do. Add gbox to the startup so it will start on the next reboot.
Code:
vim /etc/rc.local
and add the following line at the bottom
Code:
/bin/gbox start &
Now you can reboot the server and check if gbox is running.

Thursday, October 15, 2009

Running Gbox and CCcam on the Same Box

1st Script
copy this in gbox_cam.sh
---------------------------------------
CAMNAME="GbOx_CCcam"
USERNAME=""
ZAPTIME=8
CAMID=970
DVBSET=1
INFOFILE="ecm.info"
# end

# This method cleans up /tmp folder of gbox files
remove_tmp ()
{
rm -rf /tmp/*info* /tmp/*gbox* /tmp/*online* /tmp/*share* /tmp/Newcs* /tmp/atack* /tmp/debug*
}

# This method starts Gbox > CCcam (That order)
start_cam ()
{
/var/script/AES_Gbox.sh &
sleep 5
/var/bin/gbox &
sleep 30
/var/bin/CCcam_2.0.3 &
}

# This method stops gbox and CCcam and then calls the tmp cleanup method
stop_cam ()
{
touch /tmp/gbox.kill
/bin/prockill gbox
/bin/prockill CCcam_2.0.3
killall -9 newcs cs2gbox 2> /dev/null
remove_tmp
}

case "$1" in
start)
echo "[SCRIPT] $1: $CAMNAME"
start_cam
;;
stop)
echo "[SCRIPT] $1: $CAMNAME"
stop_cam
;;
restart)
echo "Restarting $CAMNAME"
stop_cam
start_cam
;;
*)
"$0" stop
exit 1
;;
esac

exit 0

--------------------------------------
rename ur cccam ver in
CCcam_2.0.3 or CCcam_2.0.4 ,CCcam_2.0.5

and reboot
this scrip is for Gemini i have test it it works very will u have gbox and cccam together .
----------------------------------------
You just have to take care about the name of both cams. It must be the same as the cam files in your dreambox.
You need about 30 sec delay between the start of gbox and the start of CCcam : even if gbox starts first , CCcam will take your local card (it is faster) so you will appear with no local for your gbox partners.

Mbox Config Tutorial

 Mbox Tutorial 



- You should remove all G-Lines And Y lines form your Gbox's cwshare.cfg before you run Mbox unless you use a different cwshare.cfg in a different path with G and Y lines removed ( set for different path in mbox.cfg than the one for Gbox )or Mbox won't run .

- You can use same ignore.list and ident.info for gbox with mbox, they go in the same path /var/keys ( unless you change the path in the settings as explained in this Tut )


- Unlike Gbox, Mbox can not read local cards directly ( not yet at least ) , that is why you need Newcs so you can share your local and have it appear as Local to other peers - explanation in examples here.

- A working cwshare & newcs example added to end of tutorial.


To start Mbox you need to configure mbox.cfg first.
These parameters you must set before you can start Mbox:


D: { 0 }
//D: { x }
//x=0 -> disable
//x=1 -> enable dbox2 cw writing
//x=2 -> enable STAPI for IPBOX
//x=3 -> enable STAPI for Kathrein

T: { /tmp/ }
// T option -> where to store temp files ... (share.info,debug.txt ,etc.)
// T: { folder_path_to_files, example: T: { /tmp/ } }

K: { /var/keys/ }
// K option -> where is cwshare.cfg file
// K: { folder_path_to_files, example: K: { /var/keys/ } }

P: { /tmp/pmt.tmp }
// P option -> PMT location (Dont used with linux and windows)
// you must be tuned to channel so image can generate this file
// { /tmp/pmt.tmp } for resivers and images that create this file <- use this
if you can
// { 1/tmp/camd.socket } for enigma 1
// { 2/tmp/camd.socket } for enigma 2



Now for the start of Mbox you need to know where the mbox.cfg path is.
The default path for mbox.cfg is /var/keys/
For other paths you must start mbox with path as argument!!!

For some receivers like Ipbox and Kathrein there is no /var/keys/ so you must
start mbox always with arguments.

Example:

without arguments
./mbox or ./var/bin/mbox

with arguments
./mbox /data/keys/mbox.cfg or ./var/bin/mbox /data/keys/mbox.cfg

To STOP Mbox you need to create mbox.kill.
Put this mbox.kill in the temp dir of Mbox.T: path (look
your settings in mbox.cfg)

Example T: { /tmp/ }: touch /tmp/mbox.kill


Other parameters of mbox.cfg that are interesting:

M: { 1 }
// M option -> Mode option
// M: { x }
// x=0 -> local mode no NET
// x=1 -> NET mode
// default 0
Z: { 12 } { 127.0.0.1 8000 }
// Z option -> control sending/writing current informations
// Z: { xy } { IP port }
// x=0 -> don't print time stamp (in console screen and in debug file)
// x=1 -> print time stamp ( .... )
// y=0 -> no writing/sending informations to debug file/destination IP
// y=1 -> send informations to destination IP but not in debug file
// y=2 -> write informations to debug file but don't send to destination IP
// y=3 -> write/send informations to debug file/destination IP
// IP port -> destination IP and UDP port where to send informations

Only debug file: Z: { 12 } { 127.0.0.1 8000 }
only send debug to IP: Z: { 11 } { 127.0.0.1 8000 }
Both file and IP: Z: { 13 } { 127.0.0.1 8000 }

L: { 1 }
// L option -> how mbox to menage virtual card(s) with level 0
// ( only for peer(s) who have and can reshare virtual cards but don't want to
use LEVEL 0 card(s) for them self)
// L: { x }
// x=0 -> don't load any virtual cards with LEVEL 0, you can't use them for
your self
// x=1 -> load all virtual cards with LEVEL 0 ,you will be using them for
your self
// default 1

If you run Mbox on a server then you can't use level0 cards
so you have to set:
L: { 0 }


About the cwshare.cfg:

If you don't use a brascet and you must set some other
options after the brascet then don't leave it empty.
Put a zero in it so Mbox knows it's not used.

Example: C: { 127.0.0.1 15000 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13
14 } { 0 } { 0 }

When using Mbox and Newcs on the same box/server then Mbox
can see those cards as local.
But you must make a connection ( C-line in cwshare.cfg) with IP 127.0.0.1.
Only then you will have these cards as local in your Mbox server.


About D line in cwshare.cfg file ...
Now you can set what provids boxids you want to reshare with another peer(s)
- two formats are supported - the normal gbox dline format & Mbox new dline format-

This is standard D line ( gbox format )
=======================
D: { IP { port1 port2 { pass { level1 level2 }}}}


This is my new upgraded D line ( To use for Mbox exchange -Mbox format-)
===============================
D: { IP { port1 port2 { pass { level1 level2 }}}}
{ 0000 } { 0 } send filter
{ 0000 } { 0 } receive filter


D: { IP { port1 port2 { pass { level1 level2 }}}}
{ xxyy !!in hex!!!} { provid-boxid-boxid;provid;provid-boxid; ...!!in hex!!!} send filter
{ xxyy !!in hex!!!} { provid-boxid-boxid;provid;provid-boxid; ...!!in hex!!!} receive filter

for both brascets

xx -> 00 disabled
xx -> 01 allow only this cards for provid to be reshared received
xx -> 02 denied only this cards for provid to be reshared received

yy -> how much provids is in next brascet dont caculate boxids

1st example:
============

D: { IP { port1 port2 { pass { level1 level2 }}}}
{ 0102 } { 0001006A;0001006C-0A0A-0B0B; }
{ 0102 } { 00010080;00010081-0A0A-0B0B; }



{ 0102 } { 0001006A;0001006C-0A0A-0B0B; }

xx is 01 ,ALL cards for (0001006A) provid is SENT to peer AND cards with boxid
0A0A,0B0B for provid 0001006C, ALL others provids(cards) will NOT be sent!!

yy is 02 ,there is only 2 provids in next bracket dont caculate boxids


{ 0102 } { 00010080;00010081-0A0A-0B0B; }
xx is 01 ,ALL cards for (00010080) provid is RECEIVED from peer AND cards with
boxid 0A0A,0B0B for provid 00010081, ALL others provids will be IGNORED!!

yy is 02 ,there is only 2 provids in next bracket dont caculate boxids



2nd example:
============

D: { IP { port1 port2 { pass { level1 level2 }}}}
{ 0202 } { 0001006A;0001006C-0A0A-0B0B; }
{ 0202 } { 00010080;00010081-0A0A-0B0B; }


{ 0202 } { 0001006A;0001006C-0A0A-0B0B; }
xx is 02 ,ALL cards for this (0001006A) provid is NOT sent to peer AND cards
with boxid 0A0A,0B0B for provid 0001006C, ALL others provids(cards) are !!

yy is 02 ,there is only 2 provids in next bracket dont caculate boxids


{ 0202 } { 00010080;00010081-0A0A-0B0B; }
xx is 02 ,ALL cards for (00010080) provid is NOT RECEIVED from peer AND cards
with boxid 0A0A,0B0B for provid 00010081, all others provids will be received!!

yy is 02 ,there is only 2 provids in next bracket dont caculate boxids




NOTICE: MBOX WILL NOT COMPLAIN IF YOU USE OLD D LINE STYLE !!!!!!!!!!!!!



Connecting to newcamd server program Newcs
==========================================

example:
C: { server_ip server_listening_port username password des_key } { x } {
xxxxyyyy:xxxxyyyy;......}
C: { 127.0.0.1 15000 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14 } {
10 } { 0100006a:0100006B;}

[second brascet] -> { x } max. number ecms in buffer ,decimal !!!!!

[third brascet] { 0100006a:0100006B;} is used if you want to change caidprovid
from what newcs detected to caidprovid to use with gboxx protocol so 0100006A
will be 0100006B in gboxx protocol




Resending ECM(s) on timeout interval
====================================
O: { xxxx yyyy }

example:
O: { 4000 2000 }

4000 (4 seconds)-> resend current ecm on boxid if no dcw
2000 (2 seconds)-> wait 2 more seconds for dcw ,if no dcw on time resend ecm(s)
to all boxid's



NDS system ->Resending ECM(s) on timeout interval
=================================================
N: { xxxx yyyy }

example:
N: { 400 200 }

default disabled...


Add more cards for CaidProvid
=============================
X+: { xxxxyyyy:zz;xxxxyyyy:zz; } // zz -> max. is 30 !!!!!

example:
X+: { 0100006A:15; }

With X+ active, for caidprovid:0100006A max. cards for use is 15.



About the 12000.list or the port.list:
You need the 12000.list file to run Mbox with your local
cards!!!
If you are sure that your card can decrypt all Sids then put ONLY this in the
port.list file:

SF: { 0000 }

Now you must make file called "port.list" in
K: path (look your settings in mbox.cfg)


"Port" is newcs port, look into the newcs.xml file and search for
newcamd_port.
Code:
......
12000ort> .......

So the file will be called 12000.list.
If you have 17050then the filename will be 17050.list


Pls use SID pids , CHIDs for Irdeto or G line, because now mbox send only one
ECM and wait response from newcs before it send new ECM.

//this is for forbiden SID pids or Irdeto chids ..
//example
SF: { 04A0 } -> forbiden SID pid -> your card cant decrypt this channel
SF: { 0220 }
IF: { 0203 } -> forbiden Irdeto ChID -> your card cant decrypt this ChID
IF: { 0302 }
G: { 0100006A } -> dont list and reshare this provid from your card if card
cant decrypt that, mbox will just flood newcs with bad ECMs for this provid.


//max forbiden SID pids or ChIDs is 150.
//max G lines is 15.


//OR to enable SID pids or Irdeto chids
//example
SA: { 04A0 } -> enable SID pid -> your card can decrypt this channel
SA: { 0220 }
IA: { 0203 } -> enable Irdeto ChID -> your card can decrypt this ChID
IA: { 0302 }
G: { 0100006A } -> dont list and reshare this provid from your card if card
cant decrypt that, mbox will just flood newcs with bad ECMs for this provid.

//NOTE: YOU CANT MIX FORBIDEN AND ENABLED PIDS.



About the add.data file:

You don't need the add.data file to run Mbox!!!

The add.data file gives you the option to:

- change I,X,O,N line
- to delete running D line
- to add new D line(without filter rules)
- to resend "R" hello msg to all peers while mbox is running.

Write new values in "add.data" file and put it in folder from P:
line. (look your settings in mbox.cfg)

NOTE: Max time to wait before changes take affect is 2
minutes, new values for I,X,O,N will NOT be saved in cwshare.cfg but new D or C
line will be saved.
"add.data" file will be deleted after reading (read add.data.example)
!


#D: { ip { port1 port2 { pass { level1 level 2 }}}} -> remove running D line
D: { ip { port1 port2 { pass { level1 level 2 }}}} -> add new D line without
restarting mbox,new D line will be saved in cwshare.cfg
R ->Resend hello msg to all peers
X: { x } -> Change running X value
I: { x } -> Change running I value
O: { xxxx yyyy } -> Change running timeout intervals
N: { xxxx yyyy } -> Change running timeout intervals for NDS system
C: { server_ip server_listening_port username password des_key } { x } {
xxxxyyyy:xxxxyyyy;......} -> add new C line
===========================================

Here is An example of a working cwshare.cfg and newcs.xml ( you must adjust according to your own set-up )

cwshare.cfg :

I: { 02 }
O: { 4000 2000 }
N: { 400 200 }

M: { xxxxx.dyndns.info { SamePASS of your GBOX }} <-- Same line in your gbox's cwshare, do not change anything here .

Add a similar Cline to read your Local as follows - It depends on your newcs.xml ( explained below -note matching colors- ).
C: { 127.0.0.1 34000 dummy dummy 01 02 03 04 05 06 07 08 09 10 11 12 13 14 } { 0 } { 0 } <-- check above for { 0 } { 0 } , it depends on your card .

your same Dlines from gbox goes here now.


NewCS example : for a local Irdeto card in lower slot of DM ( single slot boxes = lower slot ) Pay SPecial attention to colored parts and how they're matched.. these are the most important that will be used in the Cline we mentioned above.

newcs.xml ( found in /var/tuxbox/config )




lower
sci
600
/dev/sci0
odd
normal
Yes
Yes
No
No
No


0000000000000000
000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000
No
000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000
00000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 000000000000
No
yes
34000
Yes
no
0000
round




No
16000

localhost



20
-1



8080
yes



newcs


newcssam


admin



NewCSpwd
normal
init
console,tcp
normal,init
1001
normal,init


Yes
newcs
01 02 03 04 05 06 07 08 09 10 11 12 13 14

dummy
dummy
127.0.0.1
on
off
No



mpcs
dummy
No
No
No

lower
smargo

0




* Since we chose the port 34000 in our newcs.xml and therefore in our Cline in cwshare .. we must create a file called 34000.list that goes in /var/keys ( try putting the line SF: { 0000 } in this file till you figure out what needs to be put according to above tutorial .. depends on the card you have .

How to config CWSHARE ?

CWSHARE.CFG HOWTO
Originaly by REVOLTE on the Marahibs forum edited by Samot4 and altered with sugestions from Pow.
Cwshare.cfg
This is an example of cwshare.cfg with the most important communication lines:

M: { box1.dyndns.org { 11111111 }}
#
D: { box2.dyndns.org { 5566 5580 { 22222222 { A3 A3 }}}}
D: { box3.dyndns.org { 5566 5566 { 33333333 { A3 A3 }}}}
#
D: { 192.168.1.102 { 5566 5590{ 44444444 { A3 A3 }}}}



The M-line. M: { you’re DNSNAME { you’re password }}
• The DNS name is the name that you did sign up for.
• The password contains 8 numbers/letters 1-9 A-F

The D-line. D :{ DNSNAME { PORT1 PORT2 { password { share level 2 x }}}}

• The DNSNAME is the name the one you are going to share with is using.
• PORT1 is the port you are using yourself 5566.
That port has to opened in your router.
• PORT2 is the port the person you are going to share with is using. This port has to be opened in his router .
• Password, this has to be the same as in his M-line.
• The share levels: is how far you allow the card to be shared. For example A3 A3. The first A3 says how far the local card in this box can be shared. The second A3 says how far the cards in you’re network(=virtual cards that you might get from others) can be shared. (if possible)This shouldnt be put to high,cards shared over 3 will start to cause freezes and caus a lot of unnecessery trafic.The A hasnt got anything to do with the level it simply allows NDS cards to be shared.

You should never use the same code for different boxes !!!!!!.
You can use the same port for several shares.

In the example the last D line is for sharing in house.

Sharing over the net.

With this the example cwshare.cfg from the client would look like this:

M: { box2.dyndns.org { 22222222 }} #
D: { box1.dyndns.org { 5580 5566 { 11111111 { A5 A5 }}}}

The port 5580 is the port open on box2. The second port 5566 is the port open on box1.
11111111 is the code the server( box1) is using in his M line so it has to be in the D line of the client.

Sharing in house:
With this the example share.cfg from the client would look like this:

M: { 192.168.1.102 { 44444444 }}
#
D: { 192.168.1.101 { 5590 5566 { 11111111 { A0 A0 }}}}

In this example the ip internal of the server/ box1) is 192.168.1.101, here I use the ip, because the information is not going over the net.Share is set to A0 A0 because we are not sharing only getting from box1.

Well now everything should work......

If you get a D line from a friend. Please do not show it to others it is for you’re use only.
If you post a backup img. Remove all the information about you’re share’s.
People will just put those lines in there own files and that creates problems!!!!

Dist and level….
This kind of information you can look in the .tmp file of you’re dreambox or in the Gbox center .Or you can use PHPGbox statistics and UDPlog on a pc.
The tmp/ files
share.onl contains info about who is online and who is not. The one’s with a 1 in front is online and the one’s with a 0 is not.

Share.info. In this file you can see how many cards you receive and for which provider. You can also see the levels of the diffrent cards. Level 0 means, the card cant be reshared . The distance is how many boxes there are between the card and you’re box.
Example: dist 1 means someone you are directly connected with has this card.

ignore.list

Is put in var/key file. This file is used to ignore the unused providers . This is important because you can’t have more than 1024 cards. NOTE : When you first start... leave this alone for a while... You can alway experiment with this later!

I-line

When you reach the limit of 1024 cards gbox will set it self back to less cards. Or in a worst case, don't work at all! Normally I is set to 5 , this means you can’t receive cards that are further away than 5 boxes away. You can adjust this you’re self by setting this in you’re cwshare.cfg: Short : The I = is the distance allowed.

I: { 3 }

This means you will not receive cards that are more than 3 boxes/hops away.


X

Lets you control how many cards you will receive for each provider. Normally it is 05, I think u should leave it this way. Or when you have troubles bring it back to f.e. 3. (Don't go any lower then that!)In early versions this value is in dec in later its in hex

X: { 05 }



Y
Here you can block bad cards.Cards theat doesnt have the full package.You actually put the boxid of the box sharing the bad card.This will however block all cards from that box
When you first start off, leave this also alone for a while. You can always experiment with this later!

Y: { 12 34 }

Now the cards from box 12 34 will not be used anymore. Be sure to put a space between the first two and the last two!!!!
Pleas keep in mind, that these Cards you insert over there, are blocked for all guys "behind" you. Useually, this should be used only for Cards with Level = 0. Generally bad cards should be insterted to the ignore.list (with the same care of course!)


G

In this line you can tell the emu to favor known good cards for providers.

G: { 0100006A 1234 }

0100006A = The provider ID, and 1234 the boxid

NOTICE: that if the box ID allready is in the Y line, The G line will not be used!!
By inserting G-Lines you can increase the total number of cards to be used for one provider... i.e. even if you put number of cards to X : 1, you can access much more cards if there are (some of course) BUT... as far as I know, there is no chance to increase the distance for single cards only..


# 01 repeat EMM's
# 00 consider every EMM only once
# 01 restart pid on overflow
# 1* reset ENX on every channel change
# *1 check/reset ENX freezes on FTA
# *2 check/reset ENX freezes on PayTV
# *3 check/reset ENX freezes on FTA and PayTV
# 00 write nothing in atack.txt
# 01 write into atack.txt: password is wrong
# 02 write into atack.txt: ID unknown
# 04 write into atack.txt: IP is wrong
# 08 write into atack.txt: port is worng
# 10 write into atack.txt: share.stat
# 20 create online.log for online/offline logging
# 3F write everything. (combine bits for other combinations)
# 4000 send ecm again after 4 Seconds if no reply.
# 6000 resync decode after 6 Seconds if net decode failed
N: { 00 01 03 1F 4000 6000 }

How to install gbox on a LINUX server

1.create 4 directories
/var/bin
/var/keys
/var/script
/var/tmp


2.put some files
in /var/bin :
gbox86, rename it in gbox, chmod 755

in /var/keys:

cwshare.cfg, chmod755
gbox_cfg, chmod755

in /var/script
gbox_cam.sh,
rename in gbox, chmod 755
remove the lines about AES


3. start/stop gbox


start: /var/script/gbox start
stop: /var/script/gbox stop



4. to have gbox working on boot
in linux debian :
in /etc/init.d :
put /var/script/gbox

execute this command line:

update-rc.d gbox default 19


Now gbox is up and runnig

Lines Definition in CWshare and Gbox.cfg

W line in Cwshare:
The W line decides how your local card shall be used and shared on the network, and goes in cwshare.cfg like this:

W: { 0A 0B 0C } P001 P002 P003 ...

A= Slot number (1 to 8 )
B= How your card shall be used locally (on your own box)
-0= Dont use card
-1= Use card for all Pid's
-2= Use card only for following Pid's
-3= Don't use card for following Pid's

C= How the card shall be shared on the network
-0= Dont share card
-1= Share all Pid's on card
-2= Share only following Pid's on card
-3= Don't share following Pid's on card

P is the Pid's

Example 1: I want my card in slot 1 to be used for all Pid's locally, and to be shared on the network with all Pid's ( 1FFF means all Pid's):

W: { 01 01 01 } 1FFF

Example 2: I want my card in slot 1 to be used locally for all Pid's on card, and DONT want it to be shared on the network at all:

W: { 01 01 00} 1FFF

Example 3: I want my card in slot 1 to be used locally with the following Pids only, and to be shared on the network too with the following Pid's only:

W: { 01 02 02 } Pid1 Pid2 Pid3 ...

Well, the example 3 is the most interesting, and if we all used it in the right way, it would give a good and stable share environment. Why?

I will try to explain:

Lets say i have a package with 5 channels. I only have a subsription to 3 of these channels, so 2 channels dont open with my card.
Open channels: Pid1, Pid2, Pid3
Scrambled channels: Pid4, Pid5.

There is no need to use my card or share my card with Pid's 4 and 5 since they dont open with my card!

So i would do a W line like this in my cwshare.cfg:

W: { 01 02 02 } Pid1 Pid2 Pid3

The easiest way to see Pid numbers for the channels, is by zapping and then pressing "Quick info" In Gbox Suite and look for the value CaPID for each channel.

Example: CaPID: 0x0021

The Pid number in this case is 0021.

So it would be entered like this:

W: { 01 02 02 } 0021

PS: Max 32 Pid's/Sid's allowed (32 of each) allowed

PS: This explanation goes for the S line aswell. S line goes S: { .. .. .. } and instead of Pid's, Sid's are used!

*Thanks to MasteR for corrections!*

Update (thanks to @emilio29):

Easiest way to see Pid's: In GboxSuite look in "Quickinfo".
Easiest way to see Sid's: Press "Menu", then "Information", then "Streaminfo". Look in the field "Service id" (this value is already in hex).

You get the best result using Sid's (S line), since some of the Pid's are shared!


V line in Gbox_cfg
V: { F0 00 } # no slots
V: { F0 10 } # slot 1
V: { F0 20 } # slot 2
V: { F0 30 } # 2 slots
V: { F0 35 } # 2 slots + port com
V: { F0 31 } # Sc8in1
V: { 00 05 } #Dbox2 multicam
V: { 00 07 } # Dbox2 multicam slot 1+cardreader com

G line in Cwshare:
The G line is used to force the reception of a specific card even if you received all cards that you set up by the X parameter.
So, it is used to force the card that gbox can't get usually itself.
The syntaxe of the G line is :

G: { 01000081 ZZAA }

G: { prov_id box_id }

N line in CWshare
# 01 repeat EMMs
# 00 consider every EMM only once

# 01 restart pid on overflow
# 10 reset ENX on every channel change
# 01 check/reset ENX freezes on FTA
# 02 check/reset ENX freezes on PayTV
# 03 check/reset ENX freezes on FTA and PayTV

# 00 write nothing in atack.txt
# 01 write into atack.txt: password is wrong
# 02 write into atack.txt: ID unknown
# 04 write into atack.txt: IP is wrong
# 08 write into atack.txt: port is wrong
# 10 write into atack.txt: share.stat
# 20 create online.log for online/offline logging
# 3F write everything. (combine bits for other combinations)

# 4000 send ecm again after 4 Seconds if no reply.
# 6000 resync decode after 6 Seconds if net decode failed
N: { 00 01 03 00 2000 5000 }

i hope this will help you
the colors in the d line are the same as above
you can change the values if you want to
like the attack log if you have a dream 500 the log file can flood youre box
so set the atack numbers only on what you would like to see like 04 means that youre peers ip is wrong
then as you can see you can also change the value for sending ecm and resync decode


D nad M line in CWshare:
the dline is the line that makes it possible for the client box to logon to the other box
ofcourse is the first one in the living and the second one in the bedroom

for example
the cw from the LIVINGROOM go's like this

# cwshare.cfg --- dbox1 --- Internet und Lokales Netzt
#
# ip number password
M: { 192.168.2.10 { 2B1C1D7C }}
#
# Internet Friends port range password cod
D: { 192.168.2.20 { 2244 4422 { 98765432 { A3 A3 }}}}
#
#
# allow maximum 06 share level for recieved card data
I: { 03 }
#
# Send ECMs at maximum 5 cards (please use this as default)
X: { 09 }
#
# FOR NLINE=
# 01 repeat EMMs
# 00 consider every EMM only once
# 01 restart pid on overflow
# 1* reset ENX on every channel change
# *1 check/reset ENX freezes on FTA
# *2 check/reset ENX freezes on PayTV
# *3 check/reset ENX freezes on FTA and PayTV
# 00 write nothing in atack.txt
# 01 write into atack.txt: password is wrong
# 02 write into atack.txt: ID unknown
# 04 write into atack.txt: IP is wrong
# 08 write into atack.txt: port is worng
# 10 write into atack.txt: share.stat
# 20 create online.log for online/offline logging
# 3F write everything. (combine bits for other combinations)
# 4000 send ecm again after 4 Seconds if no reply.
# 6000 resync decode after 6 Seconds if net decode failed
N: { 00 01 03 3F 3000 5000 }

ok so this is ths cw share file
what does this dline meens
the ip number : 192.168.2.20 is youre friend thats what is says
so youre friend is alowed to logon to the livingroom box
the ports in the living are 2244--4422
2244 is used by the box in the livingroom
4422 is used by the box in the bedroom
so the bedroom logs on thru port 2244 on the living
and vice versa

the pasword needs no explanation i think

the code:
A meens you let nds go thru without A you dont share nds signals
1,2,3,4,5,6,7,8,9 meens that you share it a specific amount of boxes
so if you put A1 A! then it go's no further then 1 box and so on


so let me put this simple

#livingroom :
M: { 192.168.2.10 { 45456565 }}
#
#
D: { 192.168.2.20 { 2244 4422 { 98765432 { A3 A3 }}}}
#
I: { 03 }
X: { 09 }
N: { 00 01 03 3F 3000 5000 }
--------------------------------------------------------------

#and the bedroom:

M: { 192.168.2.20 { 98765432}}
#
#
D: { 192.168.2.10 { 4422 2244 { 45456565 { A3 A3 }}}}
#
I: { 03 }
X: { 09 }
N: { 00 01 03 3F 3000 5000 }

I line In CWshare:
Just some explanation for people who do not yet get this matter

the I line determines the maximum distance of cards which you obtain
That is the number of boxes that you have to go thru to get at the card to come
example: Jan have card A and is the pear of piet now you are also a pear of piet
therefore to go to Jan and use its card you must go by piet
piet is then the first distance and jan then the second distance

This way i think its clearly enough for everyone

As from dist 3 the quality of the card becomes more badly
since there is not higher shared than level 5 it is entirely
unnecessary to put it higher as level 5

X line in CWshare:

The X line is the line which determine the number of cards you get answers from
the ammount of cards you address to give you a color on your screen
this card provide you then with the correct data

therefore e.g. X {07} that means that there to 7 cards asked for an answer for the correct data

Step by Step Gbox server setup on Dreambox

Before I start to write the How to I decided to describe first the necessarily steps to build a gbox server. So don't except How to with all Details. The questions about gbox server will show which details will be needed.




1. Get the files
2. Put the files in the right folders
3. Make the needed configuration
4. add and exchange dlines
5. control your gbox
6. possible errors and reasons


1. First download all files from the following link
Gbox2.1b

2.Extract the files and you will see also the path where the files should be put
//var/bin => gbox
//var/keys => cwshare.cfg,gbox.cfg,softcam.cfg
//var/script => gbox_cam.sh
//var/tuxbox/plugins => egboxcenter.cfg,egboxcenter.so,gboxsuite.cfg, egboxsuite.so, gbv.cfg,gbv.ident,gbv.so

Use a Ftp program to put the files in the folders. I prefer flashfxp. After you had put the files in the folders. Make CHMOD changes for the following files. You can make the CHMOD changes by using the right mouse button (FLASHFXP) on the file and selecting Attribute (CHMOD).
//var/bin/gbox => CHMOD 755
//var/keys => cwshare.cfg => 644
//var/keys => gbox_cfg => 644
//var/scripts => gbox_cam.sh => 755

3. Coniguration

You must made only individual changes to cwshare.cfg and gbox_cfg

CWSHARE:

This file is responsbile for communication between the peers.
Following lines should be inside this files
M: => Adress of your gbox
I: => Configuration about till which distance cards you allows to get
X: => Configuration abotu how many of the same card you allows to get
D: => Communication line between the peers
N: =>
W: =>


How should the lines be set:

M-LIne

M: { your.dyndns.org { Password }}

=> Password: You can only use 0-9 and A-F for setting password. My suggestion is don't use a very very easy password like 12345678 or AABBCCDD or ABCD1234, so a lot of people makes that and this can be a reason for an error, if you start the gbox. More details at the end.



I-Line

I: { 03 }

This is the selected value most gbox user set for their I-Line. Because with this configuration you only accept cards till Dist3. Cards with Dist4 and Dist5 are not good for sharing and gettings keys. If you have later more peers you can set the value to 02.



X-Line

X: { 10 }

This is a value should experiment a little bit which value is the best for your gbox server. As you know with this value you set a limit to the number of same cards. 0A, 10, 08 this are the most used values.



N-Line

N: { 00 01 03 3F 4000 6000 }

I will write more details to this line. Use the N-Line given above ( its my N-Line)



W-Line

W: { 01 01 01 } 1FFF

I will write more details to this line. Use the N-Line given above ( its my N-Line)


D-Line

This is the most importan Line

D: { other.dyndns.org { Port1 Port2 { Password { A5 A5 }}}}

other.dyndns.org => the dyndns of your share peer
port1 => your port number using for gbox
port2 => port number of you peer
Password => password of your peer
A5 A5 => Share Level for Local and Virtual Cards

You will get this dline every time for your peer. So the only thing you had to do is, to put your port number instead of port1 and add it in your cwshare.cfg. The Dline you give to your peer is the the same but with your dyndns, password and your port number is port2.

D: { own.dyndns.org { Port1 ownport { own password { A5 A5 }


GBOX_CFG

In your gbox_cfg file you have following lines

Z: { 01 12 } dream ip 8024

G: { 03 }

C: { 01 }

M: { 01 }

A: { 00 }

U: { 01 }

H: { 01 }

T: { 00 }

O: { 03 } dream ip

L: { 00 } dream ip 8029

W: { 00 00 } 9600

V: { F0 35 } => configurations for reading slot and com-ports


V: { F0 00 } nothing
V: { F0 10 } slot 1
V: { F0 20 } slot 2
V: { F0 30 } both slots
V: { F0 35 } both slots + com ports
V: { F0 05 } only com ports
V: { F0 31 } Sc8in1
V: { 00 05 } Dbox2 multicam


I will made later a detailed description for this file. The informations above are taken from my gbox_cfg



4. Add and exchange Dlines


After ending configuration you can now exchange dlines

M: { own.dyndns.org { password }}
# Internet Friends port range password cod
I: { 2 }

X: { 0A }

N: { 00 01 03 3F 4000 6000 }

W: { 01 01 01 } 1FFF

D: { other.dyndns.org { yourport otherport { otherpassword { A5 A5 }}}}

Be carefull if you add dlines it must the same like above. No more spaces or less spaces



5. Control Gbox and peers

Gbox Center and Gbox Suite are plugins to have Informations about your peers, Cards, Distance and Level Share and how many cards do you have for each provider

You can access to this plugins

Blue Panel => Plugins => Gbox Center or Gbox Suite



6. Error and Reasons


If your gbox is not working ( you will see it if you go to: Blue Panel => Plugins => Gbox Center => Gbox Share Center => Peer Status => Message that share is not found, check if gbox is running )
Then check following
1. Internet Connection
2. Correct format of dlines ( Spaces, password (0-9,A-F) )
3. Passwords of the dline ( so if two peers use the same password they will get the same Box ID and two same Box ID in one Gbox Server is not working)

4. Some Cards needs special configuration to share them ( Sky Uk, Nova etc)

G and Y Line

G and Y line very simple and can make your server much better

G Line

A standard g line is:

G: { 05022600 ABCD }


This means the BoxID ABCD is prever for provider 05022600 ( TPS 13E ).
Its interest for Boxids there are often pay for special events.....
Also interest is that when u have a x5 and u have eg 7 G lines from one provider u get it 7 times (when all are online). so u can get a small x value for all providers and get a higher value for special providers.

Y Line

the y line blocks Boxids.

Y { AB CD }

In this case the boxid ABCD will be blocked. Interest when u have freezers or fake cards form a special boxid. u can also block level 0 share.

u see the boxid in the ecm info as prov:ABCD. when u have a plugin for gbox its very easy to find the boxid.

Some important explanations and tips

when a card dont decode all channels and you dont say this gbox with a W: or S: Line in cwshare.cfg you freeze the complete cs with your card/s !!!

Level 0 Cards -->

I think its the wrong way to Add Level 0 Cards to cwshare because this is
only move the Problems to another place ! The right way is when you look from wich peer is this Level0 Card and you contact them and say they do A2 A2 at your D line ! When the Level0 Card also exist after WARN the peer again and say to him when not better you delete his line ! This is the best way to execute this Problems !!!
Exceptions.:

- Sometimes it can be OK when a Specially rare Card comes from your Peer and when they say not more than A1 because more/reshare is Bad for the Card

-If a user at distance 2 from me, has {A2 A2} then the user at distance 1 will receive his cards with level 1. When he passes them to me they will be level 0. This is not a bad thing. They may be perfectly good. It just means I cannot re-share them
------------------------------------------------------

A2 A2 - NOT MORE !!! -->

This is the best entry at all Peers and for all users enought ! More is BAD and makes instability, freezes and BAD Network Performance !!!
Important is NEVER A5 A5 !!!
-----------------------------------------------------

Local Cards -->

Every Peer likes have a Local Card most of time all other is VERY BAD ! Check this everytime !!! You will do nothing only use the Peers Checker from the Gbox Share Control ( THX to Black64 !!! )
And also its a Tip - Share only Full Cards because you cant sure if the owner from a Not Full Card makes W or S - Line ( This says gbox what channels the Card encrypt and what not ) everytime !
EXCEPTION.: Some Cards with many Channels like NDS or TPS its the best way when the Peer share not all channels because otherwise its too much for the card in cs and than it freez This can be also set by S or W line in cwshare.cfg
Also good option is to Overclock the Card for support more users.
No Share with Virtuall Cards like Anaconda or K3 or ... !!!
EXCEPTION.: When you are sure the Peer is have the right files for his Virtuall Card than its OK to share
----------------------------------------------------

Ignore list -->

Note that when you block Providers that you dont have but they are active the Peers from you dont receive it from you also !
-------------------------------------------------------

Ident.list -->

One from the Important things that you need for Good working because here you can see what are good Providers/Cards and what Bad
Here in the Forum you can use my Ident.list when you like and help the community too that we always Up2date with the list entrys/changes
-----------------------------------------------------------

I: in cwshare.cfg -->

The best here is I:02 !!! When you use gbox 2.1b and receive Distance3 Cards but you have I:02 than you can use the patched I:02 Version from the UPC here !!!
But normally its recommend to work with the newest Version ( V. 2.25 )
-----------------------------------------------------------

X: in cwshare.cfg -->

Between X:05 and max X:0A !!! When you beginn with X:0A and have more than 900 Cards set it to X:09 ! When you have after this also more than 900 Cards set it to X:08 ! Et cetera
Attention the entrys work with Hexadezimal so X:10 is not meaning max 10 Cards from one Provider, in Numbers X:10 is --> 16 Cards !!!
-------------------------------------------------------------

Some small Tips from me ...

NEVER Handle WITH PROGRAMMS @ BOX direct USE only PC Programms !!!
gsuite,center ... all will crash sometimes and give from time to time false Infos !!!
-------------------------------------------------------------

Its a good think when you make a excel list with all your Peers and write behind them what Cards they local have and his email Adress
When you have bad peers that you have deleted make it in a seperate list and give them a extra Info with your Commentar why you have delete him. So you can be better sure that you dont share again with bad peoples.
Its recommendable when you security this files with for example Steganos Save or some other Crypt Programms that no one other can read this Details !


.................................................. .................................................. ...
These are BASICS !!! When anybody is meaning there was some not correct or have also good Tips let me known here and i can update this Info --> This is only for Beginners of gbox that he can see what is Important and how works the think ! I am also NOT a Professional i make this for Hobby and will only do the best for the Community !!! I will NEVER say I am the Boss ore some else !!! Thanks for understand

Some Basic definitions in Gbox

Share-configuration
The template is:
Server
M: { { }}

D: { { port_from port_to { { }}}}
Client

M: { { }}

D: { { port_from port_to { { }}}}
=> IP-address of the box. If this is going over the internet, use the WAN-IP-
address!!
=> Encryption-key of the box
=> The IP- or DNS-address of the person you want to connect to.
=> Port you want to use on the box. If this is going over the internet, this
needs to be forwarded if behind a router! UDP!!
=> Port that the other sided uses on the box.
=> Share-level for the LOCAL cards.
=> Share-level for cards you receive from others.
Assuming the server has the IP-address 192.168.1.10 and the client 192.168.1.11:
Find the file /var/keys/cwshare.cfg and alter the following lines accordingly:


Server

M: { 192.168.1.10 { 1234ABCD }}
D: { 192.168.1.11 { 8019 8020 { DCBA4321 { 5 5 }}}} # Client
Client
M: { 192.168.1.11 { DCBA4321 }}
D: { 192.168.1.10 { 8020 8019 { 1234ABCD { 5 5 }}}} # Server
This will off-course work over the internet! Use the WAN-IP-address or Just use a DynDNS or no-
ip address... Looks cooler..



================================================== ===========
Analyzing logging
So, you've got things sorted, and you want to take a look at what's what. Well, actually, there are
6 files to be viewed, of which 4 are permanent:
• /var/tmp/share.info => shows the cards you receive from others
To make things easy, I took myself as an example. I did this on my dreambox:
/tmp > cat share.info
CardID 0 at 192.168.2.102 Card 0100006A Sl:3 Lev:0 dist:1 id:87F4
CardID 1 at 192.168.2.102 Card 0100006B Sl:3 Lev:0 dist:1 id:87F4
CardID 2 at 192.168.2.102 Card 0100006C Sl:3 Lev:0 dist:1 id:87F4
CardID 3 at 192.168.2.102 Card 0100006D Sl:3 Lev:0 dist:1 id:87F4
CardID 4 at 192.168.2.102 Card 06260000 Sl:11 Lev:0 dist:1 id:87F4
OK, to break things down I'll use the first line:
CardID 0 => ranking-number of the card the way they are sorted... Alphabetically
o
on Card-number.
at 192.168.2.102 => IP-address of where they are coming from
o
Card 0100006A => Card-number. This is how the card is identified
o
Sl:3 => Displays the slot the card is in at the provider, when run on a Linux-PC
o
up to 18 has been seen.
Lev:0 => Amount of hops I'm allowed to reshare. Zero.
o
dist:1 => Amount of hops the card is at. In this case: 1.
o
id:87F4 => Identification-number for gbox that is providing the card.
o
• /var/tmp/share.log => Same as share.stat, only that this displays the real-time data.
• /var/tmp/share.onl => shows who's on-line
Again, I'll use myself as an example:
/tmp > cat share.onl
1 192.168.2.102 192.168.002.102 87F4 2.01
1 => 1 is on-line, 0 is offline.
o
192.168.2.102 => The entry you use in cwshare.cfg.
o
192.168.002.102 => The way gbox translated cwshare.cfg to an actual IP-
o
address. See the 002 ?
87F4 => Identification-number for gbox on the other end.
o
2.01 => Version-number of gbox on the other end.
o
• /var/tmp/share.stat => Same as share.log, only that this displays the stats over the
entire running-time, and of the last 5 minutes.
Hello_I/O=> Number of hello's or "handshakes" between 2 peers.
o
ECM_I/O/F => ECM received (In), sent (Out) and Forwarded by gbox.
o
CW_I/O/F => Control Words received (In), sent (Out) and Forwarded by gbox.
o
Control Word is the reply to an ECM request.
GSMS_I/O => Messages received (In) and sent (Out) and by gbox.
o
loc_up and loc_down => LOCAL Network traffic. (Probably filters defined by the
o
internet standard, 10.x.x.x / 127.x.x.x / 192.268.x.x / 169.254.x.x)
inet_up and inet_down => Network tracfic in and out of internet. (Probably
o
every other IP-addres different from what I mentioned 1 point before?)
• atack.txt => Shows a misconfiguration or someone that is trying to connect to you
without being authorized to do so.
An example. On my server I mutilated the key for the client (that means the line starting
with D: . On the client the atack.txt is created and filled with a number of messages:
ATACK ALERT: from IP 192.168.002.102 port 3101 PASSWORD IS WRONG
o
EDB2097E (32) Sun Aug 7 16:32:09 2005
This means that someone it trying to connect using a wrong password.
I then remove the server completely out of the config:
INTRUDER ALERT: IP 192.168.002.102 Port 3101 (PASS 2346A4B2 ID 87F4
o
unknown) Sun Aug 7 16:40:50 2005
You see the difference?
goneOFFLINE: BAD IP|PORT (DynDNS Peer1) Actual IP Peer1/Localport (IP-
o
address from local DNS Resolve/Localport) Tue Aug 23 12:55:02 2005
This message says that the actual IP-address off the Peer doesn't match with
what gbox thinks it should be.
• Debug.txt => Can take all message generated by gbox. Depends on what you put after
Z: in the file gbox_cfg
->HelloL to => Initial request to every "D:-line" in cwshare.cfg
o
->Hello1 to => Second request if first not answered to (quickly enough)
o
->Hello2 to => Third request if first not answered to (quickly enough)
o
->HelloR to => I think this means Reconnect to peer if timed out? Anyone?
o
->HelloW to => Don't know. Anyone?
o
->HelloS1 to => Don't know. Anyone?
o
->Here? to => Repetitive request every x seconds to see if peer has come on-
o
line.
<-Hello from => Reply to Hello L/1/2/R from Peer, Or first request after Peer
o
reboot? Anyone?
<=Hello from => Don't know. Reply is received in the same millisecond as "<-
o
Hello from". Anyone?
->Hello to => Reply to "<- Hello from".
o
||CW (->1) blocked from Peer1 to Peer2/GboxID Peer2 => Don't know
o
actually. Anyone?
<>ECM (1->1) from Peer1 forwarded to Peer2 (GboxID Peer2 )
o
<>CW (->1) from Peer2 forwarded to Peer1 => Here you see a request being
relayed to someone else, and the answer to that request. In (1->1), the first "1"
stands for the slot the card is in at the supplier, "->1" stands for the amount of
hops the message has to travel to that supplier. In (->1) "1" stands for for the slot
the card is in at the supplier.
<-ECM (1<-) received from Peer1
o
->CW (->1) send to Peer1 (527 ms) => This is a request from Peer1 to a local
card, the reply and the time it took to read the card and supply the key.
dbox2 Peer1 is not responding 6 times => Well, that says enough I think?
o
goneOFFLINE: Removing Peer1 from list, seems offline => Sets Peer1 from
o
1 to 0 in share.onl, after not responding 6 times.
• online.log => Shows the coming and going of peers. Creation of this file depends on the
line N: in cwshare.cfg
comeONLINE : Welcome PEER1 IP xxx.xxx.xxx.xxx/ Sun Sep
o
4 16:22:45 2005 => PEER1 comes online
goneOFFLINE: Removing PEER1 from list, seems offline Sun Sep 4
o
17:45:39 2005 => PEER1 doesn't respond anymore
IP update : PEER1 was xxx.xxx.xxx.xxx now xxx.xxx.xxx.xxx Sun Sep 4
o
17:45:53 2005 => PEER1 has a new IP-address
comeONLINE : Welcome PEER1 IP xxx.xxx.xxx.xxx/ Sun Sep
o
4 18:01:05 2005 => PEER1 is back on-line again!

Credits go To Anakin

Gbox Cfg by cuba
GBOX_CFG

In your gbox_cfg file you have following lines

Z: { 01 12 } dream ip 8024

G: { 03 }

C: { 01 }

M: { 01 }

A: { 00 }

U: { 01 }

H: { 01 }

T: { 00 }

O: { 03 } dream ip

L: { 00 } dream ip 8029

W: { 00 00 } 9600

V: { F0 35 } => configurations for reading slot and com-ports


V: { F0 00 } nothing
V: { F0 10 } slot 1
V: { F0 20 } slot 2
V: { F0 30 } both slots
V: { F0 35 } both slots + com ports
V: { F0 05 } only com ports
V: { F0 31 } Sc8in1
V: { 00 05 } Dbox2 multicam

Instead of dream Ip you must the the IP of your PC. And for make it possible that your programmer is read you must use following line as described
V: {F0 05 }


Thanks to Cuba and Ethereal.

Howto Avoid Attacking on Linux server Using Firewall

Actuallly i have been sick from people who tells u that he had a local and then u discover that he has n`t or has a fake one.....

so what to do....
asks him gently Plz delete my d-line...( but the guy still adding u and cozing attacks.....

the system gives u alert....


Adding the { A0 A0 } Share level is not affective any more like before espicially after gbox version 2.25c , 2.1c which can take ur { 0A } level and reshare it to any level he wants....


so what is the solution......?

After many searchs in the net i found some Linux geeks who using the firewall of the Linux system
as a protection for thier PCs from hacker....

Few commands will resolve this problem....
remember only for gbox -- cccam --Linux servers
 
iptables -L # means list the Rules that included in the buffer

iptables -F # flush all the Rules that u added before and makes the Firewall Accept All

Ex : iptables -A INPUT -s Someone.dyndns.XXX -j DROP




this will add a rule in the firewall system to Kill all the incoming Requests ( INPUT ) from the alais { Someone.dyndns.XXX }

and here is a the whole story from the Ubuntu Website

Hope i`ve been usefull

Useful Telnet and CLI commands for Dm and Linux servers

When you Telnet your box or make a SSH connection shell to your Linux server, these commands are useful for you:
1-Show me who is online, which IP and which Gbox Version is running:
cat /var/tmp/share.onl

2- Show me all Distance 1 cards:
grep "dist:1" /var/tmp/share.info

3- Show me all Distance 1 cards and resolve the Provider ID:
for i in `grep 'dist:1' /var/tmp/share.info | awk '{print $6}' | sort` ; do grep "^$i" /var/keys/ident.info ; done

4-remove the Windows carriage returns ^M on Textfiles:
tr -s "\r" "\n" < winfile > unixfile

5-Showing the ident.info file in a nice way:
first CD to /var/keys
then:
cat ident.info | cut -c 1-9,19-196 > ident.info.new

and you will see the providers lije this example:
01000000;S0 - Mediaguard CAID
01000002;(Old)S1 - Orbit (1W/26E)
01000003;(Old)S1 - Canal+ France (19E)

6-With this command, you can also see if gbox process is running:
ps -ef

7- To start cs2gbox:
cd /var/bin/
./cs2gbox &

8- To start gbox:
cd /var/bin/
./gbox&

9- To start cs2gbox and gbox together in Gemini:
/var/script/gbox_cam.sh start

10-To stop cs2gbox:
killall cs2gbox

11- To stop gbox:
killall gbox

12- To chmod binary:
chmod 755

13- To see number of cards from a peer :
cd /tmp/
grep share.info | wc -l

14- To see cards from a peer with distance and level:
cd /tmp/
grep share.info

15- To see peer status:
cd /tmp/
more share.onl
(Lines beginning with 1 are online peers, Lines beginning with 0 are offline peers)

16- To see number of cards with level X where X = number
cd /tmp/
grep Lev:X share.info | wc -l

17- To see number of cards with level X for a certain peer where X = number
cd /tmp/
grep share.info | grep Lev:X | wc -l

18- To see number of cards at distance X where X = number
cd /tmp/
grep dist:X share.info | wc -l

19- To see number of cards with distance X for a certain peer where X = number
cd /tmp/
grep share.info | grep dist:X | wc -l

20-rebooting your server:
reboot

21- changing your server login password (Very important):
passwd

22-For editing files:
vi
example:
vi /var/keys/cwshare.cfg

How to Irdeto2 Nova cards

The Problem
gbox needs some tweaking to handle Irdeto 2 efficiently. Some known Irdeto 2 problems are
1-Nova Freezing
2-Irdeto 2 cards refusing to decrypt on fast zapping
3-Long response time to ECM

There are 2 things that can be done to drastically improve the performance of Irdeto 2 cards.
1-Creating an ignore CHID list and adding it to /var/keys/ignore.list (Every Irdeto 2 owner MUST do this)
2-Overclocking the DM slots (Not everyone will want to do this, but it is a very useful technique)

The gboxt sample below shows what gbox used to do with my card before I created the CHID list
==== Irdeto ECM on CaID 0x0604, pid 0x054D ====
prov:00, chid: 0026
==== Irdeto ECM on CaID 0x0604, pid 0x054D ====
prov:00, chid: 0026
card 1 response in 180 ms
==== Irdeto ECM on CaID 0x0604, pid 0x054D ====
prov:30, chid: 004E
card 2 response in 200 ms
==== Irdeto ECM on CaID 0x0604, pid 0x054D ====
prov:30, chid: 004E
card 1 response in 184 ms
==== Irdeto ECM on CaID 0x0604, pid 0x054D ====
prov:00, chid: 005D
card 2 response in 186 ms
ecm buffer full !!!
ecm buffer full !!!
ecm buffer full !!!
ecm buffer full !!!
ecm buffer full !!!
==== Irdeto ECM on CaID 0x0604, pid 0x054D ====
prov:00, chid: 005D
card 1 response in 184 ms
ecm buffer full !!!
==== Irdeto ECM on CaID 0x0604, pid 0x054D ====
prov:00, chid: 0087
card 2 response in 183 ms
==== Irdeto ECM on CaID 0x0604, pid 0x054D ====
prov:00, chid: 0087
card 1 response in 183 ms
==== Irdeto ECM on CaID 0x0604, pid 0x054D ====
prov:00, chid: 009B
card 2 response in 185 ms
==== Irdeto ECM on CaID 0x0604, pid 0x054D ====
prov:00, chid: 009B
card 1 response in 250 ms
CW0: 87 7F C7 95 C9 89 D5 72
CW1: 9F 25 5C 48 2A C0 B8 75
===============================================

All the above output is after zapping to just 1 channel!!! As you can see my card attempted to decrypt the channel on CHID 0026, 004E, 005D, 0087, and 009B. With each attempt needing about 180ms. So gbox finally decrypted the channel after 180*6=1080ms. The good news is that this can be solved. The bad news is that it requires some effort from Irdeto 2 card owners.

The gboxt sample below show what gbox is doing with my card after I created the CHID list
==== Irdeto ECM on CaID 0x0604, pid 0x054D ====
prov:00, chid: 009B
==== Irdeto ECM on CaID 0x0604, pid 0x054D ====
prov:00, chid: 009B
card 1 response in 248 ms
CW0: D6 FF 56 74 3F 94 37 8E
CW1: FE F6 9B E9 AB 3E B6 01
===============================================

The card only attempted to decrypt the ECM with the CHID the card can handle, and so the response time was 248ms. Thats almost 1/4 from the original response time.

The Process To Create CHID list
1-Download the attached file (Irdeto CHIDs.txt), this file includes most if not all known Irdeto CHIDs. To make your card more efficient you need to tell gbox to only send ECMs to your card with the CHIDs your card can handle.
2-Start gbox
3-Zap to EVERY channel that your card is supposed to decrypt
4-After every zap, wait until the channel is decrypted then open the file called ecm.info.
There are several ways to do that:
a-From telnet issue the following command "more /tmp/ecm.info"
b-From gbox center go to G-Box EMU Center --> ECM Information

This is what ecm.info normally SHOULD look like
==== Irdeto ECM on CaID 0x0604, pid 0x054D ====
prov:00, chid: 009B
CW0: E4 A6 A6 55 C5 32 6A 70
CW1: 22 70 97 31 BC 33 D8 15
decode:slot-1
5-Make sure in ecm.info that the decode is from your slot. so decode:slot-1 or decode:slot-2. If decode:Network then this WILL NOT WORK and I'll explain why later
6-If decode is slot-1 or slot-2, then the next thing is to check the second line in ecm.info. In this line the CHID of the channel is written. In the example above the CHID is 009B.
7-Open the attached file (Irdeto CHIDs.txt) and comment out the CHID. So in the example above I'd do the following
#I: { 00 9B }
8-Repeat steps 4-7 for EVERY channel that your card is supposed to decrypt
9-When you are done with all the channels, you are left with the correct CHIDs for your card.
10-Copy the contents of your updated Irdeto CHIDs.txt file and paste them in /var/keys/ignore.list (Together with your normal G list in ignore.list)
11-Reboot gbox with updated ignore.list containing CHID list
12-Zap again to every channel that your card is supposed to decrypt, and make sure the channels are still being decrypted by your card (decode:slot-1 or decode:slot-2). If a channel won't decrypt with your card, then you made a mistake in your CHID list, and need to start again with no CHID list in ignore.list and recheck the channel.
13-You're done, and have drastically improved the reponse of your card and helped the network.

Important Information
1-Nova Greece CHIDs are 0002, 0003, 0014, 0015 (So if you are a Nova Greece owner just copy and paste the contents of the attached file "Nova Greece CHIDs.txt"
2-Nova Cyprus CHIDs are 0065, 0066, 0068, 0069
(So if you are a Nova Greece owner just copy and paste the contents of the attached file "Nova Cyprus CHIDs.txt"
3-For all other Irdeto 2 providers you need to do the above process as I explained. You cannot take your friends CHID list just because they have the same card.
Here is why this is the case
I have an Irdeto 2 card for rule 9 Arabia. My card can handle CHIDs 001C, 001D, 001F, and 0021. However a friend on my network also has the same card but his card can handle different CHIDs, If he had just used my CHID list, his card would not have decrypted ANY channel.
4-If you add more channels to your sub (upgrade your subscription) or order any PPV events such as Home Cinema then whenever you order an event you need to repeat the process for the newly added channels to ensure you are not ignoring the CHIDs
5-It is very important to check EVERY channel your subscription can handle before creating the CHID list and after creating the CHID list and ensuring that decode is one of the slots

The process takes about 20 minutes with a rule 9 Full subscription. But the results are drastic, so I advise every Irdeto 2 owner to do this.


The Process To Overclock your card
Irdeto 2 cards run at 6.00MHz, but can be overclocked to run at 7.8MHz with no problems

BE VERY CAREFUL WITH THE BELOW PROCESS. I'M NOT RESPONSIBLE IF YOU DAMAGE YOUR CARD

1-Open gbox_cfg
2-Add the following to your gbox_cfg file
# For overclocking freaks, Clocking internal STB04xxx slots with:
# 1=7.80MHz 2=6.30MHz 3=5.25MHz 4=4.50MHz 5=3.94MHz 6=3.50MHz 7=3.15MHz
# Irdeto works fine on 7.8MHz, all other fine on 6.30MHz or 5.25MHz
# The Dream has not a clean clock signal, some cards that are sensitive will
# refuse to work even on 3.5MHz, thats why 3.15MHz is the default value there.
# On other STB04xxx recievers the same cards work with 6.30MHz
#
F: { 51 } 01 # Lower slot running Irdeto 2 card at 7.8MHz
F: { 52 } 01 # Upper slot running Irdeto 2 card at 7.8MHz
3-Save the file and restart gbox

Important Information
1-Only overclock the slot with the Irdeto 2 card, as overclocking a non Irdeto card to 7.8MHz can permenantly damage your card
2-Read this well
# For overclocking freaks, Clocking internal STB04xxx slots with:
# 1=7.80MHz 2=6.30MHz 3=5.25MHz 4=4.50MHz 5=3.94MHz 6=3.50MHz 7=3.15MHz
# Irdeto works fine on 7.8MHz, all other fine on 6.30MHz or 5.25MHz
# The Dream has not a clean clock signal, some cards that are sensitive will
# refuse to work even on 3.5MHz, thats why 3.15MHz is the default value there.
# On other STB04xxx recievers the same cards work with 6.30MHz
#

There you go. If you successfully do process 1, then you have made a drastic improvement to your card response time, and have helped your peers. Process 2 is just an extra and I only advise experts and Nova card owners to attempt to do it.

Hope that was helpful.

Irdeto chid's
I: { 00 01 }
I: { 00 02 }
I: { 00 03 }
I: { 00 04 }
I: { 00 05 }
I: { 00 06 }
I: { 00 07 }
I: { 00 08 }
I: { 00 09 }
I: { 00 0A }
I: { 00 0B }
I: { 00 0C }
I: { 00 0D }
I: { 00 0E }
I: { 00 0F }
I: { 00 10 }
I: { 00 11 }
I: { 00 12 }
I: { 00 13 }
I: { 00 14 }
I: { 00 15 }
I: { 00 16 }
I: { 00 17 }
I: { 00 18 }
I: { 00 19 }
I: { 00 1A }
I: { 00 1B }
I: { 00 1C }
I: { 00 1D }
I: { 00 1E }
I: { 00 1F }
I: { 00 20 }
I: { 00 21 }
I: { 00 22 }
I: { 00 23 }
I: { 00 24 }
I: { 00 25 }
I: { 00 26 }
I: { 00 27 }
I: { 00 28 }
I: { 00 29 }
I: { 00 2A }
I: { 00 2B }
I: { 00 2C }
I: { 00 2D }
I: { 00 2E }
I: { 00 2F }
I: { 00 30 }
I: { 00 31 }
I: { 00 32 }
I: { 00 33 }
I: { 00 34 }
I: { 00 35 }
I: { 00 36 }
I: { 00 37 }
I: { 00 38 }
I: { 00 39 }
I: { 00 3A }
I: { 00 3B }
I: { 00 3C }
I: { 00 3D }
I: { 00 3E }
I: { 00 3F }
I: { 00 40 }
I: { 00 41 }
I: { 00 42 }
I: { 00 43 }
I: { 00 44 }
I: { 00 45 }
I: { 00 46 }
I: { 00 47 }
I: { 00 48 }
I: { 00 49 }
I: { 00 4A }
I: { 00 4B }
I: { 00 4C }
I: { 00 4D }
I: { 00 4E }
I: { 00 4F }
I: { 00 50 }
I: { 00 51 }
I: { 00 52 }
I: { 00 53 }
I: { 00 54 }
I: { 00 55 }
I: { 00 56 }
I: { 00 57 }
I: { 00 58 }
I: { 00 59 }
I: { 00 5A }
I: { 00 5B }
I: { 00 5C }
I: { 00 5D }
I: { 00 5E }
I: { 00 5F }
I: { 00 60 }
I: { 00 61 }
I: { 00 62 }
I: { 00 63 }
I: { 00 64 }
I: { 00 65 }
I: { 00 66 }
I: { 00 67 }
I: { 00 68 }
I: { 00 69 }
I: { 00 6A }
I: { 00 6B }
I: { 00 6C }
I: { 00 6D }
I: { 00 6E }
I: { 00 6F }
I: { 00 70 }
I: { 00 71 }
I: { 00 72 }
I: { 00 73 }
I: { 00 74 }
I: { 00 75 }
I: { 00 76 }
I: { 00 77 }
I: { 00 78 }
I: { 00 79 }
I: { 00 7A }
I: { 00 7B }
I: { 00 7C }
I: { 00 7D }
I: { 00 7E }
I: { 00 7F }
I: { 00 80 }
I: { 00 81 }
I: { 00 82 }
I: { 00 83 }
I: { 00 84 }
I: { 00 85 }
I: { 00 86 }
I: { 00 87 }
I: { 00 88 }
I: { 00 89 }
I: { 00 8A }
I: { 00 8B }
I: { 00 8C }
I: { 00 8D }
I: { 00 8E }
I: { 00 8F }
I: { 00 90 }
I: { 00 91 }
I: { 00 92 }
I: { 00 93 }
I: { 00 94 }
I: { 00 95 }
I: { 00 96 }
I: { 00 97 }
I: { 00 98 }
I: { 00 99 }
I: { 00 9A }
I: { 00 9B }
I: { 00 9C }
I: { 00 9D }
I: { 00 9E }
I: { 00 9F }
I: { 00 A0 }
I: { 00 A1 }
I: { 00 A2 }
I: { 00 A3 }
I: { 00 A4 }
I: { 00 A5 }
I: { 00 A6 }
I: { 00 A7 }
I: { 00 A8 }
I: { 00 A9 }
I: { 00 AA }
I: { 00 AB }
I: { 00 AC }
I: { 00 AD }
I: { 00 AE }
I: { 00 AF }
I: { 00 B0 }
I: { 00 B1 }
I: { 00 B2 }
I: { 00 B3 }
I: { 00 B4 }
I: { 00 B5 }
I: { 00 B6 }
I: { 00 B7 }
I: { 00 B8 }
I: { 00 B9 }
I: { 00 BA }
I: { 00 BB }
I: { 00 BC }
I: { 00 BD }
I: { 00 BE }
I: { 00 BF }
I: { 00 C1 }
I: { 1D 52 }





#Nova Cyprus
I: { 00 01 }
I: { 00 02 }
I: { 00 03 }
I: { 00 04 }
I: { 00 05 }
I: { 00 06 }
I: { 00 07 }
I: { 00 08 }
I: { 00 09 }
I: { 00 0A }
I: { 00 0B }
I: { 00 0C }
I: { 00 0D }
I: { 00 0E }
I: { 00 0F }
I: { 00 10 }
I: { 00 11 }
I: { 00 12 }
I: { 00 13 }
I: { 00 14 }
I: { 00 15 }
I: { 00 16 }
I: { 00 17 }
I: { 00 18 }
I: { 00 19 }
I: { 00 1A }
I: { 00 1B }
I: { 00 1C }
I: { 00 1D }
I: { 00 1E }
I: { 00 1F }
I: { 00 20 }
I: { 00 21 }
I: { 00 22 }
I: { 00 23 }
I: { 00 24 }
I: { 00 25 }
I: { 00 26 }
I: { 00 27 }
I: { 00 28 }
I: { 00 29 }
I: { 00 2A }
I: { 00 2B }
I: { 00 2C }
I: { 00 2D }
I: { 00 2E }
I: { 00 2F }
I: { 00 30 }
I: { 00 31 }
I: { 00 32 }
I: { 00 33 }
I: { 00 34 }
I: { 00 35 }
I: { 00 36 }
I: { 00 37 }
I: { 00 38 }
I: { 00 39 }
I: { 00 3A }
I: { 00 3B }
I: { 00 3C }
I: { 00 3D }
I: { 00 3E }
I: { 00 3F }
I: { 00 40 }
I: { 00 41 }
I: { 00 42 }
I: { 00 43 }
I: { 00 44 }
I: { 00 45 }
I: { 00 46 }
I: { 00 47 }
I: { 00 48 }
I: { 00 49 }
I: { 00 4A }
I: { 00 4B }
I: { 00 4C }
I: { 00 4D }
I: { 00 4E }
I: { 00 4F }
I: { 00 50 }
I: { 00 51 }
I: { 00 52 }
I: { 00 53 }
I: { 00 54 }
I: { 00 55 }
I: { 00 56 }
I: { 00 57 }
I: { 00 58 }
I: { 00 59 }
I: { 00 5A }
I: { 00 5B }
I: { 00 5C }
I: { 00 5D }
I: { 00 5E }
I: { 00 5F }
I: { 00 60 }
I: { 00 61 }
I: { 00 62 }
I: { 00 63 }
I: { 00 64 }
#I: { 00 65 }
#I: { 00 66 }
I: { 00 67 }
#I: { 00 68 }
#I: { 00 69 }
I: { 00 6A }
I: { 00 6B }
I: { 00 6C }
I: { 00 6D }
I: { 00 6E }
I: { 00 6F }
I: { 00 70 }
I: { 00 71 }
I: { 00 72 }
I: { 00 73 }
I: { 00 74 }
I: { 00 75 }
I: { 00 76 }
I: { 00 77 }
I: { 00 78 }
I: { 00 79 }
I: { 00 7A }
I: { 00 7B }
I: { 00 7C }
I: { 00 7D }
I: { 00 7E }
I: { 00 7F }
I: { 00 80 }
I: { 00 81 }
I: { 00 82 }
I: { 00 83 }
I: { 00 84 }
I: { 00 85 }
I: { 00 86 }
I: { 00 87 }
I: { 00 88 }
I: { 00 89 }
I: { 00 8A }
I: { 00 8B }
I: { 00 8C }
I: { 00 8D }
I: { 00 8E }
I: { 00 8F }
I: { 00 90 }
I: { 00 91 }
I: { 00 92 }
I: { 00 93 }
I: { 00 94 }
I: { 00 95 }
I: { 00 96 }
I: { 00 97 }
I: { 00 98 }
I: { 00 99 }
I: { 00 9A }
I: { 00 9B }
I: { 00 9C }
I: { 00 9D }
I: { 00 9E }
I: { 00 9F }
I: { 00 A0 }
I: { 00 A1 }
I: { 00 A2 }
I: { 00 A3 }
I: { 00 A4 }
I: { 00 A5 }
I: { 00 A6 }
I: { 00 A7 }
I: { 00 A8 }
I: { 00 A9 }
I: { 00 AA }
I: { 00 AB }
I: { 00 AC }
I: { 00 AD }
I: { 00 AE }
I: { 00 AF }
I: { 00 B0 }
I: { 00 B1 }
I: { 00 B2 }
I: { 00 B3 }
I: { 00 B4 }
I: { 00 B5 }
I: { 00 B6 }
I: { 00 B7 }
I: { 00 B8 }
I: { 00 B9 }
I: { 00 BA }
I: { 00 BB }
I: { 00 BC }
I: { 00 BD }
I: { 00 BE }
I: { 00 BF }
I: { 00 C1 }
I: { 1D 52 }




# Nova greece
I: { 00 01 }
#I: { 00 02 }
#I: { 00 03 }
I: { 00 04 }
I: { 00 05 }
I: { 00 06 }
I: { 00 07 }
I: { 00 08 }
I: { 00 09 }
I: { 00 0A }
I: { 00 0B }
I: { 00 0C }
I: { 00 0D }
I: { 00 0E }
I: { 00 0F }
I: { 00 10 }
I: { 00 11 }
I: { 00 12 }
I: { 00 13 }
#I: { 00 14 }
#I: { 00 15 }
I: { 00 16 }
I: { 00 17 }
I: { 00 18 }
I: { 00 19 }
I: { 00 1A }
I: { 00 1B }
I: { 00 1C }
I: { 00 1D }
I: { 00 1E }
I: { 00 1F }
I: { 00 20 }
I: { 00 21 }
I: { 00 22 }
I: { 00 23 }
I: { 00 24 }
I: { 00 25 }
I: { 00 26 }
I: { 00 27 }
I: { 00 28 }
I: { 00 29 }
I: { 00 2A }
I: { 00 2B }
I: { 00 2C }
I: { 00 2D }
I: { 00 2E }
I: { 00 2F }
I: { 00 30 }
I: { 00 31 }
I: { 00 32 }
I: { 00 33 }
I: { 00 34 }
I: { 00 35 }
I: { 00 36 }
I: { 00 37 }
I: { 00 38 }
I: { 00 39 }
I: { 00 3A }
I: { 00 3B }
I: { 00 3C }
I: { 00 3D }
I: { 00 3E }
I: { 00 3F }
I: { 00 40 }
I: { 00 41 }
I: { 00 42 }
I: { 00 43 }
I: { 00 44 }
I: { 00 45 }
I: { 00 46 }
I: { 00 47 }
I: { 00 48 }
I: { 00 49 }
I: { 00 4A }
I: { 00 4B }
I: { 00 4C }
I: { 00 4D }
I: { 00 4E }
I: { 00 4F }
I: { 00 50 }
I: { 00 51 }
I: { 00 52 }
I: { 00 53 }
I: { 00 54 }
I: { 00 55 }
I: { 00 56 }
I: { 00 57 }
I: { 00 58 }
I: { 00 59 }
I: { 00 5A }
I: { 00 5B }
I: { 00 5C }
I: { 00 5D }
I: { 00 5E }
I: { 00 5F }
I: { 00 60 }
I: { 00 61 }
I: { 00 62 }
I: { 00 63 }
I: { 00 64 }
I: { 00 65 }
I: { 00 66 }
I: { 00 67 }
I: { 00 68 }
I: { 00 69 }
I: { 00 6A }
I: { 00 6B }
I: { 00 6C }
I: { 00 6D }
I: { 00 6E }
I: { 00 6F }
I: { 00 70 }
I: { 00 71 }
I: { 00 72 }
I: { 00 73 }
I: { 00 74 }
I: { 00 75 }
I: { 00 76 }
I: { 00 77 }
I: { 00 78 }
I: { 00 79 }
I: { 00 7A }
I: { 00 7B }
I: { 00 7C }
I: { 00 7D }
I: { 00 7E }
I: { 00 7F }
I: { 00 80 }
I: { 00 81 }
I: { 00 82 }
I: { 00 83 }
I: { 00 84 }
I: { 00 85 }
I: { 00 86 }
I: { 00 87 }
I: { 00 88 }
I: { 00 89 }
I: { 00 8A }
I: { 00 8B }
I: { 00 8C }
I: { 00 8D }
I: { 00 8E }
I: { 00 8F }
I: { 00 90 }
I: { 00 91 }
I: { 00 92 }
I: { 00 93 }
I: { 00 94 }
I: { 00 95 }
I: { 00 96 }
I: { 00 97 }
I: { 00 98 }
I: { 00 99 }
I: { 00 9A }
I: { 00 9B }
I: { 00 9C }
I: { 00 9D }
I: { 00 9E }
I: { 00 9F }
I: { 00 A0 }
I: { 00 A1 }
I: { 00 A2 }
I: { 00 A3 }
I: { 00 A4 }
I: { 00 A5 }
I: { 00 A6 }
I: { 00 A7 }
I: { 00 A8 }
I: { 00 A9 }
I: { 00 AA }
I: { 00 AB }
I: { 00 AC }
I: { 00 AD }
I: { 00 AE }
I: { 00 AF }
I: { 00 B0 }
I: { 00 B1 }
I: { 00 B2 }
I: { 00 B3 }
I: { 00 B4 }
I: { 00 B5 }
I: { 00 B6 }
I: { 00 B7 }
I: { 00 B8 }
I: { 00 B9 }
I: { 00 BA }
I: { 00 BB }
I: { 00 BC }
I: { 00 BD }
I: { 00 BE }
I: { 00 BF }
I: { 00 C1 }
I: { 1D 52 }