this build on java.....basically this will be a brige beetwen your newcamd or radegast servers......
so i explain what for this use full tool....
in this you can enter many servers or your cards in the config....
e.g: you will have one card and you can add as many clients like 2000 or 3000 users in one card
so you will have one user for the card in newcamd server and this tool will cash the and give all other users which are in the user.xml in proxy server .....that means your card will be hit only single user and keep in cache for all other users so your card will be relax all the time ...also build in web interface you can map the channels who what it on will show with a channel name ......i cant list everythink here all the options this tool provide ......
to first time to setup it's a bit complicated but ones you done you will know what i'm trying to tell ....
good luck..
Part Of Readme....
First, in order to avoid the usual confusion about the proxy:
- This is not a cam emulator or card server, it knows next to nothing about ca systems, DVB concepts, iso7816 or the md api.
- It's 100% memory-hogging-java, intended to run on stable servers, not on stb's or desktop pcs (although of course this
may still be possible).
- It's not for everyone, it could be considered an SDK for building custom sharing solutions or integrating sharing into
existing communities. If you don't have any experience writing code, the proxy probably isn't for you.
- Yes it's controversial. Used properly a cluster of 2 proxies could handle several thousand clients with a handful of cards,
bandwidth being the only real limit. NOTE: This assumes complete understanding of all aspects of the newcamd protocol.
Cardservproxy is a scalable proxy primarily for the newcamd protocol, with load balancing and cluster handling built in.
It will keep track of 2 or more cardservers (typically newcs) and accept incoming connections from clients (any client
that support the newcamd or radegast protocols). It removes the need for complex clients or servers, by centralizing all
of the complexity.
Features/benefits:
- The proxy hides the servers from the clients. New servers can be added/removed on the fly without affecting traffic
or having to change the clients configurations.
- The proxy hides the clients from the servers, the servers will only ever have a single very busy user (the proxy)
from a fixed ip.
- User management is centralized in the proxy, the servers will not have to be updated to add new users. The proxy user
manager is pluggable and can be connected to any external user database with a minimum of coding.
- Connected servers don't have to have identical card subscriptions, the proxy can keep track of which services will
decode on which card, and route requests accordingly.
- The proxy will use fairly sophisticated load balancing to make sure requests are routed to the least loaded card that
has the service in question. It will monitor the utilization for each card and give a clear indication when there are
bottlenecks or excess capacity.
- Multiple providers with different ca-systems can be hosted by the same proxy, by defining separate profiles. Each
profile is assigned its own listener port(s) and any number of card servers (exactly which ca-systems are used or
whether it is dvb-s/c/t doesn't matter).
- Caching is centralized to the proxy (ideally the caches of the individual cardservers will never score a hit). This
means that as long as someone in the same proxy or proxy cluster is watching a service, an infinite number of others
can watch the same service without causing any extra traffic towards the card servers. Once there are enough cards
connected to always keep all the providers services in cache at any given moment, the number of users becomes limited
only by bandwidth.
- The proxy is prepared for integration into existing communities (irc bots, web forums, torrent trackers) and provides
an example webgui on top of an ajax-friendly generic http/xml query interface.
- Multiple proxies can be clustered together by real time cache-sharing. If user a is watching a service on proxy1,
then user b can watch the same service on proxy2 without causing any requests towards a card server.
- The proxy can be used as a protocol analyzer or general troubleshooting tool, since it decrypts/encrypts newcamd
and allows user created plugins to be added.
- Nearly all changes to configuration can be performed without restarts, the proxy monitors the config file proxy.xml
and most other resources.
- As of 0.8.10, new user created connector implementations (protocols) can be added in the same manner as plugins.
- Full java source is available.
The creator accepts no responsibility or liability for any breach of provider contracts or local laws resulting from the use of this code.
The proxy prefers a sun JRE (1.4.2 or later) but others like JamVM _may_ work. If you're interested in getting the
proxy to run properly under gcj/gij or any other non-sun jre, contact me on efnet (be prepared to make source changes).
To get started read the example configs and the proxy-reference.html, + the changelog and cardproxy.sh start script.
INSTALL NOTES:
- Mainly tested on sun jre 1.4.2 and 1.5 (but the latest java6 release should of course also work fine).
No installation is necessary, get the self extracting dist and unpack wherever.
Both are available here: http://java.sun.com/javase/downloads/previous.jsp (sun previous releases)
Which one works best will depend on your environment. Later versions will probably work as well.
- The cardproxy.sh start script is just an example, you will likely need to edit it. If you have multiple jre's or jdk's
installed then put the full path to the one you intend to use in the line that starts java. If it fails for no
apparent reason then check the log/cardserv-sysout.log where all stdout and stderr output should end up.
- To start without the script (on any OS): cd <csproxy dir>; java -jar lib/cardservproxy.jar
- If you start the proxy with no proxy.xml configuration file in the config dir, a skeleton config will be generated.
- When running under windows, use the prepared java service wrapper setup (jsw-win32.zip) to install the
proxy as a proper nt service (kept running regardless of user login/logout and started automatically at boot).
Make sure the all the jsw files are in a dir called jsw in the proxy home dir, and set silent="true" for the logging
in proxy.xml or you'll have duplicate logs. Also make sure you can successfully start the proxy from cmdline before
you try it as a service.
NOTE: Do not try to run the jsw wrapper.exe manually, it will only work when started by the installed service entry.
NOTE: It is of course also possible to start the proxy as a normal java app, without the script (see above)
or even with the script, using cygwin bash: http://www.cygwin.com
so i explain what for this use full tool....
in this you can enter many servers or your cards in the config....
e.g: you will have one card and you can add as many clients like 2000 or 3000 users in one card
so you will have one user for the card in newcamd server and this tool will cash the and give all other users which are in the user.xml in proxy server .....that means your card will be hit only single user and keep in cache for all other users so your card will be relax all the time ...also build in web interface you can map the channels who what it on will show with a channel name ......i cant list everythink here all the options this tool provide ......
to first time to setup it's a bit complicated but ones you done you will know what i'm trying to tell ....
good luck..
Part Of Readme....
First, in order to avoid the usual confusion about the proxy:
- This is not a cam emulator or card server, it knows next to nothing about ca systems, DVB concepts, iso7816 or the md api.
- It's 100% memory-hogging-java, intended to run on stable servers, not on stb's or desktop pcs (although of course this
may still be possible).
- It's not for everyone, it could be considered an SDK for building custom sharing solutions or integrating sharing into
existing communities. If you don't have any experience writing code, the proxy probably isn't for you.
- Yes it's controversial. Used properly a cluster of 2 proxies could handle several thousand clients with a handful of cards,
bandwidth being the only real limit. NOTE: This assumes complete understanding of all aspects of the newcamd protocol.
Cardservproxy is a scalable proxy primarily for the newcamd protocol, with load balancing and cluster handling built in.
It will keep track of 2 or more cardservers (typically newcs) and accept incoming connections from clients (any client
that support the newcamd or radegast protocols). It removes the need for complex clients or servers, by centralizing all
of the complexity.
Features/benefits:
- The proxy hides the servers from the clients. New servers can be added/removed on the fly without affecting traffic
or having to change the clients configurations.
- The proxy hides the clients from the servers, the servers will only ever have a single very busy user (the proxy)
from a fixed ip.
- User management is centralized in the proxy, the servers will not have to be updated to add new users. The proxy user
manager is pluggable and can be connected to any external user database with a minimum of coding.
- Connected servers don't have to have identical card subscriptions, the proxy can keep track of which services will
decode on which card, and route requests accordingly.
- The proxy will use fairly sophisticated load balancing to make sure requests are routed to the least loaded card that
has the service in question. It will monitor the utilization for each card and give a clear indication when there are
bottlenecks or excess capacity.
- Multiple providers with different ca-systems can be hosted by the same proxy, by defining separate profiles. Each
profile is assigned its own listener port(s) and any number of card servers (exactly which ca-systems are used or
whether it is dvb-s/c/t doesn't matter).
- Caching is centralized to the proxy (ideally the caches of the individual cardservers will never score a hit). This
means that as long as someone in the same proxy or proxy cluster is watching a service, an infinite number of others
can watch the same service without causing any extra traffic towards the card servers. Once there are enough cards
connected to always keep all the providers services in cache at any given moment, the number of users becomes limited
only by bandwidth.
- The proxy is prepared for integration into existing communities (irc bots, web forums, torrent trackers) and provides
an example webgui on top of an ajax-friendly generic http/xml query interface.
- Multiple proxies can be clustered together by real time cache-sharing. If user a is watching a service on proxy1,
then user b can watch the same service on proxy2 without causing any requests towards a card server.
- The proxy can be used as a protocol analyzer or general troubleshooting tool, since it decrypts/encrypts newcamd
and allows user created plugins to be added.
- Nearly all changes to configuration can be performed without restarts, the proxy monitors the config file proxy.xml
and most other resources.
- As of 0.8.10, new user created connector implementations (protocols) can be added in the same manner as plugins.
- Full java source is available.
The creator accepts no responsibility or liability for any breach of provider contracts or local laws resulting from the use of this code.
The proxy prefers a sun JRE (1.4.2 or later) but others like JamVM _may_ work. If you're interested in getting the
proxy to run properly under gcj/gij or any other non-sun jre, contact me on efnet (be prepared to make source changes).
To get started read the example configs and the proxy-reference.html, + the changelog and cardproxy.sh start script.
INSTALL NOTES:
- Mainly tested on sun jre 1.4.2 and 1.5 (but the latest java6 release should of course also work fine).
No installation is necessary, get the self extracting dist and unpack wherever.
Both are available here: http://java.sun.com/javase/downloads/previous.jsp (sun previous releases)
Which one works best will depend on your environment. Later versions will probably work as well.
- The cardproxy.sh start script is just an example, you will likely need to edit it. If you have multiple jre's or jdk's
installed then put the full path to the one you intend to use in the line that starts java. If it fails for no
apparent reason then check the log/cardserv-sysout.log where all stdout and stderr output should end up.
- To start without the script (on any OS): cd <csproxy dir>; java -jar lib/cardservproxy.jar
- If you start the proxy with no proxy.xml configuration file in the config dir, a skeleton config will be generated.
- When running under windows, use the prepared java service wrapper setup (jsw-win32.zip) to install the
proxy as a proper nt service (kept running regardless of user login/logout and started automatically at boot).
Make sure the all the jsw files are in a dir called jsw in the proxy home dir, and set silent="true" for the logging
in proxy.xml or you'll have duplicate logs. Also make sure you can successfully start the proxy from cmdline before
you try it as a service.
NOTE: Do not try to run the jsw wrapper.exe manually, it will only work when started by the installed service entry.
NOTE: It is of course also possible to start the proxy as a normal java app, without the script (see above)
or even with the script, using cygwin bash: http://www.cygwin.com