CardsharingServer ver 3.12

Switch to [russian]
 
Menu
Free Test
Registration
Price List
Rules
Forum
Password recovery
ENTRANCE
















Rules violating which, your account can be disabled:


  1. 1. Connection to the server without valid subscription - penalty for violation 5$ (The penalty is paid by depositing your balance in the billing)

    Probable reasons resulting in account lock:


    • Subscription has finished. In case your subscription has finished, you need to disconnect receiver from the server by removing the data you were provided with when purchasing subscription and restart your receiver. It is strictly prohibited to connect to any port of the server without valid subscription.

    • Connecting to the wrong port. It is allowed to connect to the paid ports specified in the billing. If you had more than one subscription and you do not want to extend one of them, you have to delete settings of the subscription from your receiver and reboot it not later than in the day of the subscription end.

    • Connecting to the wrong server. It is allowed to connect only to the server host (ip address) specified in the billing ("My subscription" section).


  2. 2. Frequent reconnections to the server - penalty for violation 5$ (The penalty is paid by depositing your balance in the billing)

    An automatic protection system against DDOS attacks is installed on the server. Limit of reconnections to any port - maximum of 5 connections per 5 minutes. If the connection limit is exceeded, IP address will be automatically blocked by the system for 30 minutes and unblocked later again. If you are blocked by the server for reconnections, you need to find out the reason for broken connection (reconnection) and eliminate it. If constant reconnections are going on within more than 2 days, your account will be banned by administrator. It can be unbanned only after the penalty is paid via the billing.

    The most frequent reasons for broken connection between the receiver and the server are as follows:


    • More than one emulator copy is launched in your receiver. Emulator restart script has glitched launching one more copy of the emulator without termination of the previous one. Usually, the reason for this is the receiver owner himself who, without waiting when the script is fully worked over (15 seconds), restarts emulator one more time. It may also happen if you launched a new copy of emulator manually using telnet without termination of the copy launched by the script. The easiest solution of the issue is to reboot receiver.

    • Understated timeout to listen to DW from the server (< 7 seconds) in emulator settings. If the parameter is understated and response from the server has not been received within the established time, emulator will break connection and connect to the server again after several unsuccessfull attempts to receive DW. In the mgcamd emulator, K parameter is responsible for DW timeout: { 07 } in mg_cfg file. Recommended value is 07. Check your settings, edit them and restart emulator.

    • Understated number of unsuccessful attempts for decoding of CW or expect time for decoding in emulator settings. The above parameters force the emulator to reconnect to the server if response from the server has not been received within X seconds or X number of CW queries. If the parameters are undertstated, for example, CW - 3 and time - 30, therefore, emulator will reconnect to the server each 3 requests or each 30 seconds in case of unsuccessfull decoding. For example, switching on the channel that cannot be encrypted, emulator will wait for 30 sec and reconnect, again in 30 sec, etc...as a result, after 5 attempts of reconnection (2.5 minutes), the limit of reconnects will be exceeded and ip will be banned for 10 minutes. Emulator cannot be allowed to reconnect so frequently. In mgcamd emulator, N line is responsible for those parameters: { 07 } 360 3600 , where 360 - the number of queries before reconnection and 3600 - the number of seconds before reconnection. Recommended N value: { 07 } 360 3600. Check your settings, edit them and restart emulator.

    • Login, password or DES key error. Excess space, wrong letter register (capital, small), using Cyrillic letters in login and password - all these are result of inattention that leads to unsuccessfull connection to the server, and as a consequence, constant reconnects that negatively influence the server work. Please be extremely attentive when adding settings to your receiver and re-check all settings 2-3 times. In order not to do an error, copy ready-made lines from the billing (My subscription sub-menu). Please also remember that changing the password to enter the billing, the password for all subscriptions will also be changed. After you changed the password in the billing, you need to make changes to your receiver settings within 5 minutes and reboot it. Password change on the server is immediate.


  3. 3. Sending packages with broken ECM structure to the server. - penalty for violation 5$ (The penalty is paid by depositing your balance in the billing)

    Packages with broken ECM structures, these are ECM requests (CW) with some bites corrupted. Being received by smart-cards, such requests will freeze the cards and are able to damage them forever. When one or more cards are frozen, the package starts freezing or stops completely for all users. Since the problem is posing serious problems to all our users, there is no compromise when banning the blamed person. In 90% of cases, the reason is a bad signal from satellite when a picture starts falling to pieces. In 10% of cases, the reason is in bad unstable internet connection. The packages are broken with their integrity being destroyed. The reason can be in unstable wifi connection, in overloaded uplink (upstream traffic) typically "eaten" by P2P clients (torrents, etc.). To solve the problem, it is required to disable the software using upstream traffic, check the route to the server for losses available using traceroute command, try to use other internet provider service. In case of a problem with signal reception, it is recommended to use a dish of the larger diameter or re-tune the dish available damaged by, for example, a strong wind. We give a breaker the only chance. For the repeated violation, the user IP and account will be banned forever without a possibility to restore.


  4. 4. Sending duplicated requests for decoding to the server. - penalty for violation 5$ (The penalty is paid by depositing your balance in the billing)

    Requests for decoding is allowed to be sent not frequently than 1 time per 5 seconds. Emulator shall be set up properly for this. By sending an request to the server, receiver will wait for response within minimum 5 seconds. Since the requests are processed by cards within 2-3 seconds (5-6 seconds for some packages), it is recommended to set ECM timeout as 7000ms. If the parameter is low (for example, 100ms), receiver will send 30-50 requests to the server instead of 1 request. Excessive requests being sent to the server will negatively affect the processing of all requests received from the users and significantly slow it down. Breakers will be punished by penalty. In mgcamd emulator, K parameter is responsible for DW timeout: { 07 } in mg_cfg file. Recommended value is 07. Check your settings, edit them and restart emulator. 7000ms -right parameter.


  5. 5. Launching more than one emulator using one receiver. - penalty for violation 5$ (The penalty is paid by depositing your balance in the billing)

    It is allowed to create only 1 connection for any port of the server. It is not allowed to launch more than 1 emulator. For receivers without open Linux OS such as Openbox and its clones, it is required to disable all active emulators and emulators with AUTO status except for the main emulator. The most frequent reason for ban is launching Xcamclient and Mgcamd emulators at a time. When using the recommended Mgcamd emulator, always disable AUTO mode of xcamclient emulator and delete folder /var/etc/protect/xcam, otherwise both emulators will connect to the server resulting in conflict. As a result, you will have problems to watch TV due to emulator conflict, and you will need to pay penalty for violation. Be sure that only 1 emulator is launched in the receiver before connecting to the server. Remove all the remaining emulators, if any.


  6. 6. Sending EMM requests to the server - penalty for violation 5$ (The penalty is paid by depositing your balance in the billing)

    It is not allowed to send EMM requests to the server (requests to update subscriptions and other changes of the cards). It is allowed to send ECM requests only (requests for decoding). When connecting to the server, setting up your emulator, be sure that an option of sending EMM requests to the server is disabled. By this, you will save not only your outgoing traffic, but you will not load the server with excessive requests to be processed. In the oscam emulator, EMM can be disabled in oscam.conf, [dvbapi] section, au=0 parameter. In the CCcam emulator, it is required to add or replace the existing parameter to CCcam.cfg file DISABLE EMM : yes


  7. 7. Sending a large number of KeepAlive requests to the server - penalty for violation 5$ (The penalty is paid by depositing your balance in the billing)

    To maintain active connection of the ports used to transfer data, a so-called KeepAlive parameter exists. The KeepAlive sends requests to the server with the preset time interval to maintain active connection. It is used to maintain the router connection to the server due to inactivity time. recommended parameter is 300 seconds (1 request per 5 minutes). It is not allowed to set the parameter lower by 10-30-60 seconds. (For example, subscriber of VIP ALL package will send 181440 requests per day instead of 6048 requests with the KeepAlive set for 10 seconds when connecting to 20 ports). In the Mgcamd emulator, CWS_KEEPALIVE = 300 parameter is set in the newcamd.list file with CWS lines are added from the billing.


  8. 8. Cascading - an increased number of queries for decoding (limit - 1 query per 10 seconds, 360 queries per 1 hour, 8640 queries per 24 hours)

    For cascading, account will be terminated without possibility of restoration and without any compensation. Breaker will be banned forever with all his subscriptions and balance terminated. Account unbanning is not possible! Cascading is being equal to a theft. Please remember that per 1 account, it is allowed to connect only 1 receiver with 1 active emulator and simultaneously watch and record only 1 channel. Those users violated the rules are not subject to be forgiven without no amnesty in no way.


  9. 9. Connecting 2 and more receivers per 1 account. Breaker will be banned forever with all his subscriptions and balance terminated. Account unbanning is not possible!

    Only 1 receiver can be connected per 1 account. It is not allowed to make settings for 2 receivers even if you want to use them one after another. All purchased subscriptions shall be used only for one receiver. Connection shall be using only one emulator and from the only IP address. If you decided to sell your old receiver, please be sure that server data have been deleted from the settings. Reset your receiver settings to default factory. It is not allowed to buy 2 subscriptions for 2 receivers per 1 account. For each receiver, a separate account shall be registered and separate subscription(s) bought.


  10. 10. Using PIP (picture-in-picture) option or simultaneous recording one and watching the other channel. For this violation, account will be terminated without possibility of restoration and without any compensation. All subscriptions and balance will be terminated. Account unbanning is not possible!

    When using PIP option or recording one and watching the other channel at the same time, requests to the server are being sent 2 times more frequently, i.e. cards are loaded 2 times more as if from 2 users. This option can be used with a "Dual Login" option being activated via "Personal information" billing section with no active subscriptions available. The "Dual Login" is 50% more expensive as compared to the single subscription. Please remember that "Dual Login" is the option for 1 receiver with 2 tuners onboard, not for 2 individual receivers. Without active "Dual Login", it is allowed to send 1 request each 10 seconds (maximum of 8640 requests per day). With the "Dual Login" being active, the amount is doubled and it is allowed to send 2 requests each 10 seconds (maximum of 17280 requests per day)


  11. 11. Delayed decoding. Breaker will be banned forever with all his subscriptions and balance terminated. Account unbanning is not possible!

    It is strictly prohibited to use delayed decoding for our server (telecast records decoding). With such decoding, requests are being sent to the server 30 times faster than during general viewing resulting in cards overload. Due to this, cards are overloaded and stop processing the requests received from other users. They freeze more frequently. This will result in picture freezes and failure of stable TV-watch up to the complete rejection in decoding for all users. Since the violation is very serious and malicious, we have to apply the most cruel sanctions to the users violated this rule: account will be disabled without a possibility to restore and any compensation.


  12. 12. Connecting to the reserve server from other receiver or emulator. Breaker will be banned forever with all his subscriptions and balance terminated. Account unbanning is not possible!

    It is allowed to connect to the main and reserve server using 1 receiver and 1 emulator from 1 IP address and send the same request for decoding per 1 time period. It is not allowed to share servers between 2 receivers. Users broken the rules will be banned without notification and without possibility to be unbanned. They will loose subscription together with the remaining money on their balance.


Administration reserves the right to change price, content of the packages, remove or add channels (packages), change ports, IP addresses etc. without notification and any compensation.

This is not administration liability, if a problem with provision of services arises not due to a fault of the server (provider bankruptcy, applying new methods of protection by provider, revolution in the country, cyber attack, etc.). No compensation is also envisaged.


You will find configuration files recommended by our server for MGCAMD emulator here

P.S. You will find out an actual status of your account (banned or not and the reason) on the homepage of the billing after authorization.


Cardsharing server © 2017