Вход в биллинг - Billing entrance - www.CardsharingServer.com

English forum section

Автор Тема: MgCamd adjustment for IP Box  (Прочитано 7075 раз)


  • Главный помощник Moderatora
  • Ветеран
  • ****
  • Сообщений: 9048
  • Keep trying!
MgCamd adjustment for IP Box
« : 07 Марта 2013, 08:19:58 »
Download the firmware for your receiver from here:

Flash procedure:

Format USB disk to FAT32 or linux ext3.
Files you downloaded to be unzipped and copied to the USB disk
Switch OFF IPBox using switch on the rear panel, insert USB disk to the receiver
Switch IPBox ON using switch on the rear panel
As soon as AB IPBox ХХХ appears, press and release „Standby“ button
USB UPGRADE will uppear and update will start, it may take 15-20 minutes
After flashing, IPBox will restart automatically

Check mg_cfg file
For firmware on DGS basis (Ab-com, NLB, SifTeam, PGI, UFM), parameter B: { 12 }
For Enigma firmware, B: { 11 }

Addons for enigma2 http://www.cardsharing.cc/index.php?topic=28602.0 (see attached file)

It is assumed that:

- You know standard settings of your receiver completely and have already set its IP address;
- You have an idea of how to use FTP and Telnet;
- Your receiver has Internet access;
- mgcamd is already installed and starts automatically with the receiver start-up;

If you are not sure in any of the above issues, please read the description below:

What is the way to correctly set up receiver's IP address?

You need to read Manual to the receiver. All commands are set up via receiver's main menu. Receiver may get its address dynamically using DHCP protocol or you may apply fixed address in your home network. To check if your receiver is "recognized" in the network, you may apply several methods. For example, you may use ping command from Windows command string (DOS-window) that sends test request "is there anybody at teh given address?" and demonstrates the reply. Properly adjusted address will produce something like (in this sample, IP address of the receiver is


Pinging with 32 bytes of data:

Reply from bytes=32 time=1ms TTL=255
Reply from bytes=32 time<1ms TTL=255
Reply from bytes=32 time<1ms TTL=255
Reply from bytes=32 time<1ms TTL=255

Ping statistics for
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 0ms, Maximum = 1ms, Average = 0ms

Please pay attention that at the end, 0% of lost test packages are shown. It means that everything works OK. Also, receiver has its own web-interface that typically must be active when the receiver is ON. Try to open the page: http://ip.address.of your receiver/ in a browser of your PC. You will be asked for login and password. It means that your receiver is available in the network.

What is FTP and Telnet and how to use them?

There is no necessity to explain Unix/Linux principles here. If you really do not know what is it, use Google.

To enter IPBox using FTP, apply FTP client of FileZilla Client, Far or Total Commander type. To use Telnet or SSH, the best option is PuTTY.

How to check if my receiver has Internet access?

Enter your receiver using Telnet and give a command to ping address, where address is either IP-address or name of the sharing server you use. To stop the command fulfillment, press CTRL+C. Here is a sample where sharing server name is myserver1.xyz.com:

