Posts by musogeek

    add this to the peer account in oscam.user


    Code
    hostname = dnsorip.of.peer


    obviously replacing after the = the ip address or dns of your peer!

    You should be able to share to client using CCcam protocol - configs look ok - but there is no need to define CAID and IDENT on account in oscam.user in your setup. Not sure if it will help (according to oscam wiki you have applied the correct format) but worth a mention. Does it work if you placed both cards in group 1?

    How are you set up? Do you have oscam as cardreader and cccam as server? If so is there a possibility that cccam is reading your card, but a full server restart would often cure this rather than just an oscam reboot. in oscam webinterface is your card still showing as working?
    Not ecm whitelist error as the ones being requested are included.


    only channels 1-4 are now supported on hotbird. Could be related to this.

    Same problem here, changed HDMi cable, no help. Tried update front panel from 20018 to 20026, no go, doesn't update. Running openvix: build 747. Display worked with 743, but I've been testing so many plugins etc that can't say if openvix is causing display issues.


    - I've owned box for a week and display is only thing I've(?) messed up.


    First post should be here
    Introductions
    Also can you clarify what the issues you are having with the front panel? is it the same as stevejo's issues or something different?
    Have you tried a clean install of 747?
    Panel running fine here with latest EGAMI image.

    Hope someone has an answer, my duo2 switches on from standby
    during the night so how do I stop it.thanks in advance for your help.


    Do you have any timed events such as recordings, epg downloads or autobouquets updates?


    Are you getting up in the middle of the night and watching TV in your sleep? :popcorn:


    go to the setup - timers - power timers, and see if there is anything there that shouldn't. You can also create a new power timer, and set up a standby event if this is being caused by downloads or updates you have set.


    I have had issues with receivers staying awake after updates before, but ViX doesn't usually give me this issue.

    http://linuxsat-support.com/nb…rmware-usb-step-step.html


    I have installed to HDD following above - USB should be similar - I just deleted a miniguide I did from memory but I haven't got a good memory because it didn't work.:laugh: The trick is that you need to have USB stick formatted so there is a Swap and an EXT3 partition, then you need to unpack the image on to the USB drive maintaining correct file structure and permissions, and then you have to tell the NBOX to boot from it.

    im setting up a uk server in november, 4 quadcore stream servers based in holland, super fast reliable. with uk package and also. jsc sports , up and running at the minute, but,, still on trial see how it performs..


    i will have to charge but no where near as much as the daft prices mag servers charge, mnthly charge around 19£
    to pay for server costs and upkeep.. for member of linuxsat only.. working on key encryption and ip and mac system for mag250 boxs, or the blade stream boxs.


    Thanks for that advert - unfortunately this is effectively advertising yourself as a payserver. An example of what will be the new breed of payerver once sharing stops being possible, because of payservers spoiling it. This is a hobby. You are wanting to make money out of it. You are no longer welcome here.

    any reports on what this firmware is like. stable, any features, etc? cheers Has there been an update since May?


    I must say it is very stable - 8.3 is the latest version. Features are very limited to say the least, no plugins repo set on the image at all, but as I noted here;
    http://linuxsat-support.com/nb…esolution.html#post140399
    you can install plugins manually, either using IPK, or for some IPKs that won't install (reports as wrong architecture as for mipsel) you can unpack the IPK and send the folder to the plugins folder - this worked well for CoolTVGuide 6.4.0 version for OE 1.6

    Anyone got any pointers on how to install this to the HDD? i assume i can use the Pen version, i have installed Hyperion to the HDD before but this was in a .*.tar.gz format where this one is a img file .
    I have my partitions setup and i have also configured duo boot for it, so i have freebox loader for this image, just a bit lost as to the install of it. I dont want it in NAND as i have Nebula Zero there and its nice and stable.


    Not sure if it would work based on what I read here
    http://linuxsat-support.com/nb…2-openpli-hard-drive.html

    i`ll give it a go this evening with the different files, willy question but where would i check the kernal version ?:83:


    I am hoping someone else can answer this! - On some images the kernel version might be displayed by pressing menu - information - about, but on OpenPLi 8.3 it doesn't have that info and I realised the version by searching the net and looking at the info posted with the image. As I said I have only seen it confirmed as working with OpenPli 8.3 and have only confirmed that it is working with that myself. OpenPLi runs fine and stable from NAND, but the problem is that there is no Plugin repo, so all plugins have to be installed manually, which isn't a massive problem so long as you are comfortable installing manually. I am sure somewhere there are other options, probably posted somewhere in Polish. I have this working with autobouquets, CrossEPG, CoolTVGuide 6.4 and autotimer, so it is worth it in my opinion to build from scratch. Because of the limitations such as lack of boot options, finer control, backups etc (it really takes a lot of manual configuring), another idea would be to have a version of this installed to a USB drive (I will post the USB version here a bit later on this eve or tommorow) - and you could switch to the patched version when you want to watch some HD footy!

    I am getting that you are wanting to put your reader entries (peer) in oscam and then send them to client on your own network. It is good practice to put each real card in a separate group - some put each peer in a separate group as well, this keeps things separate - but it is usually ok to put all peer reader entries in the same group. You have enabled CCcam protocol, that is fine, but you also need to have a separate entry in oscam.user and corresponding cline on client. so long as you only do this for a local reader and not for remote reader (this would be seen as abusing reshare rights) it is ok to ignore reshare values so you get all of the service you would get if the client for the peer was running in the receiver. in the reader account for your peer - change group = 1 to group = 2


    in oscam.user - add the following;


    Code
    [account]
    user                          = local
    pwd                           = pass
    keepalive                     = 1
    group                         = 2
    cccmaxhops                    = 3
    cccreshare                    = 0
    cccignorereshare              = 1


    the above will share everything in group 2, ignoring reshare level and without giving reshare - and as I said this should only be used for a client in your own lan that is not acting as a server in its own right. You have an nline for the local to share with your local receiver, but you can if you want scrap the nline and just use CCcam protocol. To do this you can delete the original user entry you have, and delete the nline on your client and just use a cline (and you can also delete the newcamd entry in Oscam), but if you do this then you will need to bear in mind the reader entry for your local is in group 1 - so on the above simply change group = 2 to group = 1,2


    on your local receiver, (CCcam) you need to add a cline - change your ip address to the ip address of your oscam server


    Code
    C: ip.address.of.server 25125 local pass


    Now - if you are wanting to share outside your own network, the reshares from your virtual reader and your local card important remove the cccignorereshare entry. Add something like this to oscam.user for each peer


    Code
    [account]
    user                          = peer
    pwd                           = peerpass
    hostname                      = yourpeers.dns
    uniq                          = 3
    group                         = 1,2
    cccmaxhops                    = 2
    cccreshare                    = 1


    this will share your local and reshares up to your hop 2 with a reshare value of 1 hop down, will restrict your user to one log on (only last login will be allowed), and lock the account to their IP address. Ensure you have forwarded the port used in cccam entry of oscam.conf (in your case 25125) in your router to the server local IP address. You then give your peer cline


    Code
    C: your.dns 25125 peer peerpass


    Remember - you have just advertised your port - so if you are wanting to set this up for external shares then you should use a different one!