I'll clarify:

I used the source from d2plug.

I then compiled it.

The resulted uImage is different (in size and content) from the uImage in that you can download from the d2plug site.

I also used the "make header_install" as we both wrote, but the resulted files are NOT in the same format required by packageds that require the linux-headers. The required linux-headers are like the ones you have, for example, in /usr/src/linux-header-2.9.32-204-dove in the d2plug.
In kirkwood (the old sheevaplug) you could find the linux-headers by "apt-get install linux-headers-2.6.32-5-kirkwood"...

1. Yes. Right now I am using it as a client. My question is how to make it AP - and how to enable routing of other Wireless clients throgh the d2plug's eth0 connection.

2. the bluetooth is fine.

3. I tried. It seemd that the network connection I am booting from (wireless or eth0) stays untill I'm booting again. Does your d2 switch betweeen eth0 and mlan0 once you plug eth0 out of the switch?

I compiled d2plug_lsp_src_v0p4.tar.bz2 from http://www.plugcomputer.org/downloads/d2plug/index.html and a) the reslted uImage is different than the one in http://www.plugcomputer.org/downloads/d2plug/index.html, and b) even using make install_headers - you don't get the required headers.

In the /usr/src/ directory you can find linux-headers of other versions than the kernel. These other linux-headers are also in d2plug-rootfs-20110903.tar.gz.

In /lib/module there is a directory that is partially right, /lib/modules/2.6.32.9-dove-5.4.2.

Can anyone help me with creating a proper linux-header-2.6.32.9-dove-5..4.2?

OK, I managed to work. But it was crazy - and there is one important lesson...

The wpa_supplicant was configured by looking at the "wpa_supplicant -Dwext -imlan0 -c/etc/wpa_supplicant.conf -dd" results (important - use the -dd to see what happens), while playing with various parameters in the wpa_suppliant.conf file.

Eventually, I managed to see with iwconfig the hidden  ESSID I used (in the .conf you have to say ap-scan=2), and the end result, in my AP setting, was:

ctrl_interface=/var/run/wpa_supplicant
ap_scan=2

network={
        ssid="name of access-point"
        psk="ascii-string of wpa string"
        key_mgmt=WPA-PSK
        proto=WPA RSN
        pairwise=CCMP TKIP
        group=TKIP
}

Then, I made wpa_supplicant run at boot (write a script and put it in init.d, then update-rc), but do not forget to add -D to the wpa_supplicant command (for daemon).

Then - I saw the mlan0 in ifconfig (dhcp address) and in iwconfig (with the right ESSID) - but mlan0 did not work. Every time I pulled eth0 out of the LAN - the wireless (mlan0) did not work (despite the fact it had IP address and an assigned ESSID).
Half a day went, and then, I plugged the eth0 out, and booted. Only then, the mlan0 started to work...

As for the bluetooth, it was a stupid error in the RC.2/SXXX loading sequence. You have to use for start:
        modprobe bluetooth
        insmod /lib/modules/bt8xxx.ko
        /etc/init.d/network-manager restart

Now, if anyone can tell me how to set things more easily to turn the mlan0 into an AP (there is some READing to do in
/usr/src/linux-headers-2.6.32.9-dove-5.4.2/Documentation/networking/mac80211... anf I'm not sure how much this is relevant.

True. This is the right version. However, you have to build the kernetl-tree that can be used by other pakages. I am trying to install DAHDI, for example (http://downloads.asterisk.org/pub/telephony/dahdi-linux/releases/dahdi-linux-2.6.0.tar.gz), and it requires this tree. I never built it from the kernel source, and usually, what I've done before is get-apt install linux-headers-$[uname -r].

Going into the kernel and trying to build the header files (by make header_install) creates a directory which is not compatible with what DAHDI requires.

BTW, in /usr/src/ you can find some linux-headers that are not for this image (I managed to get the 2.6.32-219-dove, the -204-dove, but none are working correctly). In lib/modules you will find the right tree, i.e., /2.6.32.9-dove-5.4.2, but it again seems to miss some files, e.g., .build, that is required by DAHDI.

I hope this detailed (and long) message explains... and sorry for the length.

I'll try both sugestions later (probably this weekend) and let you know. Thanks

I saw it. This file does not contain "linux-header-2.6.32.9-dove-5.4.2" which is required for compilation, (following the image, see uame -r). In Sheevaplug, for example, you could find the kirkwood files (e.g., debian's files were "linux-headers-2.6.32-5-kirkwood"). We need the dove files. They are NOT in d2plug_lsp_src_v0p4.tar.bz2.

Or am I missing something?

I coudn't find it in the download site. Could you be more specific? or can you attach it? It is mandatory to all of us, and compiling anything that require some Linux internals requires it (I am trying to install Asterisk, and Dahdi requires these headers...).

Thanks

a) I tried WPA_Supplicant, and I also tried define it under /etc/network/interfaces, but none worked.
b) I used similar script as 8787 to run load Bluetooth. However, it was not effective, as Bluetooth was not up after booting, and I had to enter the initialization commands sequence to run it. There was a comment, though, in 8787 that there might be a problem due to internal processes that could'nt finish at time of init invocation, thus you may not be able to initialze Bluetooth at init. I am looking for someone who managed to do it - and tell me how.

Hi,

Can anyone assist me on how to get the right Linux-header-2.6.32.9-dove-5.4.2 source/header files? I tried using the linux-header-2.6.32-219-dove, but that seems to cause problems, as the image is different...

Thanks, Ran

Hi,
Two issues:
a) did anyone managed to run the Wi-Fi in WPA? I coudn't set it up using WPA_* or etc/../interfaces.
b) I managed to use the Bluetooth, but after boot it seems you have to reload everything (I used init..RC2, similar to 8787 with all the required stuff).

Thanks, Ran

I second to this suggestion - I have several issues, and looking through all HW/SW issues of irrelevant stuff - is quite impossible