Basic setup info for RQCS private cardsharing

[pecker88]

Didn't see this posted here, so here we go:

A RQCS cardshare package has been uploaded here: http://bellexpress.vu/forum/local_links.php?catid=64#linkid7410

This software allows you to share a subbed rom24x OR rom102/3 between up to 64 client receivers. Best part about this is that it is TOTALLY private. You dont' have to connect to a supposidly "off shore" server, ect... It is a private group of people, sharing a subbed card.

I have this setup and running great on a 508 and vip722 ird. Obivously, you will ONLY get ch's that are subscribed. However, this WILL WORK after the card swap is finished.

good luck

PS. if you get this up and working, wouldnt' hurt to send Ranton a small donation for his time/effort.

[pecker88]

Well, here's a little more info:

Obivously, you will ONLY get the ch's your subscribed to, nothing else. RQCS is a bit easier to setup, (compared to NKshare) as you dont' have to *manually* populate keyset info. You simply have to have a .bin that is married to the client receiver.

The server portions of both Nkshare and RQCS are similar. You have to have either A) tsop dump from subbed241 receiver or B) dump from rom10x cam that was replaced by the 24x cam you got in the mail.

If you have st19 or cemu running, setup will be VERY SIMPLE as you already have the hardware setup and all of the necessary keyset info. You HAVE to re-flash the atmel chip on the max/mel with a modified N3 flash where the 9th byte of the ATR is set to 64.

For VIP receivers, a max/mel WILL NOT work. You HAVE TO either use a mod-serial card OR AVR with 8515 chip. Again, a max/mel WILL NOT work on VIP receivers, regardless of what flash you use for the atmel.

As far as NKshare, here is a bit of info found at another site:

client.ini:

;===============================
; ATR FOR ISO7816 INTERFACE
;===============================
ATR:3FFF9500FF918171644700444E41535032343120447368 4830329D
;=========================
; CLIENT PRIVATE DATA
;=========================
BOXKEY: taken from currently working st19.cor file using GenDT08_sk
CAMNUMBER:taken from currently working st19.cor file using GenDT08_sk
IRDNUMBER:taken from currently working st19.cor file using GenDT08_sk
TIMEZONE:taken from currently working st19.cor file using GenDT08_sk
ZIPCODE:taken from getdata of subed 241
PROVIDER_A:00 01(taken from getdata of subed 241)
PROVIDER_B:01 01(taken from getdata of subed 241)
PROVIDER_C:01 02(taken from getdata of subed 241)
BLACKOUT:(taken from getdata of subed 241)
; Tiers(taken from getdata of subed 241)
; -----------------------------------------------------------

