Posts by i290975

    If anyone has time please have a look at my configs.


    Cheers


    oscam.conf


    [global]
    logfile = stdout
    nice = 1
    preferlocalcards = 1
    readerrestartseconds = 2
    dropdups = 1
    block_same_ip = 0
    block_same_name = 0
    failbantime = 5
    failbancount = 5


    [cache]


    [newcamd]
    port = ****************
    key = ***************
    keepalive = 1


    [dvbapi]
    enabled = 1
    au = 1
    reopenonzap = 1
    user = ********
    boxtype = dreambox


    [monitor]
    port = *********
    monlevel = 4
    hideclient_to = 15


    [webif]
    httpport = *****
    httpuser = *****
    httppwd = *****
    httprefresh = 10
    httphideidleclients = 1
    httpallowed = ***************
    hideclient_to = 15


    oscam.server


    [reader]
    label = lower_card
    protocol = internal
    device = /dev/sci0
    caid = *****
    detect = cd
    mhz = 3150
    cardmhz = 3150
    group = 1
    emmcache = 1,3,2
    blockemm-unknown = 1
    blockemm-g = 1
    ndsversion = 2


    oscam.dvbapi


    P: ***** "my card's four digit ID"

    Having researched this some more it seems there was a general broadcast problem when it happened two weeks ago. Can't find anything about a general problem yesterday when I last had the problem. It may not be a load problem with oscam server after-all. I'd still love to hear people's suggestions for using the VU duo to ease the load on the DM500.

    Hi


    Oscam r9698 running on DM500 gets glitchy when a lot of clients are sending requests, usually during a match. Has anybody got a suggestion how I could use my VU duo to reduce the load. I don't want to use my VU duo as the card reading server but would use it as a proxy or cacheex partner.


    Cheers

    Does this need to be done on all recent builds?


    3150MHZ for sly UK - is it sat box or omnikey as well?


    Thanks


    This setting on the OSCAM web interface says;


    Dreambox Mipsel: 2700, PPC: 3150, DM7025: 8300


    As far as I know the 3150 applies to Power PC binaries only. I'm not sure what binaries sat box and omnikey use. I'm sure someone else on the forum can give you a definitive answer.

    Hi,


    I'm running OSCAM 1.2 r8852 on DM500. Recently tried upgrading to OSCAM versions 8963, 9003, 9058, 9062 and 9063. Each upgrade resulted in ecm times increasing 10 fold i.e. approx 90 ms to 900 ms. I changed back to version 8852 and ecm times are back to normal. Anybody got any suggestions?


    Cheers

    I've always read that a USB key was the best place for egp.dat?? I'd be happy to ditch my USB key because it regularly interferes with reboots from my VU Duo

    Plenty of tutorials with screen shots to help you are available all over the web. There is no short answer to your question. You need to read two or three tutorials on setting up dreamboxes. You better find out what satelite your dish is pointed at, you'll need to know this to scan the channels. The gemini image may well be configured for the satelite you want as it was in use nearby.

    The downloaded nabilosat reboot and stanby scripts won't run through scheduler. They do run manually from telnet. The restart EMU scheduled job does run. Both downloaded scripts are set to 755. Anyone know how I can setup a debug log?


    PS. This is not a crond issue, nabilosat darkstar II has an internal cron service

    You don't need two different ports on your dreamboxes. You do need two different ports on your router. Your router should be able to translate the incoming requests to the seperate IPs, using the same ports wont matter once you have two seperate IPs. Just in case you don't want to change the listening ports on your DM500s.

    Hi, VU+ DUO that gives no problems ever except when I use a usb key to store the EPG. Each night I do a 'deep standby' on the box. Next morning roughly every fourth time the box will hang on restart, the LED screen says 'restarting'. A hard reset gets over the problem but its a pain in the neck for an otherwise perfectly functioning box. I use VIX images, have used 2.2 and now use 3.0, the problem has appeared under both images, besides its most likely a boot loader problem so the enigma version is probably of little relevance. Any help or suggestions would be gratefully appreciated.