maybe you should look at doing a bit of reading first as all the info is available in the forum.
cardsharing-tutorials
cccam-support-tutorials
are good places to start - there is also a search box at the top right.
maybe you should look at doing a bit of reading first as all the info is available in the forum.
cardsharing-tutorials
cccam-support-tutorials
are good places to start - there is also a search box at the top right.
You can get whatever packages your friends and your friend's friends have. If you buy yourself a card, then your friends can have that package. Payservers have nothing to do with cardsharing. You don't share anything with them, you just pay them, and then once they have your money, and your details, they might disappear leaving you worried...
very simple - really just try plugging it in and see what happens! - if it is not recognised then plug it in your pc and do a quick format, then try again. If you are using it for PVR functioin then navigate receiver settings to the exteranal drive then format it.
Thank you for your answer, but why is creating 2 log's?
It appears to me that once the OSCam.log file gets to its max sixe that you set in the config, then it backs up this file as oscam.log-prev, so if you reduced your log size then once you reach this smaller limit the oscam.log-prev will be a smaller file. If you want to delete it then it won't cause any harm, it is just a log file.
Basically if you are not sharing the load with others, then everything goes on to your server so it can get overloaded so as caz said the best way is to cardshare, so if everyone in your 'family' get their own boxes with their own card and set up their own server, then you won't have to suffer the burden of everyone's viewing. If you are a sly subscriber there is always multiroom which could potentially get you another card for a bit extra money.
CCCam and OSCam will do the same thing as a CAM but in software, so pretty much anything in the Vu cardreader will work.
can you connect your box at all? if you can telnet or ftp to it then the problem could be the server or the port. check your CCcam.cfg file to make sure the port is set to 16001 (WEBINFO LISTEN PORT : 16001)
Sometimes there can be simple things wrong such as a bad RJ-45 cable or connections. You said you checked your router and it hasn't connected - I take it DHCP is enabled in your router? Not familiar with your box but if there is an option to enable static IP rather than use DHCP then it is worth doing this and maybe try setting the receiver's mac address in your router to make it a permanent fixed IP.
Any computer which could run a windows operating system will suit your purpose, so long as it is set correctly and it has the correct drivers to get everything working. If it is a old PC or not a very fast one, then it is an idea trim down what you are installing on it, as to just run a server, you don't need whistles and bells.
It might be an idea to look at the system BIOS to ensure everything is how it should be and there is nothing going on which would cause things to behave differently, not sure if there would be any USB or power saving options in the your BIOS but worth a look. Usually if you are having issues, then it would be software driving your hardware rather than hardware itself. If you are getting different results on different computers, then you might want to see if you need additional drivers for your chipset, so might be an idea to browse the manafacturer websites to see if there are any additional drivers. Also maybe a browse of linux forums to see if anyone else has any issues with USB devices on your computers. If any drivers are needed that are not under the GPL (open source) then they would not be installed by default. To be honest though with USB, they are all set to a standard in such a way that they should all work without anything additional, after all, it is a universal standard format designed so that lots of things work, so maybe there could be some other issues causing it rather than the USB itself.
Worth looking at any power saving options you have set up, I have found that any issues with my USB devices is often down to this.
Hard to tell what is going on but I am sure something will be able to fix it!
I have read on other forums that they have closed down, blaming the internet and cardsharing (whether this meant ps or proper cardsharing, who knows). I wonder how many people bought this card, not because they wanted to view the content, but because they wanted a cheap local card to share to so they could watch something more decent. Maybe considering this, cardsharing may have been helping them. It definitely was one of the most common cards on people's servers. Would they have bought this card if they were not sharing?
When you have all the packages you need then there is no need to add any more peers. If your server is not on the same machine as your receiver, then your receiver will be one hop away, so you will need peers who are offering you reshares if you want to view them packages. There is always the option of putting one or two of your shares on the receiver rather than the server if you want to maximise your own viewing potential. If you are exchanging shares with people you hardly know, then take care as there are a lot of fakers out there. 10 peers might even be enough, so it depends on how you work things. I treat my server like I would treat my tropical fish. I check it about 3 times a day, get rid of dead ones and replace them, and about once every 3 days, I will just watch the server for about an hour to see how everything is getting on!
Ubuntu is best for those not too familiar with linux. It is easy to set up, and fast to install. I use Ubuntu 10.10 (Maverick Meerkat), and there is an easy install script to get your server up and running. I have used various flavours of linux over the years, and Ubuntu is definitely the most user friendly, especially if you have had little linux experience. As Glenviewjf said, once you have it set up, it is really easy to maintain, infact I have mine on a Netbook with the lid closed, and access it from a windows PC.
I have noticed high usage from the 2 peers who have 2.3.0 installed also recorded a log and noticed some strange login attempts. I am not usually a paranoid person. I think the illegal login requests could be from old peers, but I have not been able to confirm that because I don't keep records of everything! Think I will send a warning to the peers who have 2.3.0 - glad I have to use 2.1.3, never had a reason to try this version!
You would be getting that message often I would imagine if your dns is out there. Best start again regardless. As everyone has said, use trusted peers. Get one of your peers to check your ports to see if you have any ports open that shouldn't be, and make sure you only have open what is necessary!
Try adding this for each of your account entries in oscam.user
Quotekeepalive = 1
The image installed on these boxes if they originated from forum sponsor (sat-shop) would be the SatStation image. There is an addons server which will be preinstalled that will include OSCam r6096, which I am running and it is fine. If the box is new or fairly new it should already be updated with the latest bootloader. The latest SatStation image is in the Duolabs downloads section on this forum, and the guide to flash latest image is in the Duolabs Qbox support section. Any help needed just ask and will help you get up and running.
Choice of images is up to you, but remember most of the images are backups of other people's setup. If you decide to use the backups, you will have to change things to suit yourself, like language and tuner configs. All backups and the SatStation image will have addon servers with OSCam, but if it only includes the Stock 0.0.59 or 0.0.60 image, you will need to add the addon servers or reflash with an image that has them on already.
When you are getting this set up there is often something simple that is missed out that is causing the issue, often it is to do with simple things such as the listening port in the cccam.cfg not matching with the open port (i missed this at first), ip addresses, or other communication issues. It is hard to say without knowing what your configs look like, also bear in mind that changes require reboots a lot of the time. Have a look over it again and you might see something obvious that you missed before, but if you are not sure and have no joy you might be better off posting your configs (cccam.cfg and oscam.conf) blanking the sensitive bits!
Yes a different reader entry in oscam.server for each reader/proxy reader
QuoteDisplay More[reader]
label = proxy1
protocol = cccam
device = proxy1.dyndns.address,12000
user = proxy1
password = proxy1pass
group = 1
cccversion = 2.2.1
cccmaxhops = 2
ccckeepalive = 1
cccreshare = 1
[reader]
label = proxy2
protocol = cccam
device = proxy2.dyndns.address,12000
user = proxy2
password = proxy2pass
group = 1
cccversion = 2.2.1
cccmaxhops = 2
ccckeepalive = 1
cccreshare = 1
is it possible to have 2 compleatley different servers in the reader of oscam server file ? if so any examples out there ? how does it select one over the other ?
When you enter the server details in OSCam, it will know to some extent what services are available. It will not send requests if it knows that service is not available. If you have the same service on both readers/proxy readers, it sends the request to both readers, and the quickest response will be the one serving the request. so long as you know how to enter one reader entry, then the only difference for the second one is you have to give it a different name providing they are both using the same protocol. Once you understand this, then you can look at defining services and caids for each reader if you want, and other options such as loadbalancing. I am not sure an example is needed if you are aware how to add a reader entry, but if you still don't understand, please let us know what you don't understand. The information is out there in the OSCam wiki, and on this forum, and this is quite basic stuff, so maybe a little reading will help.
Had a similar setup on my Qbox. Found it is best to put the fixed dish on tuner A, so if you have a timer record, it will use the fixed, leaving you to watch whatever you want on the motorised.