have you lowered your firewall ? some routers will require it
or maybe switch it off while you test and reboot
Posts by sync
-
-
you have bridged a 2nd router from the 1st one so your duo is a client to the 2nd router,
it's not directly connected to the main router so if you open for example port 12000 on 1st router you cant forward to to the duo because it's not going to see it as a clientI can't see this working unles you find a way to tunnel through the 2nd router, or possibly setup some sort of vpn
-
-
If your internet has problems then you wont be able to supply the vps with your card
In my opinion a vps is only for payservers and I would not share with anyone using oneFix your broadband issues first because thats your problem
-
you don't need a phone line to get a sly subscription, you only need it if you want multiroom (2 or more *** boxes)
also you can activate any card on any phone line using a legit sly box,
if you had a box lying around you could phone them and ask them to just send out the card as you have your own equipment, and you would have the card in about 3 days
bring box and card to a friends house and activate it in about 2 minutes -
-
-
-
-
Why is there a need to constantly upgrade ? Some of the older images are the best
I find an image I like and that is stable, set it up the way I want and then leave it alone
Everyone trying to upgrade to the newest image when the hardware in their box says the same, if it's working then just let it work ;-) -
Code
Display MoreEmmAnalyzerPlugin Records emm's received from client sessions, and stores them in memory for inspection. NOTE: For this to be useful, observe the following: - The client(s) that is to be monitored must be set to forward all emms, and not perform any local caching. - The client(s) should probably stay tuned to the same mux/transponder/sid for the duration of the recording. - Emm's in memory are kept indefinately, until the plugin is restarted or disabled (could grow large). - Limit the recording to a particular user and profile, if there is a lot of traffic.============================================================
Code
Display MoreCacheCoveragePlugin This plugin attempts to aid in achieving 100% cache coverage for selected profiles. It monitors the cache contents and analyzes cw continuity for each service (this can't currently be used with systems that always zero out one cw). Cache contributions from both local client sessions and remote ClusteredCache nodes are tracked per service. It can detect (by looking at the cw overlaps) when there a multiple ecm sources for the same service. This typically occurs when the same exact service is available on different transponders, or different terrestrial transmitters separated geographically. Average variance from the expected cw interval is measured (typically amounts to the average ecm processing time), and continuity errors (gaps) are counted. Data is collected for all encountered cache contexts (networkid-caid combinations) even if there is no corresponding local profile, allowing any ClusteredCache setup to be analyzed. Backlogs of all cw's are kept up to 1 minute and can be viewed manually for each service entry. Additionally, the time offset for each cw is measured (counted from the first encountered cw in the validity period), allowing the cw change distribution over time within one period to be estimated. I.e showing which services have cw switchovers at the same time.When you are using CSP you will have to decide what is best for your setup, this includes plugins, some use none at all some use them all when there is no need
I know what works for my setup and have it running very well, depending on the connectors, caid, remote cache and clients each setup has the settings can be very different on each one.
It may seem harsh to say this but try them and see if they work for you or if you really need them, it's the only way to do it as no 2 csp servers will ever be the same.
One bit of advice I'll give to anyone is do not use a friends config, create your own and go from there. -
Cardsharing is actually Legal in some countries believe it or not, most of the big payservers have their servers located in arab countries to avoid being caught and/or shut down.
Also a quick google search will throw you up hundreds of pages of tutorials on cardsharing, emulators and proxy servers etc.
Nothing like a few hours of reading google searches ;)here is a start Card sharing - Wikipedia, the free encyclopedia
-
Here is the complete plugins folder, don't forget to restart CSP after adding them
-
Im running latest r224, it's definitely the best imo
and here is couple of suggestions ;)Code<plugin class="com.bowman.cardserv.EmmAnalyzerPlugin" enabled="true" jar-file="emmanalyzerplugin.jar"/> <plugin class="com.bowman.cardserv.CacheCoveragePlugin" enabled="true" jar-file="cachecoverageplugin.jar">These may not work in an older version, best to upgrade me thinks :)
-
They can be added or deleted from the oscam webif, a quick google search will find the latest ones
also have a look here -
tbh I much prefer CSP as a proxy, been using it for ages and I do like to test everything until I can find fault with it lol
I found oscam as a proxy was unreliable but CSP just kept on going, ecm's for my white cards rarely above .150 even from a cache hit
I recently upgraded to the latest r224 on ubuntu 64 bit and found the cache to work even better than the 2 year old version I had been using :) -
You will obviously need 2 oscam's running, I tested it from a dm500 as reader to oscam on pc and clients connecting to pc
It worked fine but after a while I switched back to csp :)Code
Display Moreoscam1 [reader] label = cacheex push description = cacheex protocol = camd35 device = 192.168.1.10,12345 user = cache1 password = card1 services = !adult entertainment inactivitytimeout = 0 cacheex = 3 group = 1 blockemm-unknown = 1 blockemm-g = 1Code
Display Moreoscam2 [account] user = cache1 pwd = card1 description = cacheex from card1 group = 1 uniq = 3 cacheex = 3 allowedprotocols = camd35 keepalive =1
then just reverse them and change the port to push the cache from oscam 2 to oscam 1
also you must forward the ports using cachex on UDP on your router not TCPadd to oscam.conf for oscam1
also add it to oscam.conf for oscam2 with the port you use
restart oscam after any changes, need any help give me a shout ;)
-
Sorted, bin file attached has pcsc support on 64 bit ubuntu and debian :)
save the attached file to your pc then unrar it
stop oscam on your server
ftp to your oscam's location on your server and delete old oscam or rename it to oscam.old
ftp new oscam to server
chmod 755
restart oscamor something like that ;)
-
oscam with omnikey on UBUNTU 64 BIT
hi everyone, ive been messing with a new server but can not get oscam to see my omnikey, any help/suggestions appreciated
Ubuntu 11.04 64 bit with OSCAM 1.10rc-svn build #6089
Code
Display Moreroot@ubuntu:~# pcsc_scan PC/SC device scanner V 1.4.17 (c) 2001-2009, Ludovic Rousseau <ludovic.rousseau@free.fr> Compiled with PC/SC lite version: 1.5.5 Scanning present readers... 0: OmniKey CardMan 3121 00 00 Sun Apr 22 23:32:35 2012 Reader 0: OmniKey CardMan 3121 00 00 Card state: Card removed,looks ok from output above but oscam is not seeing it, currently running a version thats supposed to work on 64 bit and has pcsc support and ive tried about 5 different bins today without any success
Code2012/04/22 23:26:24 75FF8700 r Cannot open device: 0 2012/04/22 23:27:24 75FF8700 r ERROR opening device 0 2012/04/22 23:27:24 75FF8700 r Cannot open device: 0If anyone has oscam currently working on 64 bit ubuntu 11.04 with omnikey, could you share the bin so I can rule out an oscam problem
Many Thanks -
0 means it's a local card, 7 means you can share down 7 more hops
1 & 1 means you friends card is local and you have 1 re-shareI suspect your friend is faking his local card, try his line directly in a box, if it dont clear ask him why
fakers will give you plenty excuses why and tell you its your fault all the while using your card
give him 0 0 0 { 0: 0: 0 } untill his card starts to clear channels, but watch this 'friend' closely ;)
