Hi - I'm a new MBWE owner, but I have the latest 1TB model (white case w/ light strip on front). All the hacks I've seen are apparently for the older model.

Anyone have any hacks yet for this new model? Specifically, I'm looking to be able to see a directory listing of my Public shares when connected to the MBWE remotely via HTTPS. Anyone know what file I need to modify to make this happen?

I already have the MBWE setup to access it via HTTPS (admin interface only) and SSH and can do so without any problem. Unfortunately it appears a great deal has changed between the older and newer model MBWE as I don't see many of the same files/directories referenced in the hacks. For example, there is no /etc/lighttpd directory on the new model.

Interesting… I found that I can access the TwonkyMedia server directly via HTTP. If I type in http://MyDomainName:9000/webbrowse and set a port forward rule on my router to forward TCP/UDP traffic on Port 9000 to the MBWE then I can access the web browser interface of TwonkyVision. This essentially gives me a directory listing of all the content in my /Public/Shares and I am able to stream my music/movies and view pictures in the browser.

The TwonkyVision web browser interface also lets you upload files into your shares as well. Because of this I have disabled my port forward rule for now due to the obvious security implications involved. If I can figure out a way to make an HTTPS connection to this interface and force some kind of authentication then I would be satisfied.

mini_httpd is used instead. this webserver seems to support SSL for https access….
there is no longer fastci support ( for accessbook and other hacks i did)
but it looks like there is native php support.

by the way, Dryvlyne ,
could you share with us the way you used to get SSH access to the Mybook White Light?
Regards,

Well, I can access the MBWE admin interface via HTTPS. The problem, however, is that (as far as I can tell) you can only access the TwonkyMedia server and browser via HTTP. I can add a Username & Password on the Twonky config page and it works (I get prompted when I try to access it from outside my network), but I don't know what good this is if it's sent in the clear (I've disable my Port Forward rule for now).

At any rate, if you have any suggestions I'm all ears.

As far as SSH access is concerned, there is just a box you check in the MBWE admin interface. It's very simple/easy to access via SSH.

By the way, you mentioned that this new model appears to have native PHP support. How can I test this? Where should I put a simple PHP page so that I can browse to it via HTTP(S) so I can test this? Sorry, I'm kind of a noob when it comes to *NIX related things.

Hi, Dryvlyne!
Yes the new My Book has native support for php which is great as everyone can write scripts to do work in an autonomous fashion.
You can use vi to create a simple php file.
On details how to use vi visit:http://www.eng.hawaii.edu/Tutor/vi.html
So use VI to create a file named a.php for example. Then enter something like this:

<? php phpinfo(); ?>

and save it (escape :wq).
then pass the file name as an argument to the php preprocessor:

php a.php

You will see a html code dump as a result of the command in the console. To generate a html file use the following:

Hi fercq,
I am currently working at a web Server Feature Pack for the Mybook Whitelight which will include :
- Private https web server with encryption and authentication on port 443
- Public http web site for publishing web sites…
- AccessBook Application to share files with friends, browse remotely , download / upload etc…

If you are patient enough, it should be ready in its first version within 3 weeks…

During this crisis one would expect the manufacturers to become more competitive and give a bit extra. Memory chips don't need R&D anymore so they could be cheaper thus it's more interesting to keep the price the same but put more memory in it.

For the benchmark, I've got this values so far:
FTP GET 11430 kB/sec
FTP PUT 11240 kB/sec
NFS Read 6905 kB/sec
NFS Write 5524 kB/sec
Please note that my network switch is 100MBit only, so this could be a limit for the FTP mark.
Test material was one file with about 1 GByte. No attempts so far to improve the NFS
performance (I'd like to use NFSv4). Since I am a Microsoft Noob, I didnt success in testing
SMB performance.

Yes, I disabled Mionet (was the second thing I did after enabling SSH ;-)
I also disabled the donkey tonky thing and the mDNSresponder.
Last night I managed to test the SMB/CIFS performance:
SMB Read 4274 kB/sec
SMB Write 6273 kB/sec
This morning I did another benchmark with my wife's Laptop (which has gigabit ethernet) directly connected to the MBWE. Now I have:
FTP GET 13689 kB/sec (MBWE CPU load ~12%)
FTP PUT 18020 kB/sec (MBWE CPU load ~95%)
I am sorry, but regarding the CPU loads I think my benchmark are not very representative, because my computers are not fast enough to really stress the MBWE to its limits.
I discovered some other things with the new MBWE:
- The HD (WD10EAVS-00D7B1) does not seem to support SMART :-(

Sorry, steps you posted work without any problems.
I removed all files left from my previous attempts. rebooted and reinstalled optware.
Now it is working. Just followed steps you posted (replacing ipkg-opt_0.99.163-9_arm.ipk with ipkg-opt_0.99.163-10_arm.ipk). Clearly there was some mistake on my side.
Finaly have midnight commander running :)

I've added a wiki page with bzhou's script to get ipkg installed. My page also includes two minor tweaks that I needed to get everything smooth. The page is located here: installing ipkg on MyBook World white light. Thank you, bzhou!

cs05q3armel is not the actual feed for the white book (right kernel but wrong glibc 2.3.6)
please delete your wiki page - the actual informations for ipkg optware on white book are here: http://mybookworld.wikidot.com/optware

So I just installed optware and I am *DELIGHTED*! Thanks alot, guys :)
Now is there a chance to "recover" gcc?
I would like to get unison (file synchronization) working with my wd book and therefore need gcc.
For any hints and answers thanks in advance.

I've a question about your bricked MBWE. Can you still turn your MBWE off using the powerbutton ? I had a bricked MBWE where the powerbutton did turn it on but wouldn't turn it off anymore. I'm still wondering if i bricked it myself or not…
Here is what i did.

I did use the ssh to install optware and transmission en nano packages.

I had transmission running (only manual started, not with a boottime-script).

I wanted to bacup my computerfiles. The transfer rate was acceptable (~4.5MB/sec) but less then i hoped for. Then i decided to use a crossover-cable to connect the MBWE directly to my computer. The powerbutton didn't work so i turned it off using the Web-manager.

I didn't get the static-ip setup on my Ubuntu-computer right but now i couldn't connect to the WebUI and the powerbutton didn't work.

I decided to reconnect the MBWE back to my router, but i had to cut the power

After that it was bricked.

So what's your guess ? Did i bricked it myself or not. ?
For your information: I did send the MBWE back to the shop and got my money back. I've not decided yet if i'm going to buy a new MBWE or buy another (more expensive) nas.

A public web site on port 8080 will serve pages hosted on /shres/Public/WWW/WWW-pubhttp://Mybook:8080

a private web site on port 443 ( https://mybook ) , encrypted and authenticated is also configured , and you can manage user access via the menu of the Feature pack manager.
AccessBook will also be installed , so that you can access your files remotely , and securely, and share your files with friends.

Yes i know about the Feature packs with the webserver, i have it installed already, but i didnt want to type in http://ipadress:8080. I´m thinking about using my mybook as a web dev unit as well hence i would like to use something that runs on port 80 by default. But if there isn't a way to do this of course i have to use port 8080 instead, i was just trying to be convenient :)

Anyway, another problem arised today while i was tinkering around. I tried to change the document root of the lighthttpd server from "/shares/Public/WWW/WWW-pub" to "/var/www/WWW-pub". I was just copying the WWW-pub and WWW-priv from /shares/Public/WWW/ to /var/www/ but all i get is a 403 - Forbidden page from lighthttpd. Do you or anyone else know why this is?