Posts by musogeek

the beauty of Oscam is that you can easily control your shares. Best way to do this is to set up an oscam.services file. You can do all this in the web interface, or maually by editing the right files. you can set up an entry based on just caid, (0963 for sly, etc) caid and provid (000000 for sly etc) or caid, provid and srvid (individual services) - example

[jsc]
caid                          = 0500
provid                        = 042400
srvid                         = 0074,20F5,20F6,20F7,20F8,20F9,20FA,20FB,20FC

once this is set up, then you can deny the above services to whatever peer you like by adding this to their account in oscam.user

services = !jsc

note above the '!' behind the name of the services definition is what creates the denial of what is defined for jsc, but will allow everything else

services = jsc

above without the '!' means that you are allowing it, but will deny everything else

you can create more definitions in oscam.services, and you can add them to the services =, each separated by a commar, but stick to either ! or not ! - don't mix them.

also the definitions in oscam.services can define just caid and provid, so you can allow or block whole cards.

Once you have defined a service in oscam.services, these are presented as tick boxes for positive and negative services in the webinterface in each user account, and reader entry - so as well as choosing what you give, you can choose what to accept.

Not sure about vix image but I know that some skins have settings - such as if the HD Glass skin was used there are ways to turn the options on or off so things like server info is not displayed. I know you have already thought about skins and you should now realise that using skins that are not on the ViX feeds could cause issues, so back up your image before experimenting. At the end of the day it is all about what is important for you, and if an image doesn't let you configure things how you want, then try another one.

I had one of these receivers and the super settings function isn't the best - but could it possibly be something you have set, or not set in your oscam configs? try keepalive = 1 in the oscam.user entry to see if it helps. Apart from that make sure you have the latest firmware installed.

change the user on the second user account (in oscam.user) to 'linuxsat2' = and amend the second nline accordingly in CCcam.cfg - else you will have two user accounts with the same name.

had no issues getting the connection working in the end - as such so it reported the connection being successful - never used the shares.txt option when I had this receiver - I added them manually - so long as you are following the guide and entering the information... i can't remember for sure but i know i had issues with this at first and had to do something odd to get it working - can't remember for sure and I might bee wrong (been months since i sold mine) but you might need to add full http path when entering server address - but got it to work in the end so it all is worth a try - make sure you have the latest patch as some including myself have found the super settings function on this box to be a bit iffy.

this is the best place to get all that on a lot of providers - the link below is for sly uk

http://kos.hdsat.pl/menu-20.html

mrgmx beats me to it again lol - his link leads to the same place as mine eventually! - anyway i should be out enjoying the weather while it lasts!

Well I am a muso as you know - listen to myself a bit lol seriously - my biggest influences are Pink Floyd, Metallica, Led Zeppelin, Used to listen to a lot of G & R when I was younger - REM got played a lot too, Also Nirvana, Stone Roses, some brit pop etc etc. Also listened to electronic well produced stuff, anything produced by William Orbit used to go down well...

Beatles, Dire Straights, Duran Duran, the list goes on.

Nowadays, You will find Audioslave, Foo Fighters and gorillaz (I used to like Blur too!) in my car CD player.

I had a smargo triple card reader working fine on my Vu+ on CCcam - not yet tested the omnikey but sholdn't be a problem - on some images you may need to install usb serial drivers, and in CCcam.cfg, you need to add

SERIAL READER : /dev/ttyUSB0 smartreader+

could be USB1 or USB2 depending on if you have more than one device - and on the triple reader it has all 3

As you can see this thread isn't able to provide a definite answer - I have seen 12-15 as a figure floating about as to how many peers can connect to one sly UK card, but others say many more. There is never usually a problem with straight 1 for 1 sharing - Cline fo Fline - because the burden is shared. If there are many receivers, friends/family etc - clients who are not sharing back, then the load will of course go up on your server and in turn on your virtual cards (the peers with who you are sharing and they are sharing back) - so they might question your high use. I am sure a lot of people have looked in to CSP and other options. Oscam is one where you can easily have more control over things but takes a lot of setting up. It might make your server run better, and your friends and family might be more happier, but you might find that your peers - the ones who are returning the favour get a bit peeved off with constant use.

