DreamPlug

The DreamPlug is a plug-top computer. It draws about 5 wats of power, but includes two gigabit Ethernet ports, WiFi, BluTooth, 2 USB 2 ports, 1 eSATA port, audio in and out, SDHC card slot, and includes ports for connecting a UART serial port and a JTAG board.

The DreamPlug is what the GuruPlug should have been. I purchased my DreamPlug from New IT http://www.newit.co.uk/shop/proddetail.php?prod=DreamPlug for £135 including tax and delivery. I have also purchased two SheevaPlugs and a GuruPlug from New IT and thoroughly recommend them.

Sources moved

Canonical seem to have moved Jaunty Binaries. Put this into /etc/apt/sources.list

deb http://old-releases.ubuntu.com/ubuntu/ jaunty main restricted universe multiverse

deb http://old-releases.ubuntu.com/ubuntu/ jaunty-updates main restricted universe multiverse

deb http://old-releases.ubuntu.com/ubuntu/ jaunty-security main restricted universe multiverse

JTAG Board OS X Lion

Follow the instructions here to add the JTAG board as a USB serial device. Note that the OS X 10.6 (snow leopard) drivers work in 10.7 (lion) too:
http://www.newit.co.uk/forum/index.php?topic=2128.0

Once the FTDI drivers are loaded I can connect to the JTAG using screen:

screen /dev/tty.usbserial-FTT0GSKVB 115200

Simple screen commands:

Quit screen: Ctrl - a + k
Detach screen: Ctrl - a + d
Re attach to running screen session: screen -r
Serial port status: Ctrl - a + i

LEDs

The LEDs are named; 'red' is the WiFi led and 'green' is the WiFi-AP led.
So, turn on and off the WiFi led:

echo 1 > `eval ls /sys/class/leds/guruplug\:red\:wmode/brightness`

echo 0 > `eval ls /sys/class/leds/guruplug\:red\:wmode/brightness`

and turn on and off the WiFi-AP LED

echo 1 > `eval ls /sys/class/leds/guruplug\:green\:wmode/brightness`

echo 0 > `eval ls /sys/class/leds/guruplug\:green\:wmode/brightness`

Enable the flashing BlueToothLED
blinkled
Disable the flashing BlueToothLED
blinkbtled 0xf1010148 w 0x000

WiFi Access Point

Follow the instructions here to edit /root/init_setup.sh and configure the WiFi:
http://www.plugcomputer.org/plugwiki/index.php/Setting_GuruPlug_to_be_a_WiFi_Access_Point

I altered the SSID variable, and set the WiFi into WPA2 by adding these lines before the 'bss_start' command:
/usr/bin/uaputl sys_cfg_protocol 32
/usr/bin/uaputl sys_cfg_cipher 8 8
/usr/bin/uaputl sys_cfg_wpa_passphrase $KEY

udhcpd

You can change the IP address range of the DHCP server, by altering the IP address of uap0 in /root/init_setup.sh

ifconfig uap0 xxx.yyy.zzz.1/24 up

and also editing /etc/udhcpd.conf

start xxx.yyy.zzz.100

end xxx.yyy.zzz.200

interface uap0

opt   lease  86400

opt   router  xxx.yyy.zzz.1

opt   subnet  255.255.255.0

opt   dns   xxx.yyy.zzz.1

opt   domain  localdomain

max_leases   101

lease_file   /var/lib/udhcpd.leases

auto_time   5

A word of warning. udhcpd is a bit dumb, even though you've altered the config files it will still happily hand you out old leases for the old IP address ranges, so if you do alter the address ranges then remove /var/lib/udhcpd.leases before you restart:

/etc/init.d/udhcpd stop

/etc/init.d/udhcpd start

3G Comms

I have an android phone that I want to plug into the DreamPlug to share it's 3G over WiFi.
You can follow the instructions here: http://code.google.com/p/azilink/
But you'll need a copy of adb, the Android Debugger, for Arm. There is a link on this page http://fieldeffect.info/w/Beagleboard_Notes?action=AttachFile&do=view&target=adb and notes on how to build it yourself here http://fieldeffect.info/w/Beagleboard_Notes

Then, to get the link up, you run this to get the socket forwarding from the DreamPlug to Azlink on the Android.
adb forward tcp:41927 tcp:41927

Then, to get the IP tunnel up, run:
openvpn --config azlink.ovpn

3G USB dongle

THIS IS NOT WORKING YET

Instead of using my Anfroid phone, I'd like to use a 3G USB dongle.
The '3' 3G USB dongle I'm using is a ZTE MF627. It has two modes, when it's originally plugged in it appears as a USB CD-ROM, for automatically installing software drivers, and has to be ejected before it turns into a network device. When the device is a CD-ROM it's ID is 19d2:2000, when it's a network device the ID is 19d2:0031.

Here's an easy way to eject the CD-ROM device to turn the dongle into a network device:

Create:
/etc/udev/rules.d/ZTE.rules
with this contents:
SYSFS{idVendor}=="19d2", SYSFS{idProduct}=="2000", RUN+="/usr/bin/eject %k", OPTIONS+="last_rule"

Now when the dongle is inserted the udev daemon spots the device and sends the eject command. You can check the device ID with lsusb.

We can test the device now with chat:

chat -s -v '' ATZ OK AT+CSQ OK >/dev/ttyUSB2 </dev/ttyUSB1

in the output you'll see the current signal strength.

The stick seems to crash a lot - or perhaps it's the DreamPlug that is crashing...

/etc/ppp/peers/3g

lock

hide-password

noauth

connect "/usr/sbin/chat -v -f /etc/ppp/peers/3g.chat"

/dev/ttyUSB2

460800

defaultroute

noipdefault

user giffgaff

password password

mtu 1492

ipparam 3g

usepeerdns

/etc/ppp/peers/3g.chat

ABORT BUSY ABORT 'NO CARRIER'

ABORT VOICE ABORT 'NO DIALTONE'

ABORT 'NO DIAL TONE' ABORT 'NO ANSWER'

ABORT DELAYED

'' ATZ

OK ATQ0V1E1S0=0&C1&D2+FCLASS=0

OK AT+CGDCONT=1,"ip","giffgaff.com"

OK-AT-OK ATDT*99***1#

CONNECT \d\c

pon 3g

DreamPlug is mentioned on: Linux | GuruPlug | StartingPoints

mdsh.com/wiki