Posts by newtolinux

ok glad u got sorted

new2

thread closed

your user indicates the following

user = dvbapi ... this is oscam's built in client when using oscam in a linux receiver

user = xxxxx ..... this is an additional user that you or your friend have created uniq = 3 means there can be 3 logins with same user id .. maxhops & reshare irrelevant with oscam unless you using anticascading to limit ecm in card.

the item keeping your card updated will be the dvbapi user :36_002:

new2

so do your users connect to oscam or you have cccam running separate for shares

new2

what you mean by implanted cccam ??????

new2

you don't need in both if you are using oscam as cardserver only . just enter in oscam.server a line like this boxid = 12345678 ( note no spaces !! )

an example of one for your card ... note this is based on the reader being a pcsc reader on device position 1 . your setup would be different..

[reader]
label = ***uk
enable = 1
protocol = pcsc
device = 1
caid = 0963
detect = cd
mhz = 686
cardmhz = 686
ident = 0963:000000
group = ( 1 2 3 etc depending on your setup )
emmcache = 1,3,2
lb_weight = 100
blockemm-unknown = 1
blockemm-s = 0
blockemm-g = 1
blockemm-u = 0
boxid = 12345678

good luck

new2

read it

How to - Stop your cards being stolen by oscam users who are faking
This is a quick how to for those of you who want to protect your local card after the recent rise of card fakers/stealers. With oscam currently users can take your c line that you have given and put direct to oscam thus bypassing any reshare limits you set. They can then go one step furthur and fake your local with the 256 trick in cccam versions prior to 2.1.4. Nice and easy to use and just some settings to add.

Anticascading.

So if you have a peer who is doing re-sharing/faking do the following:

In your oscam config directory create a file oscam.ac and put in it:

#
# anti-cascading table
#
# format: <CAID>:<provider ID>=<seconds>

here is an example for sly italia . note the format as above
093B:000000 = 9
*=15

next

In your oscam.conf add following:
[anticasc]
enabled = 1
numusers = 1
sampletime = 2
samples = 5
penalty = 0
aclogfile = /var/log/oscam_ac.log
denysamples = 9
fakedelay = 1000

In oscam.user, for each guilty user add:
penalty = 1

This will work as follows:

oscam will sample every user for ecm requests for 15 minutes. If a bad, bad guy exceeds the limit oscam will send a fake cw for the next 9 samples. If in userfile you do penalty = 0 the user will not be punished but it will be logged in aclog file. Do not go too tight with the settings as people chnge channels and create additional ecm requests.
Above settings works a treat.

regards

new2

To use a new white ***UK viewing card, you need to ‘pair’ the card with the receiver in order for premium content such as movies and sports channels to decode correctly.
In order to do this, you need the serial number of the official receiver the card is paired with, you then need to convert this number into a hexadecimal binary, and insert it onto your configuration file.

This tutorial will guide you through manually converting the serial number, and inserting it. Online tools are available to convert the serial number into a boxkey for you, but as the serial number is unique to your account, and using the card in an unauthorized receiver is in breach if the terms of use of the viewing card, I would rather convert the number myself, instead of risk it being ‘farmed’ by a website.

There are a few ways to get the *** digibox serial number, the first is from the on screen menu. On standard and ***+ receivers, press services, 4, 5 and note the 10 digit serial number. On ***+HD press services, 0 ,3.
Another way is from the N$S barcode sticker on the bottom of the receiver, you only need the highlighted 10 digits from the fabricated example below

9F200300468953764

Now you have the number, you need to convert it to a hexadecimal binary, I use a free iPhone app called CP HexCalc, or an online calculator hexadecimal conversion, convert decimal to hexadecimal

Enter the 10 digit decimal number into your calculator, and press the HEX button. The example above will be converted to 2CB9110. A Boxkey needs to be 8 bytes, the converted decimal number is only 7 bytes (7 digits) so we need to add a zero to the beginning of it, making

02CB9110

Write your boxkey down and keep it safe, you will need to enter it into your appropriate cam configuration file.

enjoy