;========================
; Private Session Keyset
;========================
; Private DT 08 - 73 bytes
;PVTDT08:00000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000
; Private Session N - 64 bytes
PVT_N: taken from currently working st19.cor file using GenDT08_sk
; Private Session D - 64 bytes
PVT_D:taken from currently working st19.cor file using GenDT08_sk
;========================
; RSA Keyset
;========================
; IRD N1 - 64 bytes (DN values - the same for ALL DN ird's if NO RSA mod has been done)
;------------------
IRD_N1:A4 E9 B5 85 93 2F 90 28 2F D7 0C 90 81 76 E8 60 5E 6B 2C E6 29 33 5A 0F C1 5B 31 DA B0 BF C6 FE EB 88 CF C6 96 49 99 4C D3 FE 03 9C 99 65 C6 20 C4 D5 82 8E 91 53 99 8E E4 AE 0E 8C 25 64 4D F3

; IRD N2 - 64 bytes
;------------------
IRD_N2:23 72 80 AA B3 6B E4 B2 1F C7 1F BF 08 21 8E 53 2A 54 5E 74 4D 7B 00 7F F8 69 BA 42 68 31 C4 AC 65 3F 38 25 AD E9 35 8F CD 1F 02 39 EC 44 7C BC 27 65 CC 0A EB E4 37 AF 22 70 FC 46 1C 2F A0 42

server.ini

;========================
; Private CAM / IRD Data
;========================
BOXKEY:(taken from dump of subbed 102 OR TSOP)
CAMNUMBER:(taken from getdata of subed 241)
IRDNUMBER:(taken from getdata of subed 241 OR TSOP)
;================================================
; Secondary Key - 96 bytes
;================================================
;
; Note:
; -----
; Leave this commented out if using
; the DT08 method
;================================================
;PVTSK:0000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 00000000000000000000000000000000000000000000000000 0000000000000000000000000000000000000000000000000
;========================
; RSA Keyset
;========================
; IRD N1 - 64 bytes (DN values - the same for ALL DN ird's if NO RSA mod has been done)
;------------------
IRD_N1:A4 E9 B5 85 93 2F 90 28 2F D7 0C 90 81 76 E8 60 5E 6B 2C E6 29 33 5A 0F C1 5B 31 DA B0 BF C6 FE EB 88 CF C6 96 49 99 4C D3 FE 03 9C 99 65 C6 20 C4 D5 82 8E 91 53 99 8E E4 AE 0E 8C 25 64 4D F3

; IRD N2 - 64 bytes
;------------------
IRD_N2:23 72 80 AA B3 6B E4 B2 1F C7 1F BF 08 21 8E 53 2A 54 5E 74 4D 7B 00 7F F8 69 BA 42 68 31 C4 AC 65 3F 38 25 AD E9 35 8F CD 1F 02 39 EC 44 7C BC 27 65 CC 0A EB E4 37 AF 22 70 FC 46 1C 2F A0 42

[pecker88]

OK, So if I have a subbed card with private info that has a 241 card I would read TSOP to get required info. I wouldn't need any card info except what is on system info screen. That would set up the server and the receivers I have with public info would work for the client side right? They wouldn't need to be jtagged? I just have never set up a home network and would like to share the info in my house using either wireless or the power line plugin internet sharing system.

for clarification: some entries in the above .ini examples say "from getdata of subbed 241". Here is how to create this "getdata" fiile. Open the server.ini file and add this line to the top:
GETDATA=1

Then fill in the COM info to specify which com port your ISO is hooked to. Then put 241 in ISO and launch NKserver. A data file, (referred to as "getdata" above) will then be created. This file can be opened in .txt pad and necessary info can be c/p into .ini files.

for server:
Read the tsop of subbed receiver and open in GenDT08_SK; this will get you the BK and/or PVTSK, (Private SessionKeys, if SK receiver).

for client:
Yes, the same 'ol DN public numbers will work, no problem.

[JT]

Here is a collection of N3 flash files for all three versions of the atmel chip you may be using (atmel 8515, atmel 2313, and atmel attiny 2313) and for both providers. Rev240 flashes are for Bev and Rev241 flashes are for Charlie. Also includes some flashing software.

http://bellexpress.vu/forum/local_links.php?catid=64

[JT]

At the time of this post, the current version of RQCS is 1.06. Can be found here:

http://bellexpress.vu/forum/local_links.php?catid=64

[sirdrinks]

Just got mine up and running today (client), I can't believe how easy it is to setup, easier than cemu/st19...maybe I should shut up now... ;)

[JT]

Basic how-to set up RQCS found here.

http://bellexpress.vu/forum/local_links.php?catid=64

[0utcast]

just a little information on rqcs for those that want to try it. look for some tutorials posted by fta_dude for the rqcs and rqclient. would have posted them but .pdf not allowed for file attachments.

basic things you will need

-needs rqcs binaries
-iso reader (not and unlocker)(not needed if you decide to use dreambox, beware you need to know linux to even consider the dreambox route and its far easier to run from your desktop pc with an iso reader or 2 anyhow)
-need subbed cam to share (can test with 102 for now but not much left)
-need jtag and a jtaggable receiver you can get the boxkeys and secondary key off from or already have them off from (if you have the .bn102 image saved somewhere open in gendt08 and there ya go)
-soldering iron and ability to solder
-ability to read and apply information from guides above and rqcs.conf commentations
-maxmels for every dish receiver you intend to be a client and the rqclient software running on each client pc the maxmel is connected to

as you can see there is alot to this testing method but it does work well and require some skillz beyond the free tver. i does seem a little much at first but once you get it running its simple.

the good thing is milli has most all this stuff here to help you get going. btw i do have a slinger and about 3 of every testing method so im not pushing nothing on no one. just trying to help out for those that want to test rqcs.

[OU812]

I can say it was a little confusing at first, but I am now sharing my sub with some close friends (for free) unlike some people,and it runs almost flawless and freeze free. But no need for constant software changes and those old dn and bev ird's still all work for the most part.

[The Sentinel]

Thank you pecker88, a great thread!

[CyClore]

just a little information on rqcs for those that want to try it. look for some tutorials posted by fta_dude for the rqcs and rqclient. would have posted them but .pdf not allowed for file attachments.

basic things you will need

-needs rqcs binaries
-iso reader (not and unlocker)(not needed if you decide to use dreambox, beware you need to know linux to even consider the dreambox route and its far easier to run from your desktop pc with an iso reader or 2 anyhow)
-need subbed cam to share (can test with 102 for now but not much left)
-need jtag and a jtaggable receiver you can get the boxkeys and secondary key off from or already have them off from (if you have the .bn102 image saved somewhere open in gendt08 and there ya go)
-soldering iron and ability to solder
-ability to read and apply information from guides above and rqcs.conf commentations
-maxmels for every dish receiver you intend to be a client and the rqclient software running on each client pc the maxmel is connected to

as you can see there is alot to this testing method but it does work well and require some skillz beyond the free tver. i does seem a little much at first but once you get it running its simple.

the good thing is milli has most all this stuff here to help you get going. btw i do have a slinger and about 3 of every testing method so im not pushing nothing on no one. just trying to help out for those that want to test rqcs.

How did your server work with all of the issues from the uplink problem yesterday? Is RQ 1.06 still working for you? I am thinking of getting it loaded up in the next few days...

[gizmolite]

its up and running

[CyClore]

ok, thanks. I didn't want to go through the setup of getting a private one running just to find out something changed. Thanks for the fast response...