So nobody has every encountered this?
I am trying to telnet into my DM800 running Jade3 by opening up a command prompt and typing in:
telnet 192.168.1.3 (Dreambox IP)
and i get the following jibberish.. Has anyone encountered this before? I am pulling my hair out trying to telnet. I have tried several machines with no luck.
BusyBox v1.01 (2009.09.24-16:40+0000) multi-call binary
Usage: busybox [function] [arguments]... or: [function] [arguments]...
BusyBox is a multi-call binary that combines many common Unix utilities into a single executable. Most people will create a link to busybox for each function they wish to use and BusyBox will act like whatever it was invoked as!
Currently defined functions: [, addgroup, adduser, ar, arping, ash, awk, basename, bunzip2 busybox, bzcat, cat, chgrp, chmod, chown, chroot, chvt, clear, cmp, cp, cpio, crond, crontab, cut, date, dc, dd, deallocvt, delgroup, deluser, df, dirname, dmesg, dogs2unix, du, dumpkmap, echo, egrep, env, expr, false, fbset, fgrep, find, free, ftpget, ftpput, getkey, getty, grep, gunzip, gzip, hdparm, head, hexdump, hostname, id, ifconfig, ifdown, ifup, insmod, ip, kill, killall, klogd, ln, loadfont, loadkmap, logger, login, logname, logread, losetup, ls, lsmod, md5sum, mkdir, mkfifo, mknod, mkswap, mktemp, modprobe, more, mount, mv, nc, netstat, nslookup,
od, openvt, passwd, patch, pidof, ping, pivot_root, printf, ps, pwd, readli
nk, renice, reset, rm, rmdir, rmmod, route, run-parts, rx, sed, seq, sh, sh
a1sum, sleep, sort, start-stop-daemon, strings, stty, su, sulogin, swapoff,
swapon, sync, sysctl, syslogd, tail, tar, tee, telnet, telnetd,test, time, top,
touch, tr, traceroute, true, tty, udhcpc, umount, uname, uniq, unix2dos, u
nzip, uptime, usleep, uudecode, uuencode, vi, vlock, watch, wc, wget, which, who, whoami, xargs, yes, zcat
Connection to host lost.
C:\Users\username>
edit: i've managed to ssh to the box with putty. I still find it strange telnet doesn't work. I have used it before.
Last edited by johnbarry; 26-06-10 at 01:09 AM.
Humax 5400, Strong 4653x, Strong 4668x, DM500, DM800
90cm KU, 3M C Band
Member since 2003
Look Here -> |
So nobody has every encountered this?
Humax 5400, Strong 4653x, Strong 4668x, DM500, DM800
90cm KU, 3M C Band
Member since 2003
try using putty
may not help, but may also
__________________________________________________ __
Statistically, if you wait long enough, everything will happen!
johnbarry (30-06-10)
Well, I am not familiar with Dreamboxes, but I believe they are linux based..
So, it looks like the mapping between TCP port 23 and Telnet is gone and replaced by Busybox. Note busybox has Telnet as one of its options. I have never used Busybox or can really see its usefulness..
So look at portmap if it exists, or look at Busybox setup options.
I'd rather have a bottle in front of me than a frontal lobotomy...
Have a try with the telnet client built into Dreambox Control Center
You will need the E2 version for DM800's
Reality is an invention of my imagination.
ಠ_ಠ
johnbarry (30-06-10)
I had already tried DCC and PuTTY, got exactly the same error.
Can someone please remind me where the config file is for all the port mappings? I remember accessing it a while ago, but i forgot the name and location.
Humax 5400, Strong 4653x, Strong 4668x, DM500, DM800
90cm KU, 3M C Band
Member since 2003
In PLI jade on a dm600 the following apply:
/etc/services maps tcp and udp port numbers to services
/etc/inetd.conf maps applications to these services
/etc/busybox.links links applications to the busybox multi-call binary
From your initial posting, there appears to be an issue with a missing space between telnetd and test. If you check inetd.conf, you should see that telnetd is the application run when you open a tcp connection to the DM on port 23. Busybox is then linked to telnetd in /etc/busybox.links. This all appears to be working properly, as busybox is starting and returning what is in fact an error message, as it doesn't appear to recognise the telnetd initiation. To check this, ssh into the DM, and enter:
busybox telnetd
This should open a new login shell. If you see the same error screen as your initial posting, it would suggest that my hypothesis about the error in busybox is correct.
johnbarry (30-06-10)
Thanks for your reply, the busybox telnetd command opened up a new shell, so that works.
My inetd.conf has the following, is this correct?
telnet stream tcp nowait root /usr/sbin/telnetd telnetd
I opened up /usr/sbin/telnetd and it had a whole heap of strange characters in there, is that correct?
Humax 5400, Strong 4653x, Strong 4668x, DM500, DM800
90cm KU, 3M C Band
Member since 2003
inetd.conf looks ok. Check the link for telnetd - it should look like:
root@dm600pvr ~ # ls -l /usr/sbin/telnetd
lrwxrwxrwx 1 root root 17 Jan 1 1970 /usr/sbin/telnetd -> ../../bin/busybox*
Busybox should recognise the last field of the call (in this case telnetd) and fork off the same application as if it was run from the command line (ie busybox telnetd). From your original post and your inetd.conf, it looks like telnetd is being run, but busybox doesn't recognise it. You can check it by the following:
root@dm600pvr ~ # cd /tmp
root@dm600pvr /tmp # ln -s /bin/busybox telnetd
root@dm600pvr /tmp # ./telnetd
This should also generate a login shell.
johnbarry (30-06-10)
I have done all that and it came up with a login (see below). I still can't telnet directly to the box though without ssh, any other suggestions?
root@dm800 ~ # ls -l /usr/sbin/telnetd
lrwxrwxrwx 1 root root 17 Jan 1 1970 /usr/sbin/telnetd -> ../../bin/busybox*
root@dm800 ~ # cd /tmp
root@dm800 /tmp # ln -s /bin/busybox telnetd
root@dm800 /tmp # ./telnetd
ÿýÿýÿý!ÿûÿû
PLi® jade3 dm800
dm800 login:
Humax 5400, Strong 4653x, Strong 4668x, DM500, DM800
90cm KU, 3M C Band
Member since 2003
What do you get when you run /usr/sbin/telnetd directly?
johnbarry (30-06-10)
That may not be the same telnetd. Your command should be
root@dm800 /sbin # ./telnetd
It probably is the same, but you can check this with:
root@dm600pvr # which telnetd
/usr/sbin/telnetd
After having another look, I'm not convinced that telnetd is the problem. You appear to be establishing a telnet connection, but a subsequent call to busybox is causing a problem. I wonder if the line of rubbish before the PLi message is being echoed back from the PC and forking another busybox process. I think you may need to take this up with the .
Bookmarks