Hallo,
versuche vergeblich, meinen Rechner (bzw. dbox) von meinen Eltern aus zu erreichen.
Habe bei telnet ping und die dyndns eingegeben. Das


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
H:\Dokumente und Einstellungen\xxx>ping xxx.dyndns.org
Ping xxx.dyndns.org [87.xxx.148] mit 32 Bytes Daten:
Antwort von 87.162.228.148: Bytes=32 Zeit=44ms TTL=58
Antwort von 87.162.228.148: Bytes=32 Zeit=45ms TTL=58
Antwort von 87.162.228.148: Bytes=32 Zeit=44ms TTL=58
Antwort von 87.162.228.148: Bytes=32 Zeit=44ms TTL=58
Ping-Statistik für 87.xxx.148:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 44ms, Maximum = 45ms, Mittelwert = 44ms
H:\Dokumente und Einstellungen\xxxl>


kam dabei raus. Hatte gehofft, das ich durch eingeben der dnyndns oder der da oben stehenden ip im Browserfenster irgendwas sehen würde, kommt aber nur "Zeitüberschreitung".
Habe auch mal die newcs und cccam angeguckt, aber da finde ich gar nichts, was irgendwie nach Verbindung zu meinem Rechner zu hause aussieht:


have fun with KEYWELT on your Nokia D-BOX2 - Kernel 2.4.36.6-dbox2 (19:41:11)...
dbox login: root
BusyBox v1.7.2 (2008-10-30 00:59:12 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.
/var # CCcam -dv
19:41:28.779 CCcam: ================================================== ==========
==========
19:41:28.788 CCcam: starting CCcam 2.0.9 compiled on May 17 2008@15:55:36
19:41:28.789 CCcam: ================================================== ==========
==========
19:41:28.812 CCcam: online using nodeId 4b5f7xxxf2f
19:41:28.935 CCcam: dvb api3 detected
19:41:28.942 CCcam: create 1 cam device(s)
19:41:29.070 CCcam: added 143 keys from /var/keys/SoftCam.Key
19:41:29.109 CCcam: added 32 keys from /var/keys/AutoRoll.Key
19:41:29.176 CCcam: added 46 keys from /var/keys/constant.cw
19:41:29.188 CCcam: parsed 0 entries from /var/etc/CCcam.prio
19:41:29.701 CCcam: added 793 provider names from /var/etc/CCcam.providers
19:41:36.931 CCcam: added 4173 channel names from /var/etc/CCcam.channelinfo
19:41:36.936 CCcam: server started on port 12000


bzw.


have fun with KEYWELT on your Sagem D-BOX2 - Kernel 2.4.36.6-dbox2 (19:00:07)...
dbox login: root
BusyBox v1.7.2 (2008-10-30 00:59:12 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.
/var # CCcam -dv
19:00:14.783 CCcam: ================================================== ==========
==========
19:00:14.791 CCcam: starting CCcam 2.0.9 compiled on May 17 2008@15:55:36
19:00:14.793 CCcam: ================================================== ==========
==========
19:00:14.795 CCcam: online using nodeId f1daxxx53
19:00:14.848 CCcam: dvb api3 detected
19:00:14.855 CCcam: create 1 cam device(s)
19:00:14.956 CCcam: added 143 keys from /var/keys/SoftCam.Key
19:00:14.986 CCcam: added 32 keys from /var/keys/AutoRoll.Key
19:00:15.037 CCcam: added 35 keys from /var/keys/constant.cw
19:00:15.046 CCcam: parsed 0 entries from /var/etc/CCcam.prio
19:00:15.445 CCcam: added 707 provider names from /var/etc/CCcam.providers
19:00:22.820 CCcam: added 4258 channel names from /var/etc/CCcam.channelinfo
19:00:22.823 CCcam: server started on port 12000
19:00:22.911 CCcam: newcamd server 127.0.0.1:25030 user: server
19:00:23.067 CCcam: newcamd caid 1702 providers 4 userid: 0
19:00:23.069 CCcam: newcamd **** serial: 1a9943a4
19:00:23.072 CCcam: newcamd prov 00 000000 00ffffff
19:00:23.074 CCcam: newcamd prov 01 000001 00ffffff
19:00:23.076 CCcam: newcamd prov 02 000002 00ffffff
19:00:23.078 CCcam: newcamd prov 03 000003 00ffffff
19:00:23.195 CCcam: no working cam devices, no need to start pmthandler
/var # newcs -dv
This is NewCS 1.62 - the New ****Server by the Butter-team..
Compiled on Aug 27 2008 at 16:49:31
Reading Config file from /var/tuxbox/config/newcs.xml
TCP-log password is enabled, set to: webinterfacepasswd
TCP-log set to simple mode
level: normal
type: init
output: console,tcp
logger config: level 1 type 3 output 5
Console log options: level 1 type 3
TCP log options: level 1 type 3
[ 19:00:40 ] [ Box detect ] Box type 4 (Dbox2)
[ 19:00:40 ] [ Config ] Option <blockc0> for device 0 (Multicam) not present, de
faulting to NO
[ 19:00:40 ] [ Config ] Value in <ipk> for device 0 (Multicam) is INVALID, skipp
ing...
[ 19:00:40 ] [ Config ] Value in <ucpk> for device 0 (Multicam) is INVALID, skip
ping...
[ 19:00:40 ] [ Config ] Pincode for device 0 (Multicam): 0000
[ 19:00:40 ] [ Config ] /dev/tts/1 ECM priority: round
[ 19:00:40 ] [ EMM Cache ] Initialising dynamic Cache
[ 19:00:40 ] [ ECM Cache ] Initialising dynamic Cache
[ NewCS ] Process ID is: 655
[ 19:00:40 ] [ Loader ] Starting Telnet on port 1001
[ 19:00:40 ] bind: error! 98: Address already in use
[ 19:00:40 ] [ Loader ] Reader type 4 on node /dev/tts/1
[ 19:00:40 ] [ Dbox ] Opening device /dev/tts/1
[ 19:00:42 ] [ Loader ] Unknown ****
[ 19:00:42 ] [ Loader ] Trying Irdeto (T=14)
[ 19:00:42 ] [ Loader ] Reader type 4 on node /dev/tts/1
[ 19:00:42 ] [ Dbox ] Opening device /dev/tts/1
[ 19:00:43 ] [ ATR ] T=14 1etu=104.17us Guardtime:17etu WWT:9600etu
[ 19:00:43 ] [ ATR ] Historical bytes: I R D E T O A C S [03] [84] U [FF] [80]
[ 19:00:43 ] [ Loader ] Init Irdeto ****
[ 19:00:44 ] [ Keyman ] Adding key 000000009943a4 type 0 on Provider 000000 for
caid 1702 ID=0
[ 19:00:44 ] [ Keyman ] Adding key 00000000ffffff type 1 on Provider 000000 for
caid 1702 ID=0
[ 19:00:44 ] [ Keyman ] Skipping duplicate irdeto
[ 19:00:44 ] [ Keyman ] Adding key 00000000ffffff type 1 on Provider 000001 for
caid 1702 ID=1
[ 19:00:45 ] [ Keyman ] Skipping duplicate irdeto
[ 19:00:45 ] [ Keyman ] Adding key 00000000ffffff type 1 on Provider 000002 for
caid 1702 ID=2
[ 19:00:45 ] [ Keyman ] Skipping duplicate irdeto
[ 19:00:45 ] [ Keyman ] Adding key 00000000ffffff type 1 on Provider 000003 for
caid 1702 ID=3
[ 19:00:47 ] [ Loader ] **** 1702 on port /dev/tts/1 ready
[ 19:00:47 ] [ Loader ] Starting Newcamd Server on port 25030
[ 19:00:47 ] [ Newcamd ] Newcamd thread Server started on port 25030
[ 19:00:47 ] bind: error! 98: Address already in use
[ 19:00:47 ] [ NewCS ] Ready to GO! :)


bei mir auf dem Server.
Sagt diese pingerei von oben überhaupt schon was über das Funktionieren von der dyndns/der Portweiterleitung aus?

Gruß