if you have updated an image before - which i am sure you have - then why not do the same as you did before - if it doesn't work, then you will know that there might be a new bootloader needed, then at that point you can do a search, and if a new bootloader is needed, then you will probably find out.

I am not being funny, but rather than asking questions, why not find the answers?

bootloaders are not updated anywhere near as often as images so as a rule if a new bootloader is needed, then you would hear about it. Why do you ask? Is it not working for you?

problem is - all the twoing and frowing, and we don't even understand the nature of your issue as your explanation isn't very clear. If you are trying to share your card, and you are not managing to do this, then you have to go back to basics. So long as the router has a port (which is the same as the CCcam server listen port) forwarded to the server IP - and that IP is static, the Dydns is set to the dynamic IP that your ISP assigns, the server has an fline, and the client has a cline that corresponds to the dyndns address, port, and name and password set on the fline in the CCcam.cfg on the server - then there really shouldn't be a problem. If you don't understand what I am talking about then you need to read up a bit more.

tspanel 6.3

unrar the file, put the ipk file in /tmp and install manually

restart your receiver, and then you will find all the softcams you need!

Quote from craiglivo

Hi guys thanks for your help!

But i have done everything you said but the channels will not open?

I will keep trying!

please clarify where the cline you are trying to put in comes from?

:taxman:

Quote from Eyeball1

no still no difference i have a pay line which i pay for which i only have to enter into cccam.cfg and works fine im sure is server end

I take it you have read the rules and anything to do with helping you get anything working with a paid line is a no go - still not sure what you are trying to do = are you trying to manage your server configs and monitor your server from outside your network, or are you trying to set up an external share?

It is so easy, but I understand if you are not used to it the concept can be daunting. Your receiver has some good things going for it. It connects to your network, it has an IP address, and you can connect to it with your PC. If you know the IP address, the username and password (ip address can be fixed in your network settings, and to start with, your username is root and there is no password) - then any ftp client (i use winSCP or filezilla) can log on to the receiver. Then your CCcam.cfg file can be found in /etc (usually - dependent on image) - and you add the lines here.

The idea of it all is to get your own card and to share it with others - so it becomes impractical to use the remote control to keep things working, as you would be working with flines and clines - to get the benefits you should be server and client - if you are a client only you are probably paying for your lines or getting a 'friends and family' share - better to put in what you are getting out - and read a bit more!

Quote from birdman99

tryed without port internally didnt clear???

strange that - i have one port forwarded to my server for external share - and a different port for internal share and I have never needed to forward a port on my router for the internal share.

this is your second post on the forum asking for help - we like to help others so long as they have introduced themselves to us first - so if you would like to do that first, I am sure some of us already have answers to your question!
introductions

And I just checked, and I already requested the same in your first post.

If the share is internal only then you don't need to open a port on your router - it should still work - to extend on what sync said, using the dyndns address for an internal share is not just unnecessary, in my experience it just doesn't work.

Ok seems best advice is to update in the original receiver in this thread - found another thread on here that relates to this - unless this has changed
http://linuxsat-support.com/os…cccam-oscam-s*y-09cd.html

shatanar suggests that it can be updated in Oscam - following would be in the oscam.server entry for your sly ita card

Quote

blockemm-u = 1
blockemm-s = 1
blockemm-g = 1
blockemm-unknown = 1

Will block all EMM's.

Using:
blockemm-u = 0
will allow uniq EMM's

uniq is required for updating card entitlements

I find the best way is to leave all to 1 and use the above whenever an update is required, once updated block them all agan.

Display More

this is suggesting that it is ok to periodically change blockemm-u = 1 to blockemm-u = 0 to allow uniq EMMs when the card requires updating.

also on the same thread it is suggesting that leave all blockemm flags to 1 and use scam to update the card, with another always leaving the blockemm-u to = 0 with the others set to 1.

Not sure if anyone wants to risk it though - and if someone does, remember that we are not responsible if you kill your card!