Posts by musogeek

Quote from AfyB

If you have only one reader, why are you using load balancer?

not sure if he said he has one reader - he has only posted the config for one reader:smile:

Loadbalancer isn't just for physical - it is used for virtual as well

Quote from andy ray

Cheers unique and shared are unticked already you may of seen
saveemm-u = 1
saveemm-s = 1

yep my bad lol - didn't notice that you had them on save rather than block. Should still update without saving them. Think the save option is to a file so would still update without this.

You have got your reader set as fallback? Usually this option wouldn't be set - any reason why it is set as a fallback reader?

not sure if it would be related but it is worth a try:thumbsup:

btw i just noticed that you are blocking all EMMs on your reader entry so your card won't update. Keep unknown and global blocked but allow the other 2 and it should update EMMs as long as you are leaving it on a channel that your card clears.

for dvbapi to work you need an entry in oscam.conf for dvbapi and an account in oscam.user that relates to the dvbapi entry in oscam.conf. Try changing yours to the following;

oscam.conf

[dvbapi]
enabled = 1
au = 1
boxtype = dreambox
user = dvbapi_dreambox

oscam.user

[account]
user = dvbapi_dreambox
pwd =
group = 1
monlevel = 0
au = 1

au = 1 sends updates to all cards, so if you have more than one card and each are in different groups then as far as I can see you can add extra groups, although I have never tried it with more than one card.

add peer user accounts and readers as normal.

I have dowloaded and installed the latest vti image - and the hbbtv function is working - it is very nice - shame I can't speak German (a lot of content on the German channels) - but my wife can speak German so at least I have a translator at hand!

try the following - delete what i have highlighted in blue.

[reader]
label = omnikey
protocol = pcsc
device = 0
caid = 0963
ecmwhitelist = 0963:3E,4E,4F,42,44,45,47,53,54,56,61,6A,6B,6D,6E, 6F,62,67,68,69,7A,7C,7D,7E,71,72,73,77,78,79,80,8B
detect = cd
mhz = 357
cardmhz = 357
group = 1
blockemm-unknown = 1
blockemm-u = 1
blockemm-s = 1
blockemm-g = 1
blockemm-bylen = 183,81
blocknano = all

[global]
usrfile = /var/log/oscam/oscamuser.log
logfile = /var/log/oscam/oscam.log
cwlogdir = /var/log/oscam/cw
clienttimeout = 7500
failbantime = 1440
nice = -1
maxlogsize = 4096
saveinithistory = 1
dropdups = 1
lb_mode = 1
keepalive = 1

[monitor]
port = 988
aulow = 120
hideclient_to = 15
monlevel = 1
appendchaninfo = 0

[newcamd]
port = *****
key = *****

[cccam]
port = *****
reshare = 0
ignorereshare = 1
version = 2.1.4
stealth = 1

[webif]
httpport = *****
httpuser = *****
httppwd = *****
httprefresh = 10
httpallowed = 127.0.0.1,192.168.1.1-192.168.2.4
httpdyndns =
httphideidleclients = 1

[anticasc]
enabled = 1
numusers = 1
samples = 5
penalty = 1
aclogfile = /var/log/oscam/aclog.log
denysamples = 4

reasons for above changes -

the blocknano and block emmbylen are fairly new functions and most don't use these - you can try to keep them as less likely to be causing the issues you are having
Best not set ignorereshare to 1 especially if you have virtual cards (reader accounts in oscam.server from peers) on your server, or you could be abusing the share based on what reshares you should have. You can set reshare to 1 if you want in the cccam part of oscam.cfg - I didn't highlight this, but best changed to 1 if you are cardsharing as the norm is to offer your card with one reshare.

get rid of anticascading completely - this is probably the cause of your issue - if you are sharing with friends and family then it isn't something you need - if you do need it, change the penalty to 0 so you just keep a log. Problem with having too many log files in the pi is the limited space, so i would still get rid if it all together. You can check peer's usage by other means, and if there are issues, then you can just drop them an email!

