Is there any good tutorial or program gbox sharing on a relook 400s ?

Use an image that supports gbox like Highland ,fantacy or New improved nemu image.

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. 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.
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

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...

# 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 }

hi guys
does any body have CCcam working on relook
cheers froggie

Hello!
There is nothing special on the 400s.
I think a good software for configuration is cw-share-cfg-tool.
A good dokumentation for gbox hm... perhaps gboxfaq.pdf. There exist many translations.

Gbox works good with any enigma images (gemini, nabilo,colosseum,sifteam)
best regards

Why use enigma on relook 400?Enigma doesnt suport twinturner.