oscam and satlover

[asus7]

Re: oscam and satlover

what version of oscam do you suggest to install in dm500s? Always the last one?

Various versions of oscam are evolving every day ... the choice is yours.
Unfortunately, sometimes some have many more bugs...

[BlueIsMyColor]

Re: oscam and satlover

Various versions of oscam are evolving every day ... the choice is yours.
Unfortunately, sometimes some have many more bugs...

That's why i asked if there exist one version that is more used by satlover members. I tried "oscam-stable-1.10" but does not have some options like newer ones.

[mirny]

Re: oscam and satlover

That's why i asked if there exist one version that is more used by satlover members. I tried "oscam-stable-1.10" but does not have some options like newer ones.

there is not any reccomended oscam binary, because everyone has
a different receivers with different processors.
anyway saatlover "recommends" cccam, for dvbs cards is recommended
this _http://www.satlover.eu/index.php?ind=news&op=news_show_single&ide=4

[gianni253]

Re: oscam and satlover

I suggest to use always one of the latest versions from trunk 1.20, unless it is known to have a serious bug.
You will have latest features and prompt support from developers if something is not working as expected.

[ocin]

Re: oscam and satlover

I'm newbe in oscam. I was suggested oscam 1.20 everywhere it was unstable. It works fine for me, without a y serious problems. Friendly to configure it by webif.

[ZoxPa]

Re: oscam and satlover

Only way to find version of oscam that is good for you is to try different versions of oscam-unstable. One is good, other is bad, there is no rule. Try to use last version, if it is bad go to version before it.

[gianni253]

Re: oscam and satlover

I'm newbe in oscam. I was suggested oscam 1.20 everywhere it was unstable. It works fine for me, without a y serious problems. Friendly to configure it by webif.

Maybe you misunderstood something .. 1.20 is called "unstable" but it is not unstable at all !

[knap92]

Re: oscam and satlover

Hy

I m using this version _OSCAM 1.20-unstable_svn build #7099 for more than 2 weeks now and i didt get any probleme with it ,and the config of the oscam is also importante

Regards

[gianni253]

Re: oscam and satlover

I am using 1.20 too, svn 8444 ... not a problem, and the binary is very compact: 342KB only !

[mirny]

Re: oscam and satlover

knap, gianni could you state, how many proxies/clients you've got
and your uptime?
because its different when you ruuning one local just for you, or another receiver in home in LAN. and other is two or more locals, with 10/20 (proxies/clients) of course it depends on receivers HW.
are you restarting it daily, or it is running 2weeks in a row?

[gianni253]

Re: oscam and satlover

more than 20 clients in vpn.
dm500s dedicated server.
one weekly reboot is scheduled, but uptime could be even longer (just to be safe and keep the system "fresh and clean")

[BlueIsMyColor]

Re: oscam and satlover

When i try to use oscam i get this message many times: "by timeout (5002ms)" and everything remains black for some seconds. What does this means?

[gianni253]

Re: oscam and satlover

Timeout time (5 seconds) have been exceeded.
To give a sense to this message we should know your config files (client and server)

[BlueIsMyColor]

Re: oscam and satlover

my configs:

oscam.conf

[global]
logfile = /tmp/oscam.log

[dvbapi]
enabled = 1
decodeforever = 1
user = dm500
boxtype = dreambox

[webif]
httpport = 83
httpuser = user
httppwd = pass
httpallowed = 127.0.0.1,192.168.1.0-192.168.1.110

oscam.server

[reader]
label = ***xx
protocol = cccam
device = ***xx,***xx
user = ******
password = ***xx
inactivitytimeout = 30
group = 1
emmcache = 1,1,2
cccversion = 2.0.11
cccmaxhops = 1
cccwantemu = 1
ccckeepalive = 1

oscam.user

[account]
user = dm500
pwd = dm500s
group = 1
keepalive = 1
au = 1

[gianni253]

Re: oscam and satlover

5000 ms is default timeout of the reader section for "client timeout".
There are 2 other parameters for timeouts, but it's not your case.
If your reader points to a free server, it's normal: it just states that oscam client didn't get an answer within 5 seconds.
If you can tolerate a longer timeout because the crypto system can wait longer for the dcw, then you can increase this parameter (for example "clienttimeout = 6000").
Bye