OSCam/en/Which protocols Card Reader and Cards are supported: Unterschied zwischen den Versionen
Wiwe (Diskussion | Beiträge) |
Wiwe (Diskussion | Beiträge) |
||
Zeile 7: | Zeile 7: | ||
* UDP = no firm connection between client and server sockets. No checking wheter all data packets have arrived. | * UDP = no firm connection between client and server sockets. No checking wheter all data packets have arrived. | ||
* TCP = firm connection between client and server sockets. Checking wheter all data packets have arrived. More overhead and therefore a little slower than UDP. However, this is irrelevant for the small amounts of data for CS. Great advantage: stable compounds in low Internet lines. | * TCP = firm connection between client and server sockets. Checking wheter all data packets have arrived. More overhead and therefore a little slower than UDP. However, this is irrelevant for the small amounts of data for CS. Great advantage: stable compounds in low Internet lines. | ||
=== From OScam supported protocolls === | |||
* newcamd with cascading/remote server ECM support | |||
* camd 3.3x TCP | |||
* camd 3.5x / 3.57x UDP with cascading/remote server ECM support, ECM and EMM support with size > 256 bytes | |||
* camd 3.78x TCP with cascading/remote server ECM support, ECM and EMM support with size > 256 bytes | |||
* CCcam with cascading/remote server ECM support, ECM and EMM support with size > 256 bytes | |||
* DVB API with multi tuner and PIP support | |||
* gbox with cascading/remote server ECM support | |||
* serial (HSIC, SSSP, BOMBA, DSR 9500) | |||
* radegast | |||
=== Options === | |||
* -a write oscam.crash on segfault (needs installed GDB and OSCam compiled with debug infos -ggdb) | |||
* -b starts in background, writing oscam.version with starttime and version info in temporary directory | |||
* -c <directory> read configuration from <directory>, default:see CS_CONFDIR in globals.h, while starting OSCam prints warnings on invalid keywords, comment lines start with # character. | |||
* -d <level> debug level mask: | |||
0 = no debugging (default) | |||
2 = ATR parsing info, ECM dumps, CW dumps | |||
4 = traffic from/to the reader | |||
8 = traffic from/to the clients | |||
16 = traffic to the reader-device on IFD layer | |||
32 = traffic to the reader-device on I/O layer | |||
64 = EMM logging | |||
128 = DVBAPI logging | |||
256 = load balancing logging | |||
512 = cache exchange logging | |||
1024 = client ECM logging | |||
65535 = debug all | |||
* -g <mode> garbage collector debug mode, default:none: | |||
1 = immediate free | |||
2 = check for double frees | |||
* -h usage | |||
* -p <number> maximum number of pending ECM packets, default:32, maximum:255 | |||
* -r <level> restart level: | |||
0 = disabled, restart request sets exit status to 99 | |||
1 = restart activated, web interface can restart oscam (default) | |||
2 = like 1, but also restart on segmentation faults | |||
* -S do not filter sensitive info (card serial numbers) in the logs | |||
* -s capture segmentation faults | |||
* -t <directory> use <directory> for temporary data, default:temporary directory of OS | |||
* -u enable output of web interface in UTF-8 charset | |||
* -V show OSCam version info | |||
* -w <seconds> time waiting for system time to be set correctly | |||
=== Which Card Reader are supported? === | === Which Card Reader are supported? === |
Version vom 18. November 2012, 11:05 Uhr
OSCam Übersicht OSCam Home OSCam Accueil OSCam Home
Which protocols, Card Reader and Cards are supported?
Which protocols are supported?
- UDP = no firm connection between client and server sockets. No checking wheter all data packets have arrived.
- TCP = firm connection between client and server sockets. Checking wheter all data packets have arrived. More overhead and therefore a little slower than UDP. However, this is irrelevant for the small amounts of data for CS. Great advantage: stable compounds in low Internet lines.
From OScam supported protocolls
- newcamd with cascading/remote server ECM support
- camd 3.3x TCP
- camd 3.5x / 3.57x UDP with cascading/remote server ECM support, ECM and EMM support with size > 256 bytes
- camd 3.78x TCP with cascading/remote server ECM support, ECM and EMM support with size > 256 bytes
- CCcam with cascading/remote server ECM support, ECM and EMM support with size > 256 bytes
- DVB API with multi tuner and PIP support
- gbox with cascading/remote server ECM support
- serial (HSIC, SSSP, BOMBA, DSR 9500)
- radegast
Options
- -a write oscam.crash on segfault (needs installed GDB and OSCam compiled with debug infos -ggdb)
- -b starts in background, writing oscam.version with starttime and version info in temporary directory
- -c <directory> read configuration from <directory>, default:see CS_CONFDIR in globals.h, while starting OSCam prints warnings on invalid keywords, comment lines start with # character.
- -d <level> debug level mask:
0 = no debugging (default)
2 = ATR parsing info, ECM dumps, CW dumps 4 = traffic from/to the reader 8 = traffic from/to the clients 16 = traffic to the reader-device on IFD layer 32 = traffic to the reader-device on I/O layer 64 = EMM logging 128 = DVBAPI logging 256 = load balancing logging 512 = cache exchange logging 1024 = client ECM logging 65535 = debug all
- -g <mode> garbage collector debug mode, default:none:
1 = immediate free
2 = check for double frees
- -h usage
- -p <number> maximum number of pending ECM packets, default:32, maximum:255
- -r <level> restart level:
0 = disabled, restart request sets exit status to 99
1 = restart activated, web interface can restart oscam (default) 2 = like 1, but also restart on segmentation faults
- -S do not filter sensitive info (card serial numbers) in the logs
- -s capture segmentation faults
- -t <directory> use <directory> for temporary data, default:temporary directory of OS
- -u enable output of web interface in UTF-8 charset
- -V show OSCam version info
- -w <seconds> time waiting for system time to be set correctly
Which Card Reader are supported?
An updated list you will find here: DeviceList
Seriell
- reader with Mouse protocol 3,5 or 6 Mhz clockspeed
- intern Reader (z.B. Dreambox)
- reader can also have a seral-USB adapter connection
USB
- reader with FTDI Chipset (z.B. Smargo Smartreader+)
- reader with Prolific Chipset, no overclocking possible!
Which Cards are supported?
A updated list you find here: CardsList
Diese Seite in anderen Sprachen - This page in other languages - Cette page dans d'autres langues - Queste pagine in altre Lingue
[[OSCam/de/{{#titleparts:OSCam/en/Which_protocols_Card_Reader_and_Cards_are_supported|3|3}}|Deutsch]] [[OSCam/en/{{#titleparts:OSCam/en/Which_protocols_Card_Reader_and_Cards_are_supported|3|3}}|English]] [[OSCam/fr/{{#titleparts:OSCam/en/Which_protocols_Card_Reader_and_Cards_are_supported|3|3}}|Français]] [[OSCam/it/{{#titleparts:OSCam/en/Which_protocols_Card_Reader_and_Cards_are_supported|3|3}}|Italiano]]