DSM-G600, DNS-3xx and NSA-220 Hack Forum

Well - for starters, you're going to need to compile the appropriate HID (human interface device) driver for the processor and load it, and seeing as there's no display ...

Understand this - the possibilities are limited only by your capabilities - however, there is a point of what is known as "diminishing returns", when it would just be simpler to start with standard PC and do what you need.

Personally I see little value in it (actually, none). You can telnet/ssh into the unit and perform any action and even see what you are typing and the responses. I purchased these units since I specifically wanted a headless device, low power consumption, small space etc. The last thing I want is another keyboard (larger than the unit itself). Everything I need to script is done and I rarely telnet in any more. I have 2xDNS-323 units and 3 full Linux servers. None have mice, keyboards or monitors. I can telnet in from a PC, my smartphone or a number of other devices locally wired, wireless or remote.

Last edited by FunFiler (2011-03-07 23:27:24)

fordem wrote:

you're going to need to compile the appropriate HID (human interface device) driver for the processor and load it

Thanks for the advice, any good links to start with this ?

FunFiler wrote:

Personally I see little value in it (actually, none).

Think about a barcode scanner for example : you just scan something and the NAS will do what you want (to manage your books for example) You don't need any display or thing like that (you can maybe let the front leds blink to inform the user that the action was successful)

Mijzelf wrote:

Actually I have connected a keyboard to my NAS. (Only the PCB, btw).

Nice job ! How exactly did you do that ?

Thanks for your responses

Mijzelf wrote:

you need to compile the appropriate HID driver, usbhid.ko in this case, and maybe some dependencies.

Thanks, but can you give me more hint on how to do this ?
Thanks a lot.

I'm using the reloaded method to run debian squeeze with the debian kernel and kernel modules (I don't want to overwrite the dlink firmware since I don't have a serial console)

The debian kernel module package does have most of the normal kernel modules (88 total) including the usbhid module.  I imagine it's about the same amount of work to get a reloaded debian environment working as it is to get the toolchain and build the modules for the dlink kernel (assuming the modules don't require a kernel setting that dlink didn't enable).

psyko57 wrote:

I've tried to load the plugin, but i can't "cat /dev/tty0"...

Did it load? What did dmesg say when you plugged in the keyboard?

Hm. Mine says:

usb 2-1: new low speed USB device using ehci_platform and address 7
usb 2-1: configuration #1 chosen from 1 choice
input:   USB Keyboard as /class/input/input0
input: USB HID v1.10 Keyboard [  USB Keyboard] on usb-ehci_platform.16781-1
input:   USB Keyboard as /class/input/input1
input: USB HID v1.10 Device [  USB Keyboard] on usb-ehci_platform.16781-1

So it's recognized as a keyboard *and* as a device. Don't know what that means, though.
About cat /dev/tty0; do you have that node? On my system it's

crw-rw---- 1 root root 4, 0 2011-02-20 14:14 /dev/tty0

Further it's not world readable (unless you change that), so it can only be 'cat'ed by root.
When you 'cat' it, you only see the output when you press enter,

Try to load usbkbd.ko

psyko57 wrote:

I've tried to do 'echo plop > /dev/tty0' but even with this, 'cat /dev/tty0' don't display anything...

(Plop?) That is normal, A 'tty' is sort of a terminal. So 'echo plop >/dev/tty0' displays plop on the monitor assigned to that tty, while reading gives the input of the keyboard, and maybe even of the mouse.

Maybe we just can't 'cat' a tty ?

I can. But it's a different box and a different kernel, and I don't know which differences are important.
Some googling on 'keyboard embedded linux' led me to SamyGO, some TV hacking project, and it gave me this script:
MouseAndKeyboard.sh:

#!/bin/sh

cd $1

# Load keyboard and mouse support
insmod ./modules/usbhid.ko
insmod ./modules/evdev.ko

# Generate input device nodes at /dtv
i=0
while [ $i -le 31 ]
do
    mknod /dtv/event$i c 13 $(($i + 64))
    i=$(( i + 1 )) 
done

I think /dtv can be translated to /dev in our case. But I must admit that there are no /dev/eventx on my box.

I un- and reconnected the keyboard, and udev made this modifications. In /dev:
crw-rw---- 1 root root    442, 2057 2011-03-13 19:34 usbdev2.10_ep00
crw-rw---- 1 root root    442, 2057 2011-03-13 19:34 usbdev2.10_ep81
crw-rw---- 1 root root    442, 2057 2011-03-13 19:34 usbdev2.10_ep82
drwxr-xr-x 2 root root         2800 2011-03-13 19:34 char
crw-rw-rw- 1 root root      5,    2 2011-03-13 19:35 ptmx
in /dev/char:
lrwxrwxrwx 1 root root 18 2011-03-13 19:34 442:2057 -> ../usbdev2.10_ep82
lrwxrwxrwx 1 root root 18 2011-03-13 19:34 189:137 -> ../bus/usb/002/010
And this 189:137 points to:
crw-rw-r-- 1 root root 189, 137 2011-03-13 19:34 010

It's not clear to me what this all means.