G-Box mit dem WIFI?

[madita_madita]

Hi...

geht mit dem Diablo WIFI auch G-Box?

bin schon am testen aber ohne Erfolg... :fie:

 

[Gelöschtes Mitglied 79255]

AW: G-Box mit dem WIFI?

Nanana, da musst sowas erst in die Firmware eingewickelt werden. Ist nicht so einfach wie du denkst!

Vorstellen: Du G-Box runterladen, du kopieren per Cas auf Diablo, aber nix geht. Da nix implentiert in Diablo! Kapito.

 

[Phantom]

AW: G-Box mit dem WIFI?

Ja, diese sollte funktionieren. Getestet habe ich es jedoch noch nicht da ich derzeit kein Gbox Server habe.

 

[kiliantv]

AW: G-Box mit dem WIFI?

Gbox ist ja Implementiert müßte gehen, ich habe es nur noch nicht probiert.

Anbei die cwshare.cfg fürs Diablo

M: { CAM-IP { Passwort }}
D: { IP Receiver/internet { PortCAM PortRec./Internet { Passwort { 5 5 }}}}

Kommt dann unter EMU/GBOX, siehe Bild.

Anleitung dazu:

Hi Folks!

Great news coming! Your Diablo CAM Wi-Fi is now able to work as CardServer or/and Card Client. Thanks to the big card reader you can share locally or via internet your smartcard and act like a card server.
The first version of GBOX was supporting only the client function. Now you can share your Internal CAM Smartcard in a local network (home card-sharing) or with an external network like a DREAMBOX or QBox with any other receiver working with GBOX protocol.

Some quick instructions:
1. Emulators must be activated
2. Emulators must have priority on Smartcard (select that on the menu)
3. You must have the following files in the folders:
GBOX.BIN in EMU/GBOX folder (EMU/GBOX/GBOX.BIN)
CWSHARE.CFG in EMU/GBOX (EMU/GBOX/CWSHARE.CFG)

General instructions.

CWSHARE.GFC works exactly as the CWSHARE for Linux receivers. For your convenience I put some examples of configuration to copy and paste in case you want to have a quick configuration.

Typical CWSHARE file:

M: { 192.168.0.1 { AAAAAAAA }}
D: { 192.168.0.2 { 11111 22222 { BBBBBBBB { 5 5 }}}}

*************************************************
M (LOCAL MACHINE) CONFIGURATION
*************************************************

M= Local Machine (Your CAM it can be used as Card Server or/and Client)