New2

credit 2 digidude

[cccam]
port = xxxx
reshare = 1
ignorereshare = 1
forward_origin_card = 0
version = 2.1.1
updateinterval = 240
minimizecards = 1
keepconnected = 1
stealth = 1
reshare_mode = 0

whats that bit ??????????

A quick how to for getting mgcamd up and running on an enigma 2 receiver capable of ipk manual installation..... I only tested on a dreamelite image . You may need a different ipk for a different image

step 1 > ftp to your receiver

step 2 > transfer over the following files to the /tmp directory

step 3 > change the file attributes of recently transferred files to 755

step 4 > use ipk installer on your image to install mgcam + mgcam configs

step 5 > once installed check in your softcam menu for addition of mgcam 1.35a . If it does not appear restart enigma2

step 6 > the configuration of config files . There are only 2 which you need ever edit. newcamd.list & mg.cfg ( usr/keys or var/keys )

so the configuration ....... from elsewhere in lamen terms

To configure the newcamd ( mgcamd ) protocol we will need to edit the parameters prescribed in the file newcamd.list, which is located in the /var/keys or usr/keys of the receiver. To edit all the files necessary we use an editor that understands the line ending characters and carriage return, used in the Linux files. (such as DCC - a popular tool )

The file newcamd.list default contains the following lines:

CWS_KEEPALIVE = 300
CWS_INCOMING_PORT = 21000
CWS = 192.168.1.1 20000 dummy dummy 10 02 13 04 15 06 17 08 01 10 11 12 13 14 lan server1
CWS_MULTIPLE = 192.168.1.2 20000:20005 dummy dummy 10 02 13 04 15 06 17 08 01 10 11 12 13 14 lan server2

The first line - CWS_KEEPALIVE sets the time in seconds after which the emulator MgCamd verifies connection to the server for car***aring spelled out in the port settings. Apply in the case of using NAT router, which disconnects inactive connections or when you open encrypted channels after the transition from open to them.
In the second line CWS_INCOMING_PORT given port to listen for incoming connections from the server, this line can be omitted.
Next in line CWS prescribed parameters cardsharing server to open a particular package.
Instead of 192.168.1.1 would require a real IP or domain address server car***aring, followed by the server port - 20000, instead of which prescribes working for a specific package of channels, then follow the login and password - dummy dummy, which is also the right to correct, then the DES key states - 10 02 13 04 15 06 17 08 01 10 11 12 13 14, which in most cases, changes to 01 02 03 04 05 06 07 08 09 10 11 12 13 14 and in custody should be - lan server1, which in most cases do not affect cardsharing work, and are only used when applying camdcmd protocol.

In the case of more than one port to open multiple channel packages, you need to add extra lines to the ports used, for example:

CWS = xxxxxxxxx.com 40000 login password 01 02 03 04 05 06 07 08 09 10 11 12 13 14
CWS = xxxxxxxxx.com 40001 login password 01 02 03 04 05 06 07 08 09 10 11 12 13 14
CWS = xxxxxxxxx.com 40002 login password 01 02 03 04 05 06 07 08 09 10 11 12 13 14

If ports are to be used in order, you can register them in one line:

CWS_MULTIPLE = xxxxxxxxx.com 40000:40002 login password 01 02 03 04 05 06 07 08 09 10 11 12 13 14

The second file i referenced to is the mg.cfg . This is not really needed to be edited unless you know what your doing. I shall post another tutorial just for this file . The default file will get you going though !!!
Enjoy

New2

Any questions post away

just go to the dm800 section and locate an image suitable for your clone receiver. This website does not contain any keys !!!!! . You would need a cam such as cccam on the image then you can load all your key files into the receiver. A bit of reading for u me thinks

new2

which card reader are u using ?

new2

this is a known issue with oscam using the smartreader protocol ( i.e bus:device id ) . The reason you didnt have such issue with cccam is because cccam assigns by usb port no ttyusb 1 2 3 4 5 for example. You can create rules for smargo in etc/udev depending on which linux distro you have. This then locks the smargos to the correct device id and never changes on reboot . Two factors 1 - linux distro & 2 which reader firmware version .

