Eurocardsharing

Go Back   Eurocardsharing > Sharing receivers > Technomate > Tutorials

Tutorials Discussion, for newbies CS share 2 tm9100 in house gbox 2.25 only at Technomate forum; Hi this is for total newbies who wish to share 2 tm9100 or tm9101 supers with one sly uk card ...

Reply
 
LinkBack Thread Tools Display Modes
for newbies CS share 2 tm9100 in house gbox 2.25 only
Old
  (#1)
nelly68
Junior Member
 
nelly68's Avatar
 
Offline
Posts: 7

Level: 1 [♥ Bé-Yêu ♥]
Life: 0 / 15
Magic: 2 / 458
Experience: 60%

Thanks: 2
Thanked 1 Time in 1 Post
Join Date: Jul 2007
for newbies CS share 2 tm9100 in house gbox 2.25 only - 15-May-2008, 23:01

Hi this is for total newbies who wish to share 2 tm9100 or tm9101 supers
with one sly uk card in house with gbox 2.25 only no pc required for the share just to setup.
If you follow these instructions and cut and paste where needed you will have them up and working in an hour or so. This is not for skilled gbox users nor will everything seem correct to them but it will help total newbies on the way to thier first share and from there the confidence to move on to more complex stuff.
what you will need
PROGRAMS
1 DCC 294 for file transfer
2 Technomate control center 6
3 IBOOT
These are the programs you will need for setup
most can be found on the main tm websites or downloaded from some of the users here who have left links
You also need to down load an image
I used UK UR 10 for this it is one of many but you can download from panel all you need setup for you and no need for lots of file transfer which could lead to a small error resulting in frustration. on this image and i asume the other UR images are the same you will be able to download gbox 2.25 card readers plus the most important for the tm9100 a fully working gbox suite and gbox center with no need for messing with settings.
At this point i will assume that the basics of the tm have been learnt
i recomend loading the UR IMAGE onto a memory card do not risk putting it into flash memory as this can create problems and after setup and a bit of practice the image can be kept for referenc while another of your choice is used later
OK
step one
use Iboot to load image onto memery cards of each box
once complete boot each box up in turn and setup with basic config
one sat fixed dish eurobird 28.2 east do this even if you have motorised the need is to keep it simple and not to complicate things.
do a search to scan for all channels
now both boxes should have one sat with all channels on them and nothing else
now goto the remote coloured buttons starting with red on the left.
forget the red and press each one the first green button when pressed will show the UR download panel these are such things as download keys softcams add on and others
with the box connected to the router select download softcams configs
in the list go down to gbox 2.25 2 cards press selct to download
once complete goto download add ons press select and move down till you see gbox center and gbox suite download both do not leave one out
repeat this for the 2nd box but download gbox nd2.25 2 card
now all the basics are downloaded
now time to get sly card working on each box on the remote press the blue button and a screen appears called UR softcam v .1 put sly card in any of the slots then select gbox 2.25 from all three boxes press save and exit.
for this i put the channel to sly one before doing and it clears quickly

now both boxes should have been checked same way and sly working on both
if you have got to this point and alls well good now to setup boxes
there are two boxes and we are going to set them upwith these settings
box 1
ip 192.168.1.150
port 6667
password 12345678

box 2
ip 192.168.1.151
port 5566
password 12345679
agian these are used to keep it very simple and not to confuse
on the first box goto setup press expert setup there you will see ip address at top change this to 192.168.1.150 next to that is a box dhcp press this till a red cross appears now move down to port and change this to 6667 from 80 defualt save and exit
now next box goto setup expert setup and change ip to 192.168.1.151
agian put a cross on dhcp then move to port and change to 5566save setting and exit it may be worth rebooting both boxes at this point
both boxes have now had basic setup now time to use technomate control center to change passwords to the deired numbers
so with both boxes connected to router and pc or laptop connected to router start technomate control center and press update then press change password. change the ip address to 192.168.1.150 then add new password twice in my case the UR IMAGE add no password so current password left blank and the new password12345678 was added when change correct it wiill let you know do the same for other box 192.168.1.151 password change to 12345679
ok next stage
need to check that password and ip match
so on the pc start dcc 294 change language to english
you will see a pc a sat box and a router
in connection type click router
in equipment tick card flah and memory stick
leave pc ip alone router should be 192.168.1.1 this is defualt
change box ip to 192.168.1.150
next change password leave root alone and add 12345679
if all done press reconnect if good it will all turn green ftp connected
telnet connected and boot manager not found
if both boxes do this then you are ready for the last stages
you need now to up date file cwshare.cfg start dcc294 agian and select box 191.168.1.150 when connected goto ftp at the bottom left of your screen
you will now see a split screen the left hand side is the image folders double click on var folder then new list appears double click on keys now a small list of files appears go to cwshare.cfg right click on the file slect edit delete the few lines and paste this below with all ashes

#Please find below an example and explanation of the cwshare.cfg file that is used with g*ox and is extremely important ...

#Cwshare.cfg
#This is an example of cwshare.cfg with the most important communication lines:

M: { 192.168.1.150 { 12345678 }}
#
#D: { box2.dyndns.org { 5566 5580 { 22222222 { A3 A3 }}}}
#D: { box3.dyndns.org { 5566 5566 { 33333333 { A3 A3 }}}}
#
D: { 192.168.1.151 { 6667 5566{ 12345679 { A1 A1 }}}}



#The M-line. M: { youre DNSNAME { youre 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 youre 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 nd$ 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 youre use only.
#If you post a backup img. Remove all the information about youre shares.
#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 youre dreambox or in the g*ox center .Or you can use PHPg*ox statistics and UDPlog on a pc.
#The tmp/ files
#share.onl contains info about who is online and who is not. The ones with a 1 in front is online and the ones 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 youre 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 cant 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 g*ox 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 cant receive cards that are further away than 5 boxes away. You can adjust this youre self by setting this in youre 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 Second$ if no reply.
# 6000 resync decode after 6 Second$ if net decode failed
#N: { 00 01 03 1F 4000 6000 }
finish paste on the #n line
now at top of screen select save and exit
now your setting are in for that boxes cwshare.cfg
next look at the file if it as 644 attributes at right and side right click onfile select attributes 755 then save
now box 192.168.1.150 is done please do not try and alter this file in gbox suite it gave me problems
reboot box
now in dcc294 select box 192.168.1.151
agian select ftp then var then keys then cwshare edit file and paste this below

#Please find below an example and explanation of the cwshare.cfg file that is used with g*ox and is extremely important ...

#Cwshare.cfg
#This is an example of cwshare.cfg with the most important communication lines:

M: { 192.168.1.151 { 12345679 }}
#
#D: { box2.dyndns.org { 5566 5580 { 22222222 { A3 A3 }}}}
#D: { box3.dyndns.org { 5566 5566 { 33333333 { A3 A3 }}}}
#
D: { 192.168.1.150 { 5566 6667{ 12345678 { A1 A1 }}}}



#The M-line. M: { youre DNSNAME { youre 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 youre 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 nd$ 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 youre use only.
#If you post a backup img. Remove all the information about youre shares.
#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 youre dreambox or in the g*ox center .Or you can use PHPg*ox statistics and UDPlog on a pc.
#The tmp/ files
#share.onl contains info about who is online and who is not. The ones with a 1 in front is online and the ones 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 youre 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 cant 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 g*ox 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 cant receive cards that are further away than 5 boxes away. You can adjust this youre self by setting this in youre 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 Second$ if no reply.
# 6000 resync decode after 6 Second$ if net decode failed
#N: { 00 01 03 1F 4000 6000 }

agian paste down to #n line
save then change attribute on file to 755
reboot box

both boxes are ready to share the above settings in each paste are exactly like i have mine all lines with # at start are guides
no # the proper lines at the time of setting this up i messed with the share levels and remove a then added a as i was trying a digalb card as well as sly card this turned out to the best and agian kept it simple to reduce chance of errors
both boxes should have everything ready now time for router

you need to setup two static ip adresses in your router
ip 192.168.1.150
ip 192.168.1.151
and set up rule for each
ip 192.168.1.150 set rule name box1 set protacol to udp only and port to 6667
next set 192.168.1.151 to rule name box2 protacol to udp and port to 5566
after after this save and reboot router
now boxes and router ready
start boxes and put sly card in one goto blue panel select gbox 2.225 for each softcam save and exit both boxes should now have full packages
if not goto goto yellow button gbox suite and look at gbox info it will tell you if you are on line and if a card or peer other box on line

if you follow this carefully it will work i have had sly card running for days with no freeze or glitches the card it self is a very recent one
some of these steps and settings you do not need but follow it anyway to prevent missing something hope it works for you
once running you can change a bit at a time in your cwshare file to learn
ever so slightly different to dreambox but not much
ps nice to give a little back
   
Reply With Quote
The Following User Says Thank You to nelly68 For This Useful Post:
Markoni (11-November-2008)
Old
  (#2)
tomslick
Senior Member
 
tomslick's Avatar
 
Offline
Posts: 100

Level: 9 [♥ Bé-Yêu ♥]
Life: 0 / 200
Magic: 33 / 5663
Experience: 0%

Thanks: 44
Thanked 49 Times in 30 Posts
Join Date: Apr 2008
16-May-2008, 22:15

Great post. Just repaired my 2nd tm9100 and used exactly your setting and it worked perfect. Only thing is changing port 80 to 6*** is not need and it stops your computer from logging in with firefox/explorer. Still a super post.
   
Reply With Quote
The Following User Says Thank You to tomslick For This Useful Post:
nelly68 (16-May-2008)
Sponsored Links
Old
  (#3)
nelly68
Junior Member
 
nelly68's Avatar
 
Offline
Posts: 7

Level: 1 [♥ Bé-Yêu ♥]
Life: 0 / 15
Magic: 2 / 458
Experience: 60%

Thanks: 2
Thanked 1 Time in 1 Post
Join Date: Jul 2007
16-May-2008, 23:01

thanks glad it helped
   
Reply With Quote
Old
  (#4)
nelly68
Junior Member
 
nelly68's Avatar
 
Offline
Posts: 7

Level: 1 [♥ Bé-Yêu ♥]
Life: 0 / 15
Magic: 2 / 458
Experience: 60%

Thanks: 2
Thanked 1 Time in 1 Post
Join Date: Jul 2007
18-May-2008, 01:11

for educational purpuse anyone setting up a CSnetwork only need to remove box2 id fronm router and put box2 two at new location and add their ndns.org address in d line and they become a fully fledge member of cardsharing network
by now you must think i think Murdock as to much power
happy sharing
bye
   
Reply With Quote
Old
  (#5)
leez
Senior Member
 
leez's Avatar
 
Offline
Posts: 111

Level: 9 [♥ Bé-Yêu ♥]
Life: 0 / 213
Magic: 37 / 6045
Experience: 55%

Thanks: 35
Thanked 1 Time in 1 Post
Join Date: Apr 2008
14-July-2008, 01:49

right m8 i have two boxes a dm 500 and tm 9100 can i share my sly card with each ... i have tried this afternoon , but to no joy .. i have g box on both boxes and all well untill the tcc bit .. when i put in those ip numbers and change port , the tcc cannot find a connection off sever it says.. i changed the ip on the ttc but it won t work.. its connected to router ok .. i dont know wheir i have gone wrong ..
   
Reply With Quote
Old
  (#6)
starwards
Banned as Payserver
 
starwards's Avatar
 
Offline
Posts: 4

Level: 1 [♥ Bé-Yêu ♥]
Life: 0 / 5
Magic: 1 / 147
Experience: 21%

Thanks: 1
Thanked 1 Time in 1 Post
Join Date: Sep 2008
Age: 37
12-September-2008, 19:26

thank you great job mate
   
Reply With Quote
Old
  (#7)
mugen888
Junior Member
 
mugen888's Avatar
 
Offline
Posts: 12

Level: 2 [♥ Bé-Yêu ♥]
Life: 0 / 31
Magic: 4 / 914
Experience: 25%

Thanks: 1
Thanked 0 Times in 0 Posts
Join Date: Dec 2007
27-September-2008, 08:51

Do both boxes have to be connected to a satelites?
   
Reply With Quote
Old
  (#8)
Markoni
ECS Master
 
Markoni's Avatar
 
Offline
Posts: 499

Level: 20 [♥ Bé-Yêu ♥♥ Bé-Yêu ♥♥ Bé-Yêu ♥♥ Bé-Yêu ♥]
Life: 0 / 491
Magic: 166 / 14880
Experience: 64%

Thanks: 40
Thanked 273 Times in 133 Posts
Join Date: Aug 2007
11-November-2008, 00:33

Quote:
Originally Posted by tomslick View Post
Great post. Just repaired my 2nd tm9100 and used exactly your setting and it worked perfect. Only thing is changing port 80 to 6*** is not need and it stops your computer from logging in with firefox/explorer. Still a super post.
Glad it's up and running.
You can change the port. Log in using this format - BOXIP:WHATEVERPORT. Browsers just default to port 80
   
Reply With Quote
need help
Old
  (#9)
mikenlin
Junior Member
 
mikenlin's Avatar
 
Offline
Posts: 11

Level: 2 [♥ Bé-Yêu ♥]
Life: 0 / 28
Magic: 3 / 746
Experience: 12%

Thanks: 0
Thanked 0 Times in 0 Posts
Join Date: Nov 2008
Age: 69
need help - 12-December-2008, 09:03

I have followed the instructions loaded ur12 and gbox onto 9100s but when i get to the card it will not clear. hlp please

mikenlin
   
Reply With Quote
Old
  (#10)
nelly68
Junior Member
 
nelly68's Avatar
 
Offline
Posts: 7

Level: 1 [♥ Bé-Yêu ♥]
Life: 0 / 15
Magic: 2 / 458
Experience: 60%

Thanks: 2
Thanked 1 Time in 1 Post
Join Date: Jul 2007
12-February-2009, 23:53

This post at the time was to help total newbies i have had the odd post asking questions please let me clear this up
1 all references to setting up router are not required for home use they were put in to help set up for sharing out side the home and to help newbies understand port forwarding without a lot of background knowledge. ip addresses in this post can be changed to no ip.com or dydns.org the other issue was changing th port address in expert setup agian this was not to mess up web interface but to help newbies remember what port each box was as it confused me keep swapping boxes and remembering ports.
i posted this help to give newbies a chance
pass on your tips if they work to help others
on another site under the name nelly69 i posted a write up a long while ago on getting out of a constant reboot problem with the use of serial lead instead of jtag it is now used a lot and the dates of posts show this. i posted the frustration i had at the time to help others and some guys such as cyberdunc replied and made me feel more confident. at the time many will have known this trick but did not share it so much so the file had to be found on another site
please those with understaning pass it on even if it is a little write up i myself am still learning even now the constant changing cams key setups and so on mean we all are learning
cheers nelly68/69
i could have called the origanal post setting up card sharing on tm9100 but only those who read all post would understand
   
Reply With Quote
Reply

Bookmarks


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off

Forum Jump



ECS on RSS ECS on Twitter ECS on Facebook ECS on Youtube
Follow us on:

Powered by vBulletin
Copyright 2002 - 2010, Jelsoft Enterprises Ltd.
SEO by vBSEO ©2011, Crawlability, Inc.
Dreambox