ping myserver1.xyz.com
PING myserver1.xyz.com ( 56(84) bytes of data.
64 bytes from icmp_seq=1 ttl=63 time=12.797 ms
64 bytes from icmp_seq=2 ttl=63 time=12.778 ms
64 bytes from icmp_seq=3 ttl=63 time=12.774 ms

--- myserver1.xyz.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 0.774/0.783/0.797/0.010 ms

Here, you can see that everything works correct because there is no losses (0% packet loss).

How to check if mgcamd has started and works with the receiver start-up?

You need to enter receiver using Telnet and give command ps afx | grep mgcamd | grep -v grep
If you see something like:

-sh-3.00# ps | grep mgcamd | grep -v grep
  557 ? Sl 0:12 /var/bin/mgcamd

then, mgcamd has started and is working (you need only set it up).

MGCAMD configuration files

All files required for proper mgcamd operation shall be available in  /var/keys folder and nowhere else!. Also pay attention that capital/upper case letters available in the file names shall be like specified below, as for Linux it does matter. All files are common text-files that can be edited using eny text editor saving files as common text (plain text).

At first, pay attention to settings file:
In this file, keys are kept for emulator section of mgcamd. You DO NOT NEED this file for sharing. If you put some proper keys into the file, you can open some channels with "hacked" encryption systems without sharing at all.

Valuable advice:
If you are going to use SoftCam.Key file for certain channels and sharing server - for other channels, be sure that there is NO KEYS in the SoftCam.Key for the channels you are going to open using sharing server. mgcamd is always looking for the keys into the SoftCam.Key and if the key is found (even old one and not working), it will use only it. Naturally, that if the key is old and is not working, you will see a black screen even if you have connection to the sharing server. Therefore, it is recommended to delete SoftCam.Key from /var/keys (or rename it to the file with other extension), set up the remaining things, be sure that everything works properly, and then to decide if you need SoftCam in further sharing.

For sharing, you will need the following files:

If any other files remained in the /var/keys folder and you don't use any other software but mgcamd - you may delete ot transfer the remaining files to the other placeа. So, in mg_cfg file, the main mgcamd system configuration is contained such as time-out settings when connecting the network, adjustment options and log-files. In newcamd.list file, parameters for server(s) connection are added, i.e. here, all parameters you received from the particular sharing provider are added. Files such as ignore.list, priority.list and replace.list allow setting fine "tuning" of the parameters in order the channels to be opened faster. You may go without the three files if you are satisfied with the speed of encrypted channels opening. Often, there is no those three files at all after you installed a new firmware (or they are empty), and if you need, you may create them by yourself.

Valuable advice:

If mg_cfg contains standard information with minor changes, so, the content of the remaining files is fully dependent on the packages received and settings of the particluar sharing server. Therefore, if anybody has "100% working" configuration files, it does not mean that  they will be good for you personally. It is better to understand by yourself, what is written in those files and what sense do they have.

Please use mg_cfg from our server. Copy and paste all parameters from here: http://www.cardsharing.cc/index.php?topic=23717.0
Pay attention to {B} parameters:

# box type
# 00 autodetect, change only if you think wrong type detected.
# 01 dbox2
# 02 dreambox
# 03 triple-dragon
# 04 relook
# 05 openbox
# 06 dreambox/mips
# 08 stapi/kathrein
# 09 stapi/ipbox
# 11 stapi/openbox

For IP Box, B: { see above }

The second file which is required for sharing is newcamd.list.
It has simple syntax - it contains the information what is the sharing server you receiver needs to connect, what is the name (login), password and port No. Naturally, considering the file name, all the information containing inside is required for connection using newcamd protocol. Don't try to add servers to the file that are not accepting clients by newcamd protocol! Comments in newcamd.list file srart with #.

Lines with server configuration shall start with CWS=.... in this file! I.e., no other symbols before CWS, even spaces! Otherwise, mgcamd will ignore such lines.

# how often (in seconds) sharing server shall be checked for operability. It is useful if you watch a non-encrypted channel for a long time.

# no other parameters shall be available in this file except for sharing server parameters below!

# each next line described your connect to any sharing package you use.
# if you have several packages, for each package, a particular configuration line is required
# even if the server is the same, each package may have its separate port, therefore
# you need to add separate line for each package. All information from provider. The line format is as follows:
# CWS = server address port login password 14-digits-encryption key
# for example, you have access to two packages using different ports. Therefore, you need 2 lines
# (you need to fill up the information received in the billing:

CWS = server1.com 1234 username password 0102030405060708091011121314 # package X
CWS = server2.com 5678 username password 0102030405060708091011121314 # package Y

Restart receiver and if you set up everything correctly including home network, Internet access and the above files onfiguration, everything must work.

How to get LOG from mgcamd?

LOG is the first thing to be studied if something does not work. LOG is the first thing you will be requested on the forum, if you will need assistance. So, it is very important to know how to efficiently and correctly get a log file from your receiver.

There are 2 ways to get a log-file. Either make mgcamd to write into a file inside the receiver, or make mgcamd to sent the log using network, say, to your PC.

In the first case, you need no additional software, To read the log-file, you need to enter your receiver via Telnet and monitor mgcamd real-time operation displaying teh file content to Linux screen using tail -f log-name command. This way is not so convenient.

More convenient is to monitor log file from your PC which is conencted to the receiver by a local network, without any logins to the receiver. For this purpose, install parameter L: { 01 } as is shown in mg_cfg default settings and launch a free software http://www.cardsharing.cc/index.php?topic=26069.0 on your PC (reader of messages in syslog format), that would receive mgcamd messages and display them on the PC screen.
VU+Zero. 13E, 82.5E, 56E, Vip All, OpenPLI 6.0 image, OSCam: 1.20-unstable_svn. ALL POSTS WITHOUT SIGNATURE AND LOG-FILE will be ignored and deleted!1.mg_cfg here http://www.cardsharing.cc/index.php?topic=23717.msg58140#msg58140
2. ignore-priority.lists here http://www.cardsharing.cc/index.php?topic