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.
The problem is that I haven't been able to get it working either manually or automatically. I don't mind doing it manually if I have to, but at this point I'm not sure this is even possible.
Also, the reason I was trying to use CIF was to follow zoomlink's suggestion. I'll be glad to try anything else... The main purpose here is to get the miniDLNA to map the drive correctly. Any ideas?
Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Mon Feb 13, 2012 16:46 Post subject:
BrazilRoute wrote:
The problem is that I haven't been able to get it working either manually or automatically. I don't mind doing it manually if I have to, but at this point I'm not sure this is even possible.
It is possible, although I myself have not tried these instructions. There is more information about it in the wiki under this article: http://www.dd-wrt.com/wiki/index.php/JFFS_File_System. Near the bottom it explains on how to use CIF. That is the best I can do for now. _________________ 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.
It is possible, although I myself have not tried these instructions. There is more information about it in the wiki under this article: http://www.dd-wrt.com/wiki/index.php/JFFS_File_System. Near the bottom it explains on how to use CIF. That is the best I can do for now.
I read that but it starts from the CIF partition already mounted...
Posted: Sat Jun 09, 2012 20:38 Post subject: So... any news?!
Hey People!
I have the same E3000 and probably the same problems : the lack on DLNA servers.
The provided DLNA servers on optware are not working using K2.6.
And as I understand we can not use the K2.4 for E3000 as there were no drivers supported by the manufacturer for K2.4.
So the only solution is using the KONG build or the Tomatousb build.
I tried the lates KONG build. It works great!
Just I have problems with miniDLNA. It sometime hangs and rescan the folders everytime you start. Also I would like to disable the album arts in the files. The rescan is a problem as there are about 34k files in 1.8k folders. :-O At the moment I try different thinks to let it work and find out why it hangs using the debug mode.
So my question is : Does anybody know a way to use some of the other DLNA servers? Are there any plans to make them working on K2.6 or are there maybe included in the KONG or Tomato builds?
At the end I wanted to thank everybody who provided the information here and Kong for the great build/work he does!
Mediaservers and other external apps, that need to query the network interface only work under dd-wrt if they have been build with dd-wrt toolchain. DD-WRT extends ethernet interface structures. This is why in general dd-wrt is not compatible with external package repositories. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Joined: 25 Mar 2012 Posts: 104 Location: In a van down by the river.
Posted: Thu Apr 04, 2013 16:17 Post subject:
<Kong> wrote:
Mediaservers and other external apps, that need to query the network interface only work under dd-wrt if they have been build with dd-wrt toolchain. DD-WRT extends ethernet interface structures. This is why in general dd-wrt is not compatible with external package repositories.
It was working with Build Kong 19545, and has recently stopped working on all versions past that. Is there no way to implement a fix for this? _________________ -I Am The Uberhuman Mutant
Mediaservers and other external apps, that need to query the network interface only work under dd-wrt if they have been build with dd-wrt toolchain. DD-WRT extends ethernet interface structures. This is why in general dd-wrt is not compatible with external package repositories.
It was working with Build Kong 19545, and has recently stopped working on all versions past that. Is there no way to implement a fix for this?
I was planning to install the Kong mod on my ASUS RT-N16 router.
From what you say, MiniDLNA will not work on any Kong build after 19545. Is that right? So, I have to install that 19545 build?
Thanks!
It was working with Build Kong 19545, and has recently stopped working on all versions past that. Is there no way to implement a fix for this?
I was planning to install the Kong mod on my ASUS RT-N16 router.
From what you say, MiniDLNA will not work on any Kong build after 19545. Is that right? So, I have to install that 19545 build?
Thanks!
Technically, all kingkong builds have working miniDLNA. Some may have problems with more than one media server, this happens especially on bridged routers (a question of igmp routing). _________________ 2 times APU2 Opnsense 21.1 with Sensei
2 times RT-AC56U running DD-WRT 45493 (one as Gateway, the other as AP, both bridged with LAN cable)
3 times Asus RT-N16 shelved
E4200 V1 running freshtomato 2020.8 (bridged with LAN cable)
3 times Linksys WRT610N V2 converted to E3000 and 1 original E3000 running freshtomato 2020.8 (bridged with LAN cable)