This receiver isn't the best when it comes to using anything apart from FTA channels - however I managed to get past the test failing, and managed to get it to pass. I think you need to look at the way you are typing the server address in the box - not 100% sure of the format, but it is a case of splitting the nline or cline down to the dns/ip, port, username and password etc - no putting in C: or N: - there is also a way you can see the password as you are typing it in to make sure there are no errors there. I haven't got this receiver any more so can't be of more help sorry.

ok we will leave telnet for now - but I am assuming one of two things - either the IP address or other details you are using is not correct, or the receiver isn't connecting to your network correctly. Check your network settings and try again.

are you able to telnet the box?

Raspberry pi can work fine as a server. You need to understand that it the specs are not high, so use it as a dedicated server, so it is not doing anything else. firstly, you need to set it up correctly either by attaching a keyboard to configure it or by logging in to it with a PC with a SSH client (think you may have had to enable SSH on the Pi first before you can connect - I am not sure if it defaults to enabled)

type the command 'raspi-config'
firstly, expand root partition to fill SD card
then change the memory split, so it is using as little as possible to the graphics. You don't need the GUI so it is a waste of memory.

Also there are a couple of cron jobs you can set up.

type 'sudo nano /etc/crontab'

you will get a basic text editor - and from this - i have added a couple of lines.

05 * * * * root echo 3 > /proc/sys/vm/drop_caches
45 05 * * * root /sbin/reboot

you save this by ctrl x then y. Then reboot the Pi

the above clears the raspberry pi's cache regularly and also reboots the machine at 5.45am every morning.

Also you could do with a class 10 SD card - I had a class 4 and it run hot and melted.

this helps the pi run smoothly, but could still be the Oscam configs causing the problem, so might me a help if we knew these.

can add the ident but won't improve your ecm times

Banny
'device = 0' is because he is using an omnikey and is correct.

bear in mind that some cards have higher ecm times anyway and if working ok then there isn't really a reason to be overly concerned.

dont know too much about scam - I updated in the receiver - i am running vu+ duo and downloaded scam from tspanel -it had configs already there - and i just disabled other cams and started scam and it updated.

If you haven't got a viaccess cam, use scam - i used scam 3.60 and it worked a treat

when you are trying to edit the interfaces file, are you logged on as root?

As far as I am aware, there aren't any that work. I always thought that only dvb-t tuners worked - but I might be wrong....

cheedd you have been a member since april and you still haven't posted an intro post -
Introductions
you are lucky you got a reply - please post an intro first if you want to take partbeer10

http://linuxsat-support.com/fo…ease-read-rules-here.html

Please read rule number 1....

Quote from Sandman

Interesting wording...they cost sly £10k....I wonder if they actually made any money on it?!

Exactly my thoughts - it states the £10,000 8 month loss to sly, which implies that this loss is down to loss of subscription charges that would have been gained if the people who shared with them had otherwise subscribed to sly. Would these people have subscribed to sly if there wasn't an alternative? Maybe not - so firstly, how can sly suggest that this is a loss? Secondly, there is no mention of profit gained by those prosecuted, so were they actually payservers at all, or were they just helping out their friends and family by sharing their card?

http://linuxsat-support.com/am…ccam-amico-alien-2-a.html

Another thread on the topic where another member who has two of these boxes states that CCcam does not work on these boxes. I have done a quick search and I have seen a couple of pointers towards Cccam 2.1.4 working on spark, some people suggesting that it only works as client, and others saying it doesn't.

Usually - sh4 boxes such as this receiver Qbox and the AZbox have issues running CCcam.

Is there anyone here who does have this receiver who can confirm that they have had CCcam running with full functionality on this receiver??

If you are using a device that doesn't support CCcam, then often it will support Oscam, which is true for this receiver. Oscam takes some learning and configuring to get it up and running, but will do the job. I am sure there are some out there who have the receiver who will help, but unfortunately, most of us have probably a couple of receivers each tops and this is a fairly new kid on the block.