M: { 192.168.0.1
^-------------- = Ip Address of your CAM

--> Case 1:
If you are using the CAM in a Local Network configuration here you have to put the IP of your CAM assigned by your router or DHCP.

(!) Tip:
It is better to use a static IP address as CAM IP address in order to prevent IP changes due to the DHCP server.
So the IP it will be an internal IP i.e. 192.168.x.x or 10.10.x.x depending on your router and Local configuration.

--> Case 2:
If you are using the CAM connected to an external Network here you have to put connection IP address provided by your ISP.

It can be a static IP or dynamic IP depending on you Internet Service Provider (ISP) connection.
To check you actual IP address you can see it on:

Sie müssen registriert sein, um Links zu sehen.

This may change accordingly with your ISP connection rules.

(!) Tip:
The IP address may change each single time you reset your router.
If you have a dynamic IP assignment (by ISP) it is better to use third party software installed on your PC, router or web based.
In this case you can put this string:

M: { myname.dyndns.com { AAAAAAAA }}
Where "myname" is the name assigned by dyndns (

Sie müssen registriert sein, um Links zu sehen.

)

M: { 192.168.0.1 { AAAAAAAA }}
^--------------- = Your CAM password (8 hex digits) NOT longer NOT shorter example: B1C5119A

**********************************************************
D (REMOTE PEER MACHINE) CONFIGURATION
**********************************************************

D = Remote Peer Machine (Other servers or client)

D: { 192.168.0.2
^-------------- = Ip Address of your Remote Peer Machine. The Peer Machine will work as Server or/and Client

--> Case 1:
If you are using the CAM in a Local Network configuration here you have to put the IP of your CAM assigned by your router or DHCP.
(!) Tip:
It is better to use a static IP address as CAM IP address in order to prevent accidental IP changes due to the DHCP server.
So the IP it will be an internal IP i.e. 192.168.x.x or 10.10.x.x depending on your router and Local configuration.

--> Case 2:
If you are using the CAM connected to an external Network here you have to put connection IP address of your Remote Peer Machine.
If your Remote Peer Machine has a static IP address you can put it (example 84.132.59.xx) or the domain name in case the Remote Peer Machine has a DynDNS or similar service connected.

(?) Example:
D: { 84.132.59.xx { 11111 22222 { BBBBBBBB { 5 5 }}}}
D: { mypeer.dyndns.com { 11111 22222 { BBBBBBBB { 5 5 }}}}

D: { 192.168.0.2 { 11111
^------------ Incoming Port of my CAM. This Port Must be opened. Please check your router configuration. The port to open must be assigned to the CAM IP address.

D: { 192.168.0.2 { 11111 22222
^--------------- Incoming Port of your Remote Peer. Your Peer must have this door opened

D: { 192.168.0.2 { 11111 22222 { BBBBBBBB
^---------------- This is your Remote Peer Password (the one that the M: must set instead of AAAAAAAA). The password (8 hex digits) NOT longer NOT shorter example: F1AD231A

D: { mypeer.dyndns.com { 11111 22222 { BBBBBBBB { 5 5 }}}}
^-^---------- Sharing levels. NOT supported in this version.

The D (remote peer) can be more than one.


******************************************************************************************************
** EXAMPLE 1: LOCAL CARDSHARING TYPICAL CONFIGURATION WITH 3 CAMs **
******************************************************************************************************
In this example you can set-up a local network using 3 CAM connected each other doing the home-cardsharing

Step By Step:
1. Emulators must be activated
2. Emulators must have priority on Smartcard (select that on the menu)
3. You must have the follwoing files in the folders:
GBOX.BIN in EMU/GBOX folder (EMU/GBOX/GBOX.BIN)
CWSHARE.CFG in EMU/GBOX (EMU/GBOX/CWSHARE.CFG)
4. Connect each single CAM to the receivers and assign them static IP from the IP menu accordingly with your router mask (192.168.x.x or 10.10.x.x etc)
CAM 1 IP address: 192.168.0.1
CAM 2 IP address: 192.168.0.2
CAM 3 IP address: 192.168.0.3

Now you are ready copy the files as shown:

CWSHARE.CFG file for CAM 1:

M: { 192.168.0.1 { A1A1A1A1 }}
D: { 192.168.0.2 { 11111 22222 { B2B2B2B2 { 5 5 }}}}
D: { 192.168.0.3 { 11111 33333 { C3C3C3C3 { 5 5 }}}}

CWSHARE.CFG file for CAM 2:

M: { 192.168.0.2 { B2B2B2B2 }}
D: { 192.168.0.1 { 22222 11111 { A1A1A1A1 { 5 5 }}}}
D: { 192.168.0.3 { 22222 33333 { C3C3C3C3 { 5 5 }}}}

CWSHARE.CFG file for CAM 3:

M: { 192.168.0.3 { C3C3C3C3 }}
D: { 192.168.0.1 { 33333 11111 { A1A1A1A1 { 5 5 }}}}
D: { 192.168.0.2 { 33333 22222 { B2B2B2B2 { 5 5 }}}}


******************************************************************************
** 2 CAMS IN LOCAL CARDSHARING AND 1 EXTERNAL PEER **
******************************************************************************
In this example you can set-up a local network using 2 CAM connected each other and one external Peer (Card Server)

Step By Step:

1. Emulators must be activated
2. Emulators must have priority on Smartcard (select that on the menu)
3. You must have the follwoing files in the folders:
GBOX.BIN in EMU/GBOX folder (EMU/GBOX/GBOX.BIN)
CWSHARE.CFG in EMU/GBOX (EMU/GBOX/CWSHARE.CFG)
4. Connect each single CAM to the receviers and assign them static IP from the IP menu accordingly with your router mask (192.168.x.x or 10.10.x.x etc)
CAM 1 IP address: 192.168.0.1
CAM 2 IP address: 192.168.0.2

and make sure you have the following datas:

"externalpeerip" is the IP address for your external peer: 84.132.59.32 (fake)
"myipaddress" is the IP address assigned by my IPS (check on

Sie müssen registriert sein, um Links zu sehen.

)

Now you are ready copy the files as shown:

CWSHARE.CFG file for CAM 1:

M: { myipaddress { A1A1A1A1 }}
D: { 192.168.0.2 { 11111 22222 { B2B2B2B2 { 5 5 }}}}
D: { externalpeerip { 11111 33333 { C3C3C3C3 { 5 5 }}}}

CWSHARE.CFG file for CAM 2:

M: { 192.168.0.2 { B2B2B2B2 }}
D: { 192.168.0.1 { 22222 11111 { A1A1A1A1 { 5 5 }}}}
** NO NEED HERE FOR EXTERNAL PEER IP ADDRESS BECAUSE CAM 1 IS DOING IT **

CWShare.CFG for EXTERNAL PEER.

M: { externalpeerip { C3C3C3C3 }}
D: { myipaddress { 33333 11111 { A1A1A1A1 { 5 5 }}}}

In this case the CAM 2 is connected to CAM 1 to make all the sharing functions. You have to consider that CAM 1 is necessary to make work CAM 2. If the receiver where CAM 1 is hosted is NOT turned ON CAM 2 will NOT work!
In this case swap the 2 CAMs on the receivers. This is the easiest solution