How about adding in WEDAV client /and/or server
SNAKE OS firmware for wlxkj652, ns-k330 and NAS based on str8132 SoC
Brought to you by:
dgazineu
Menu
▾
▴
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: amsgo... (code.google.com)@gmail.com
a must have feature these days
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: stefansc...@googlemail.com
I've been dabbling with webdav via lighttpd. Accessing it with linux clients (cadaver, thunar) worked ok, but from Windows writing files doesn't work. Windows behaves the same way when running lighttpd on a PC though, so maybe lighttpds webdav support is just incomplete.
I guess I'll try apache or nginx next (if they compile at all).
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: amsgo... (code.google.com)@gmail.com
I read about some issues on Windows too. It seems that native Windows support for WebDav is not so stable as expected.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: stefansc...@googlemail.com
Got apache to run, but it's even worse. Windows won't even read files with it (Linux is fine again). Maybe there's actually something wrong with my windows installation or the network. I need to take a look at the traffic.
Google doesn't bring up a whole lot about issues with Windows (other than that the default file size limit is 50MB, but that can be fixed with a registry tweak).
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: stefansc...@googlemail.com
Ok, figured out what broke reading from windows. A type conversation got messed when cross compiling, which caused apache to report bad file sizes. The other clients I tried don't check the size values so they weren't affected.
Attached is an opk package with apache. It comes with an init script so that the server will be launched at boot time and a really basic setup page (Services->Apache).
Things to keep in mind.
I'd suggest to only make the server accessible on a LAN. That's no authentication, although it could be enabled in the apache config. It also runs as root/admin to keep things simple, but that's usually a big no no.
Windows copy dialogs don't show the progress properly. They sit at 0 or ~99 percent until the operation finishes.
I've had interrupted file transfers leave locked files behind.
Throughput is about 5 MB/s.
Memory usage seems to get quite high. I haven't checked yet how it behaves with another memory hog like transmission installed too.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: amsgo... (code.google.com)@gmail.com
Good news...
If you need some help, let me know. I can do some tests as I still have my wlx but I am not using it.