This page contains a link to a modified factory Dreambox 5600 image that contains kernel support for a serial console, serial-line PPP and net-aware applications such as telnetd and ftpd.
With this image installed, your Dreambox 5600 can become a fully-fledged member of the Internet with all the risks and benefits that implies!
You May Want To Read More About:
These instructions assume that the computer that acts a gateway for the dreambox is secured, ideally behind a separate firewall. If your gateway computer is not secured in this way, your dreambox and therefore your network may be exposed to malicious minds on the Internet - you have been warned!
These steps help you verify that the image installed correctly and that PPPD is running on the dreambox.
Dreambox DM5600 Linux/PPC load: root=/dev/mtdblock/0 ro rootfstype=cramfs console=null
echo 1 > /proc/sys/net/ipv4/ip_forward # nb: you must be root to do this
This step is optional. If you don't do it, the dreambox will only talk to the computer it is directly connected to. If you do it, the dreambox should have the same access to the network as the machine it is connected to. Note, however, that in certain circumstances doing this may compromise your network's security, so think carefully and seek advice if unsure.
Some guidelines are:
#
# runs pppd in foreground and with debugging enabled
# talking to ttyS0 at 115200bps using hardware flow control
# with local ip address (local-ip) and dreambox ip address (dreambox-ip)
# with advertisements via ARP of the dreambox's IP address
#
pppd -d -detach /dev/ttyS0 115200 crtscts local-ip:dreambox-ip proxyarp
You will probably want to investigate how best to automate these steps so that you don't have execute them everytime you reboot the gateway.
These instructions are included as a courtesy of those users who, even at home, remain trapped in the Windows Matrix.
These instructions are based on material found at: http://bwinton.latte.ca/Palm/ppp.html. See that page for screen captures that may guide your setup. Note: that I found that it was best to assign an explicit pool of IP addresses rather than have Windows automatically allocate them. If I leave it to Windows to allocate them, Windows would tend to choose addresses that were already used on my network causing the PPP setup to fail. Also, make sure you reconfigure the maximum speed of the null modem you create to 115200 - you have to do this on the modem object, not on the connection object.
These steps will:
These steps adds a line to a modem configuration file so that Windows can recognize an incoming PPP connection.
HKR, Responses, "~", 1, 08, 00, 00, 00, 00, 00, 00,00,00,00 ; Server side - the client is requesting a connection
enter a range of IP addresses that comply with the guidelines specified in the Linux configuration instructions above
It is probably best if you choose a range that is 2 addresses wide, so that the end address is always allocated to the dreambox.
If the connection was successful, you should see a line with the following columns in your "Network And Dialup Connections" folder:
<Unauthenticated user> | Direct | Connected.
The IP address assigned to the dreambox will be evident by selecting "Status | Details" from the connection's context menu and then looking at the value of the "Client IP address" line.
If the connection doesn't seem to happen, you can try debugging it using the trace facilities described by this Micro$oft article (google: netsh ras ppp).
It may also be useful to inspect the null-modem's log by selecting the null-modem's definition object and selecting "View log" from its context menu. In the modem log, if you see a line like: "Recv: ~" followed by another which says: "Unknown Response" you almost certainly didn't do the mandatory reboot after editing mdmhayes.inf. Do it now :-)
At this point you should have a working PPP connection. Under Linux this will be indicated by a foreground pppd process that hasn't yet terminated. In Windows, this will be indicated by the presence of a line in the "Network and Dialup Connections" folder as described above. If you don't have a working PPP connection you need try and work out why before continuing with the following steps.
These steps help you verify that the PPP connection really is working.
use telnet to connect to the telnet daemon on the dreambox's ip address (user=root, password=dreambox).
Note: if it takes a while for the telnet login prompt to appear, there is probably an issue with name resolution on your network. If so, you may want to edit /var/etc/ppp/options on your dreambox to remove the usepeerdns option and manually add nameserver entries to /etc/ppp/resolv.conf on your dreambox.
This image has support for various "pseudo" kernel options. To take advantage of these options, you need to connect to the Dreambox with a 115200 bps serial terminal, reboot it and, when prompted, edit the boot arguments appropriately.
The image above was created by taking an "official" Dreambox 5600 image and modifying it in the following ways:
An idea of exactly which image files were touched can be obtained by untarring the tarball listed above.
Instructions for duplicating the build will be forthcoming as and when I get time to document them.
I don't build, distribute or have any interest in images that contain code that might get me thrown in jail, so don't even ask. You _will_ be ignored.