new2

check your pm

new2

paul

take your pick at working models

Railink chipset

USB: 0411:00F4 MelCo., Inc. (Device name unknown)
USB: 050D:7050 Belkin Components F5D7050 ver 1000 WiFi
USB: 050D:705A Belkin Components F5D7050A Wireless Adapter
USB: 050D:905B Belkin Components F5D9050 ver 3 Wireless Adapter
USB: 050D:905C Belkin Components Wireless G Plus MIMO Network Adapter
USB: 06F8:E010 Guillemot Corp. HWGUSB2-54-LB
USB: 06F8:E020 Guillemot Corp. HWGUSB2-54V2-AP
USB: 0769:31F3 Surecom Technology Corp. RT2573
USB: 07AA:002E Corega K.K. (Device name unknown)
USB: 07B8:B21D D-Link Corp. RT2573
USB: 07D1:3C03 D-Link System DWL-G122 802.11g Adapter [ralink rt73]
USB: 07D1:3C04 D-Link System WUA-1340
USB: 07D1:3C06 D-Link System (Device name unknown)
USB: 07D1:3C07 D-Link System Wireless G DWA-110 Adapter
USB: 0B05:1723 ASUSTek Computer, Inc. WL-167G v2 802.11g Adapter [ralink]
USB: 0B05:1724 ASUSTek Computer, Inc. RT2573
USB: 0DB0:6874 Micro Star International RT2573
USB: 0DB0:6877 Micro Star International RT2573
USB: 0DB0:A861 Micro Star International RT2573
USB: 0DB0:A874 Micro Star International RT2573
USB: 0DF6:90AC Sitecom Europe B.V. WL-172
USB: 0DF6:9712 Sitecom Europe B.V. WL-113 rev 2
USB: 1044:8008 Chu Yuen Enterprise Co., Ltd GN-WB01GS
USB: 1044:800A Chu Yuen Enterprise Co., Ltd GN-WI05GS
USB: 1371:9022 Dick Smith Electronics RT2573
USB: 1371:9032 Dick Smith Electronics C-Net CWD-854 rev F
USB: 13B1:0020 Linksys WUSB54GC 802.11g Adapter [ralink rt73]
USB: 13B1:0023 Linksys WUSB54GR
USB: 1472:0009 Huawei-3Com Aolynk WUB320g
USB: 148F:2573 Ralink Technology, Corp. RT2501USB Wireless Adapter
USB: 148F:2671 Ralink Technology, Corp. RT2601USB Wireless Adapter
USB: 14B2:3C22 Atheros Communications Inc C54RU
USB: 15A9:0004 (Vendor name unknown) (Device name unknown)
USB: 1631:C019 Good Way Technology RT2573
USB: 1690:0722 Askey Computer Corp. [hex] RT2573
USB: 1740:7100 Senao (Device name unknown)
USB: 18E8:6196 Qcom RT2573
USB: 18E8:6229 Qcom RT2573
USB: 18E8:6238 Qcom (Device name unknown)
USB: 2019:AB01 PLANEX GW-US54HP
USB: 2019:AB50 PLANEX GW-US54Mini2

new2

there is a second encryption layer for hd channels . |There are patched versions of oscam that use this method which is called a tweak key . However they are merely myth/rumours . The same tactic has now been used with irdeto for the nova provider. sd is fine but hd won't clear. I do not think HD on viasat will become public as not a very in demand card. But who knows i guess.

new2

n line close friends only in my opinion . can be abused to easily like caz has said

new2

yes

new2

I think this will work within a local network but i am sure the streams from within webif have a furthur port associated

new2

it may be buggy at times but its the best and only o/s for everything pc related unless you don't mind limitations then you could go with mac/linux

new2

pred your files look spot on . also notice that you are allowing unique & shared emm's which is the proper way. I am certain something in the emm process has changed and i'm sure those of you running that card as local will find out soon enough . As i said before oscam/mgcam for updating is best

new2