From my research, it sounds like I need either the Kong DD-WRT or the Tomato ... can anyone recommend one over the other, from experience, for the E3000?
Do they both give the same performance as far as LAN speeds over wifi?
Kong has made a customized and optimized version of dd-wrt that works quite well. It comes in different flavors, one including minidlna which is a full featured media server application. I think it supports the E3000 router.
I've used this build for some time now on an Asus RT-N16 and is very happy with performance and functionality
Thanks for the heads-up. I had pretty much given up on this subject already. Can you just confirm if this is the correct version you are talking about?
If you read all the way down the OTRW wiki page, you will see where it states that on K26 routers NONE of the the DLNA servers work. This is tied to an issue on the interface.h file on all K26 builds. (try and enter 'netstat -i' and watch it blow up). This has to do with the netutils that are on the build.
So, KONG went ahead and made miniDLNA work and we know that works for sure. I have not tried to run Twonky on a Kong build, but I suspect that the work-around he created was specific to miniDLNA and that the Twonky dependencies on netutils are still broken.
Just for all to know... try and activate Twonky and see if it works on the Kong Builds.
On a terminal window, type the following two commands:
(Sigh...)
If you read all the way down the OTRW wiki page, you will see where it states that on K26 routers NONE of the the DLNA servers work. This is tied to an issue on the interface.h file on all K26 builds. (try and enter 'netstat -i' and watch it blow up). This has to do with the netutils that are on the build.
Sorry, not sure what that means ... what's a K26 build?
Over on the Tomato USB forum, someone said they installed Tomato + optware and it runs fine...
I did not mean to be condescending on my prior post. Please take the time to read the announcements on the forum and PARTICULARLY MAKE SURE YOU READ THE PEACOCK THREAD. These are not there for decoration, they DO really have excellent information for ALL, but specially for the newcomers.
Everyone here was, at some point, a Noob (newcomer) of some sort. The mods have done a great job at providing information, that when read and understood, can get you up to some level of speed on the lingo, etc. that is used at on the forum.
If you are unable to tell what a K26 build is, you should not be messing with your router and loading firmware on it. Not knowing of your router takes a K24 or K26 (references to Linux v2.4 or v2.6 kernels) can brick your router.
Please take a little time and read, read, read so you are well informed before loading a firmware on your router.
Quick question - since I didn't believe I would have a solution for this issue with my router, I bought a
Seagate FreeAgent GoFlex Home (STAM2000100). This would allow me to have higher transfer speeds than USB while being more reliable...
Well, it also doesn't work the way it should. Its media server does not show all of the files I select for sharing. Besides that it works great as a NAS.
The question is: can I use the miniDLNA to share these files instead? They are not connected to the router by the USB port, but are available on the NAS drive on a fixed IP.
If you enable CIF and mount the NAS drive with the fixed IP (I don't know where CIF mounts are mounted these days... way back when, they would be mounted to /tmp/share.
You could conceivably then configure your miniDLNA to read a mounted directory even if it is a CIF mount.
I tried mounting cifs as you suggested, but I couldn't make it work.... this is what I get when I try to mount it:
Code:
root@DD-WRT:~# mount.cifs //10.10.1.142/ /tmp/smbshare/ -o username=$(nvram get samba_user),password=$(nvram get samba_password)
mount error: cifs filesystem not supported by the system
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)
From what I can figure out, the default file system used by seagate is NTFS. Would this be the problem? Any ideas how to get past that?
Please confirm that you first enabled CIF on the Administration page of the router.
Now, the user and password you need is NOT the one on your router. You need to enter the user and password that your Seagate has been configured with to allow user to access its shares.
Try filling in the information on the Router's web gui for CIF and see how that goes.
I don't think CIF cares if the other machine is using NTFS. In fact it looks like it was built to login to windows machines if you read the fields on the WebGui.
I did a factory reset to undo anything I might have done wrong. After that I enabled CIF on the GUI but it didn't mount either. Any way to troubleshoot this? Should it automount or do I have to send a mount command?
Here are a few facts I think are worth mentioning:
- I can access the drive on my computer using its IP address and username/password. No problem here.
- Seagete uses directories with spaces on the name. Is that a problem? Can I mount the root drive directly?
- Do I have to enable anything else on the router? Samba?
- There is a field for a script on the CIF configuration. Is this mandatory? I didn't put anything there...
As you can see I'm not a pro on any of this, so I apologize for my noobness
Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Sat Feb 11, 2012 14:05 Post subject:
BrazilRoute wrote:
@zoomlink
I did a factory reset to undo anything I might have done wrong. After that I enabled CIF on the GUI but it didn't mount either. Any way to troubleshoot this? Should it automount or do I have to send a mount command?
Here are a few facts I think are worth mentioning:
- I can access the drive on my computer using its IP address and username/password. No problem here.
- Seagete uses directories with spaces on the name. Is that a problem? Can I mount the root drive directly?
- Do I have to enable anything else on the router? Samba?
- There is a field for a script on the CIF configuration. Is this mandatory? I didn't put anything there...
As you can see I'm not a pro on any of this, so I apologize for my noobness
Thanks!
While I have not set up CIF on my router (I have set up an external /opt and /jffs), I do know this much. If you had to manually mounting something to get CIF working, then you will have to do that manual "something" to keep it working at boot time. If there was some automation by DD-WRT going on, then that "automation" should continue to work at boot time. _________________ E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]
Try Dropbox for syncing files - get 2.5gb online for free by signing up.
Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.