Posts by prof

    what is the aim of the ecm header whitelist and what is the difference between it and oscam whitelist


    Provider Satellite CAID Provider ID Card Crypt ECM Header Whitelist: (value in hex) additional information
    B***B/FreeCard 28,2° East 0963 000000 ? NDS 80703B00,80704200,80704400,80705F00,80706500,81703B00,81704200,81704400,81705F00,81706500



    and oscam whitelist for sly


    0963:000000::::B3,B4,B7,3B,3E,42,44,45,47,4B,4E,4F,50,53,54,56,5F,6A,6C,61,62,64,65,66,67,68,69,6A,6B,6C,6D,6E,6F,70,71,72,73,74,76,77,78,79,7A,7C,7D,7E,80,82,85,8B,89,9A # B***B 28.2E
    0963:000000::::3E,41,42,44,45,5E,5F,65 # B***B FreeCard 28.2E

    i have flashed the brand new vu duo with vix 3.0 image but after doing the motorised setup with tuner A advanced mode controlling the motor and tuner be as cable connected to lnb. the motor is moving outside with same value as my dm800 longitude. but when i tried to scan i can not pick any channels. so i tried to connect the vu duo to my sly fix dish and there as well no signal through. i wonder if there is a fault with the tuner or is this common with vu boxes.
    i have tried the italisat 4 image as well no joy
    can someone point me into the right direction here please
    cheers

    my cccam crached today and here was the message i got from kernel window:



    stack smashing detected ***: /emu/cccam/CCcam.x86_64 terminated
    ======= Backtrace: =========
    /lib/libc.so.6(__fortify_fail+0x37)[0x7f7932b0c047]
    /lib/libc.so.6(__fortify_fail+0x0)[0x7f7932b0c010]
    /emu/cccam/CCcam.x86_64[0x432595]
    /emu/cccam/CCcam.x86_64[0x433530]
    /emu/cccam/CCcam.x86_64[0x42322d]
    /emu/cccam/CCcam.x86_64[0x47cd2c]
    /emu/cccam/CCcam.x86_64[0x47ce4e]
    /lib/libpthread.so.0(+0x68ca)[0x7f793353c8ca]
    /lib/libc.so.6(clone+0x6d)[0x7f7932af792d]
    ======= Memory map: ========
    00400000-004e3000 r-xp 00000000 08:01 269306 /emu/cccam/CCcam.x86_64
    006e3000-006e5000 rw-p 000e3000 08:01 269306 /emu/cccam/CCcam.x86_64
    006e5000-006eb000 rw-p 00000000 00:00 0
    01eb9000-02047000 rw-p 00000000 00:00 0 [heap]
    7f79297fb000-7f79297fc000 ---p 00000000 00:00 0
    7f79297fc000-7f7929ffc000 rw-p 00000000 00:00 0
    7f7929ffc000-7f7929ffd000 ---p 00000000 00:00 0
    7f7929ffd000-7f792a7fd000 rw-p 00000000 00:00 0
    7f792a7fd000-7f792a7fe000 ---p 00000000 00:00 0
    7f792a7fe000-7f792affe000 rw-p 00000000 00:00 0
    7f792affe000-7f792afff000 ---p 00000000 00:00 0
    7f792afff000-7f792b7ff000 rw-p 00000000 00:00 0
    7f792b7ff000-7f792b800000 ---p 00000000 00:00 0
    7f792b800000-7f792c000000 rw-p 00000000 00:00 0
    7f792c000000-7f792c03a000 rw-p 00000000 00:00 0
    7f792c03a000-7f7930000000 ---p 00000000 00:00 0
    7f7930167000-7f7930168000 ---p 00000000 00:00 0
    7f7930168000-7f7930968000 rw-p 00000000 00:00 0
    7f7930968000-7f793097b000 r-xp 00000000 08:01 408004 /lib/libresolv-2.11.3.so
    7f793097b000-7f7930b7a000 ---p 00013000 08:01 408004 /lib/libresolv-2.11.3.so
    7f7930b7a000-7f7930b7b000 r--p 00012000 08:01 408004 /lib/libresolv-2.11.3.so
    7f7930b7b000-7f7930b7c000 rw-p 00013000 08:01 408004 /lib/libresolv-2.11.3.so
    7f7930b7c000-7f7930b7e000 rw-p 00000000 00:00 0
    7f7930b7e000-7f7930b83000 r-xp 00000000 08:01 408019 /lib/libnss_dns-2.11.3.so
    7f7930b83000-7f7930d82000 ---p 00005000 08:01 408019 /lib/libnss_dns-2.11.3.so
    7f7930d82000-7f7930d83000 r--p 00004000 08:01 408019 /lib/libnss_dns-2.11.3.so
    7f7930d83000-7f7930d84000 rw-p 00005000 08:01 408019 /lib/libnss_dns-2.11.3.so
    7f7930d84000-7f7930d86000 r-xp 00000000 08:01 409495 /lib/libnss_mdns4_minimal.so.2
    7f7930d86000-7f7930f85000 ---p 00002000 08:01 409495 /lib/libnss_mdns4_minimal.so.2
    7f7930f85000-7f7930f86000 rw-p 00001000 08:01 409495 /lib/libnss_mdns4_minimal.so.2
    7f7930f86000-7f7930f92000 r-xp 00000000 08:01 408002 /lib/libnss_files-2.11.3.so
    7f7930f92000-7f7931191000 ---p 0000c000 08:01 408002 /lib/libnss_files-2.11.3.so
    7f7931191000-7f7931192000 r--p 0000b000 08:01 408002 /lib/libnss_files-2.11.3.so
    7f7931192000-7f7931193000 rw-p 0000c000 08:01 408002 /lib/libnss_files-2.11.3.so
    7f7931193000-7f7931194000 ---p 00000000 00:00 0
    7f7931194000-7f7931994000 rw-p 00000000 00:00 0
    7f7931994000-7f7931995000 ---p 00000000 00:00 0
    7f7931995000-7f79321f6000 rw-p 00000000 00:00 0
    7f7932227000-7f7932228000 ---p 00000000 00:00 0
    7f7932228000-7f7932a28000 rw-p 00000000 00:00 0
    7f7932a28000-7f7932b81000 r-xp 00000000 08:01 408011 /lib/libc-2.11.3.so
    7f7932b81000-7f7932d80000 ---p 00159000 08:01 408011 /lib/libc-2.11.3.so
    7f7932d80000-7f7932d84000 r--p 00158000 08:01 408011 /lib/libc-2.11.3.so
    7f7932d84000-7f7932d85000 rw-p 0015c000 08:01 408011 /lib/libc-2.11.3.so
    7f7932d85000-7f7932d8a000 rw-p 00000000 00:00 0
    7f7932d8a000-7f7932da0000 r-xp 00000000 08:01 408003 /lib/libgcc_s.so.1
    7f7932da0000-7f7932f9f000 ---p 00016000 08:01 408003 /lib/libgcc_s.so.1
    7f7932f9f000-7f7932fa0000 rw-p 00015000 08:01 408003 /lib/libgcc_s.so.1
    7f7932fa0000-7f7933020000 r-xp 00000000 08:01 408024 /lib/libm-2.11.3.so
    7f7933020000-7f7933220000 ---p 00080000 08:01 408024 /lib/libm-2.11.3.so
    7f7933220000-7f7933221000 r--p 00080000 08:01 408024 /lib/libm-2.11.3.so
    7f7933221000-7f7933222000 rw-p 00081000 08:01 408024 /lib/libm-2.11.3.so
    7f7933222000-7f7933318000 r-xp 00000000 08:07 786456 /usr/lib/libstdc++.so.6.0.13
    7f7933318000-7f7933518000 ---p 000f6000 08:07 786456 /usr/lib/libstdc++.so.6.0.13
    7f7933518000-7f793351f000 r--p 000f6000 08:07 786456 /usr/lib/libstdc++.so.6.0.13
    7f793351f000-7f7933521000 rw-p 000fd000 08:07 786456 /usr/lib/libstdc++.so.6.0.13
    7f7933521000-7f7933536000 rw-p 00000000 00:00 0
    7f7933536000-7f793354d000 r-xp 00000000 08:01 408006 /lib/libpthread-2.11.3.so
    7f793354d000-7f793374c000 ---p 00017000 08:01 408006 /lib/libpthread-2.11.3.so
    7f793374c000-7f793374d000 r--p 00016000 08:01 408006 /lib/libpthread-2.11.3.so
    7f793374d000-7f793374e000 rw-p 00017000 08:01 408006 /lib/libpthread-2.11.3.so
    7f793374e000-7f7933752000 rw-p 00000000 00:00 0
    7f7933752000-7f793375a000 r-xp 00000000 08:01 408017 /lib/libcrypt-2.11.3.so
    7f793375a000-7f7933959000 ---p 00008000 08:01 408017 /lib/libcrypt-2.11.3.so
    7f7933959000-7f793395a000 r--p 00007000 08:01 408017 /lib/libcrypt-2.11.3.so
    7f793395a000-7f793395b000 rw-p 00008000 08:01 408017 /lib/libcrypt-2.11.3.so
    7f793395b000-7f7933989000 rw-p 00000000 00:00 0
    7f7933989000-7f79339a7000 r-xp 00000000 08:01 408007 /lib/ld-2.11.3.so
    7f7933b8a000-7f7933b8f000 rw-p 00000000 00:00 0
    7f7933ba3000-7f7933ba6000 rw-p 00000000 00:00 0
    7f7933ba6000-7f7933ba7000 r--p 0001d000 08:01 408007 /lib/ld-2.11.3.so
    7f7933ba7000-7f7933ba8000 rw-p 0001e000 08:01 408007 /lib/ld-2.11.3.so
    7f7933ba8000-7f7933ba9000 rw-p 00000000 00:00 0
    7fff665c3000-7fff665d8000 rw-p 00000000 00:00 0 [stack]
    7fff665ff000-7fff66600000 r-xp 00000000 00:00 0 [vdso]
    ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]



    any idea what is the cause of this
    i have just run an update of sofies and see if this is due corrupt libraries

    all the configurations files are on pc server and the card is read through oscam with omnikey on pc server. my dm is just an other client on the system.
    i wanted to block all the emm in pc cccam server and therefore have my dm800 as my sole point of updating my card. so my main cccam server that i use to share with will not have anymore emm allowed through. been thinking about this. the plan was to get an Nline to dream downstairs and trick cccam with 256 so my sly will still appear as local card and have priority from same sly card that will come in through my main cccam sharing server as hope1. so really i want to bypass my main sharing server and have the card update though the nline from oscam pc server to my dm800

    hi guys,
    i am moving to oscam pretty soon but i have reservations about updating my sly card. i have updated in the past through cccam2.1.4 and has work fine for the past two years. i have a pc server wich has a cccam and oscam running. AS suggested in previous posts people get their card through their cccam server by offering their trusted peer(s) a cline with F line enabling emm update.
    i want to send an line to my dm800 and if possible have my dreambox update the card without passing through my cccam server
    so my setup would look like this
    No1 Nline from oscam to my dm800 cccam.cfg
    N: 192.168.1.xx 10000 dm800 dmpass 01 ........14 256 yes
    is this yes necessary here for allowing share emu for the card to work
    i want to get emm sent to my card through this nline
    the reason behind it is i want to block emm and unnecessary info from my pc server cccam ( DISABLE EMM: no ) so that my peers and client wont be able to see it anymore. for this reason i want to unbale the EMM only in dm800 which will serve as card updater and beause it has laready an nline trick with256 i will still have the cline from my pc server cccam that suppy me with all the other shared card so i dont have to switch to mgcamd or dvapi to get card to update.

    thank DidI .for ur input. but I don't know if u understood my question.
    I want to give Nilne from my csp to my cuzin. I want my cousin to
    connect to my csp . as I said I can make a Nline to connect locally. all ports are forwarded already just wanna dish out an Nline to my couz
    who lives in a different town
    cheers

    my port in the router is fowarded ok as i can connect locally to my dreambox from the csp
    my problem is how to go get to connect to my cousin who i gave an nline too with my domain name. is there anypart in the xml where i have to include the domain.dyndns.org
    i have seen in it if u want to exchange cache there is a section where u include the domain name and port for cache exchange. what do u do if u just want to exchange n line with a trusted friend

    hi guys,
    i finally got my csp working. i can connect to cccam server using my local ip 192.168.1.Xx from my pc to my dreambox it working fine.
    now i wanted to give the nline with domain.org on to my cousin but i can not coonect him to my csp
    here the profile for sly
    <profile name="SLYUK" ca-id="0963" network-id="0002" enabled="true" debug="false">
    <newcamd listen-port="21111">
    <card-data type="config" ca-id="0963">
    <providers>00 00 00</providers></card-data></newcamd>
    <max-cache-wait>1500 ms</max-cache-wait>
    <max-cw-wait>3500 ms</max-cw-wait>
    <filter-cards>provider</filter-cards>
    <services-file format="cccam" ca-id="0963" filter="000000">/var/etc/CCcam.channelinfo</services-file>
    </profile>


    <user-manager class="com.bowman.cardserv.SimpleUserManager">
    <auth-config>
    <user name="admin" password="secret" max-connections="3" admin="true"/>
    <user name="user1" password="secret1" profiles="SLYUK"/>

    </auth-config>
    </user-manager>


    HERE is the nline i am giving him with port forwarded as tcp in router


    N: mydomain.org 21111 user1 secret1 01 02 03 04 05 06 07 08 09 10 11 12 13 14
    but my cousin is unable to connect to my csp from his house
    can someone help with this nline with dns setting please


    cheers

    hi folks,
    i need help in running cccam in debug mode
    my current setup is this:
    usr/local/bin cccam.x86_64 -C var/etc/CCcam1.cfg
    now i want to implent this
    usr/local/bin/CCam.x86_64 -C var/etc/CCam1.cfg -dv >> var/log/debug.txt
    i have tried this but i got an error with -dv