Kong Mod Update build 17865: Update 11/13/11

49 posts / 0 new
Last post
Kong
Kong's picture
Kong Mod Update build 17865: Update 11/13/11

Here is a new build based on dd-wrt 17865.

Please Read: http://www.myopenrouter.com/article/23842/DD-WRT-Kong-Mod-Info/

Since more and more users want to support my work I have added my donate button at the router webinterface bottom. Up to now I didn't display the original dd-wrt donate button since I dislike to annoy users with that. Therefore, to hide my donate button, in case you find this annoying, logon to the router and disable the donation button:

nvram set donate=1

nvram commit

This will hide the donation button until you reset the router.

From now on you will be able to jump back to previous releases, checkout the new download location:-;

 

Update 11/13/2011:

New:

  • tcpdump added to kingkong build

Fixed:

  • fix segmentation faults(nslookup,openser...) roll back uclibc to last stable kong uclibc
  • fix console reboot command when shutdown script used

Update 11/12/2011:

Fixed:

  • ses button umount feature could lock up router

11/11/11:

New:

  • kernel USB_SERIAL_GENERIC enabled, support options when loading usb serial adapters (untested)

Fixed:

Known Bugs:

  • signal dropping over time with newd driver builds and some devices
  • wiviz not working with newd builds (driver problem)

Planned Features for next release:

  • add advanced optware package management system
  • include iptables-save

Wishlist:

  • short device links e.g. /dev/sda instead of /dev/scsi/host0/bus0/target0/lun0
  • inadyn with https support to support opendns updates

 

KongMod Downloads

zoomlink
zoomlink's picture
Kong:

Kong:

Thanks for the new load and also the easy to follow revision of builds with the new download site.

I just loaded the KingKong NewD load on my RT-N16.

All seems to be working ok except the pesky problems we always have with OTRW.

My vlighttpd service no longer works (this is the virtual hosting www service).

This is the message I am getting:
root@ROUTER:/opt/etc/wvpn# service vlighttpd start
Start service "vlighttpd" (/opt/etc/init.d/S80vlighttpd)
service: Start service: "vlighttpd" (/opt/etc/init.d/S80vlighttpd)
Starting web server: vlighttpd

/opt/sbin/lighttpd: symbol 'errno': can't handle reloc type 47

Do you have any idea what could be causing this? maybe I need to upgrade my lighttpd?

zoomlink
zoomlink's picture
Ok, I just updated lighttpd

Ok, I just updated lighttpd and nothing changed, still getting the same error and cannot start the virtual webserver.

Strangely the interfaces are up and running with the secondary IP.

Kong
Kong's picture
@zoomlink, that is because

@zoomlink, that is because lighttpd was compiled using a different library, if you have installed the uclibc that comes with these optware packages you should be able to preload the right libs in order to load lighttpd. You preload libs this way:

export LD_PRELOAD=/opt/lib/ld-uClibc-0.9.30.1.so:/opt/lib/libc.so.0

I just found a bug in my ses button umount, it can lock up the router under certain conditions. There will be fixed builds in a few hours

P.S. Did lighttpd work in my last builds? I can always revert to the previous libs again. Just wanted to see if the new uclibc is bugfree now, dd-wrts current uclibc is not.

zoomlink
zoomlink's picture
Ok, I presume I need to add

Ok, I presume I need to add this export statement to preload the libs that work on the actual optware script that calls up lighttpd?

And yes.. my lighttpd worked fine with your previous KingKong build.

zoomlink
zoomlink's picture
BTW: This is what I got when

BTW: This is what I got when I added that line to the begining of of the vlighttpd and lighttpd scripts.

Start service "vlighttpd" (/opt/etc/init.d/S80vlighttpd)
service: Start service: "vlighttpd" (/opt/etc/init.d/S80vlighttpd)
tr: can't load library '/opt/lib/ld-uClibc-0.9.30.1.so'
egrep: can't load library '/opt/lib/ld-uClibc-0.9.30.1.so'
/opt/bin/bash: can't load library '/opt/lib/ld-uClibc-0.9.30.1.so'

Kong
Kong's picture
zoomlink said: BTW: This is

zoomlink said: BTW: This is what I got when I added that line to the begining of of the vlighttpd and lighttpd scripts. Start service "vlighttpd" (/opt/etc/init.d/S80vlighttpd) service: Start service: "vlighttpd" (/opt/etc/init.d/S80vlighttpd) tr: can't load library '/opt/lib/ld-uClibc-0.9.30.1.so' egrep: can't load library '/opt/lib/ld-uClibc-0.9.30.1.so' /opt/bin/bash: can't load library '/opt/lib/ld-uClibc-0.9.30.1.so'

Ehm, the preload command was just a sample, you have to check /opt/lib/ for the names of your installed libs:-)

 

Lets see if some more people report problems with other apps. I intend to release the next build in a week or two, since proftpd released a security update. So if more people are affected I just include the old libs again.

zoomlink
zoomlink's picture
Kong said:

Kong said:

zoomlink said: BTW: This is what I got when I added that line to the begining of of the vlighttpd and lighttpd scripts. Start service "vlighttpd" (/opt/etc/init.d/S80vlighttpd) service: Start service: "vlighttpd" (/opt/etc/init.d/S80vlighttpd) tr: can't load library '/opt/lib/ld-uClibc-0.9.30.1.so' egrep: can't load library '/opt/lib/ld-uClibc-0.9.30.1.so' /opt/bin/bash: can't load library '/opt/lib/ld-uClibc-0.9.30.1.so'

Ehm, the preload command was just a sample, you have to check /opt/lib/ for the names of your installed libs:-) Lets see if some more people report problems with other apps. I intend to release the next build in a week or two, since proftpd released a security update. So if more people are affected I just include the old libs again.

Ehm, lol.. sorry.  I took your export command literally.  Is there a way to know what lib dependencies lighttpd has? it it is uclib, then I will look through the opt/libs and see what I find.

Thanks anyway... by the way, pls don't forget moving to the /dev/sda, sdb format instead of the long descriptors.

Kong
Kong's picture
zoomlink said:

zoomlink said:

Kong said:

zoomlink said: BTW: This is what I got when I added that line to the begining of of the vlighttpd and lighttpd scripts. Start service "vlighttpd" (/opt/etc/init.d/S80vlighttpd) service: Start service: "vlighttpd" (/opt/etc/init.d/S80vlighttpd) tr: can't load library '/opt/lib/ld-uClibc-0.9.30.1.so' egrep: can't load library '/opt/lib/ld-uClibc-0.9.30.1.so' /opt/bin/bash: can't load library '/opt/lib/ld-uClibc-0.9.30.1.so'

Ehm, the preload command was just a sample, you have to check /opt/lib/ for the names of your installed libs:-) Lets see if some more people report problems with other apps. I intend to release the next build in a week or two, since proftpd released a security update. So if more people are affected I just include the old libs again.

Ehm, lol.. sorry.  I took your export command literally.  Is there a way to know what lib dependencies lighttpd has? it it is uclib, then I will look through the opt/libs and see what I find. Thanks anyway... by the way, pls don't forget moving to the /dev/sda, sdb format instead of the long descriptors.

The ipkg package list you installed it from contains the Depends field which lists the dependencies.

zoomlink
zoomlink's picture
Ok.. I replaced your uclib

Ok.. I replaced your uclib with the one on the opt/lib directory and now I get the following error - different from the last one.
--
root@ROUTER:/opt/etc/init.d# service vlighttpd
web server: lighttpd is not running
root@ROUTER:/opt/etc/init.d# service vlighttpd start
Start service "vlighttpd" (/opt/etc/init.d/S80vlighttpd)
service: Start service: "vlighttpd" (/opt/etc/init.d/S80vlighttpd)
Starting web server: vlighttpd
mmap of a spare page failed!
--

Csimbi
Csimbi's picture
I am leaning towards

I am leaning towards switching from the official DD-WRT builds to the Kong builds due to the simple fact that the wireless is borked on last few the DD-WRT builds and it does not seem like they're going to fix it any soon - while I heard it works fine on the Kong builds.

What's the official homepage for Kong builds?
What's the default admin username and password for Kong builds?
Is there a simple way of restoring the DD-WRT config in the Kong builds? (So I would not have to spend hours.)

Thanks.

Kong
Kong's picture
 

 

Csimbi said: I am leaning towards switching from the official DD-WRT builds to the Kong builds due to the simple fact that the wireless is borked on last few the DD-WRT builds and it does not seem like they're going to fix it any soon - while I heard it works fine on the Kong builds. What's the official homepage for Kong builds? What's the default admin username and password for Kong builds? Is there a simple way of restoring the DD-WRT config in the Kong builds? (So I would not have to spend hours.) Thanks.

 

I don't have an official homepage. I just have a place where I can put my files, see Download link.

Default password etc is the same. About differences between my and official builds, see Info link. Unless you come from a really old official build there is not need to reset, you can just flash my build and your are good to go. You can also return to official builds without any problem.

Csimbi
Csimbi's picture
Ok, I bookmarked the download

Ok, I bookmarked the download link.

I took a leap of faith and flashed it.
Came back up just fine, settings seems to have been preserved completely.
The UI seems to be nearly identical to the official DD-WRT build.
I will have to wait with the wireless because it takes a day for it to die after flashing.
So far, so good, thanks!

BTW, any chance to prefix the filenames with "dd-wrt.kong."?

Do you accept feature requests?

Kong
Kong's picture
OK the new uclibc causes the

OK the new uclibc causes the same problems you currently see with official dd-wrt builds, so I'll switch back to my last stable uclibc. This should fix segmentation faults you currently see with nslookup, milkfish ...

Watch out for new builds soon.

Csimbi
Csimbi's picture
Ok, will keep an eye open.

Ok, will keep an eye open.
Any chance to sort the static lease list by host name or IP address, and put a checkmark next to them so I could select which one to remove (instead of the last one)?
Thanks.

Kong
Kong's picture
billypg said: Automount by

billypg said: Automount by UUID is still not working for me. As a workaround i thought of running the following command on startup to mount my drive to /jffs (of course this would only work if the drive is powered on when i boot): ntfs-3g `blkid | grep 884E79544E793BCE | cut -d : -f 1` /jffs It complains about the fuse module not being loaded, but i realized that the fuse module cannot be loaded if i disable automount. Even though there is no error with insmod the module still doesn't load. I had to enable automount and then the command works, but now minidlna doesn't start on boot (maybe it's not seeing /jffs by the time it tries to start) ... so frustrating :[ automount was working for me on the Oct 23 release.

first do:

insmod /lib/modules/2.6.24.111/kernel/fs/fuse/fuse.ko

Once I have the time to test with an ntfs drive I'll see if your problem with the uuid not showing up in diskpart output also applies to me. In the meanwhile you can see if manually loading works.

mrg666
mrg666's picture
I have tried the E3000 builds

I have tried the E3000 builds on E2000. But the E3000 build bricks the E2000. Checking on the serial console shows that the boot process gets stuck on the initialization of USB ports which does not exist on E2000. Kong, may I kindly ask if you could add a E2000 build or just make it possible to boot with the E3000 build please?

Kong
Kong's picture
wabe said: Have commented

wabe said: Have commented about some inconsistencies in Cron and jobs entered in the webgui. Have investigated this a bit further and found: - Cron jobs run fine after a 'cold boot' i.e by pulling power and then power on - a warm reboot i.e a cron job or reboot from command line breaks the jobs - A manual 'stopservice cron && startservice cron' from command line restores functionality Can anyone else verify this behavior? The strange thing is that only cron jobs entered from the webgui seems to be affected

Did you connect a usb drive while testing? As I didn't want to modify too much in sysinit I didn't rearrange cron startup, so I just added a start/stop in the mount logic as this is needed anyways e.g. if you want to run scripts from external media.With usb attached I'd think this problem should not occur.

So without a drive connected dd-wrt still has an issue with the timing (thread that creates the cron jobs  and the one who starts cron run around the same time) and that does not depend on cold or warm boot it can happen at anytime and it also depends on your configuration. If you are lucky it doesn't happen with 10 boots, if you are unlucky it happens with every boot:-)

mbo69
mbo69's picture
Hi,

Hi,
i am using the KingKong build from 13.11.2011 on an Asus RT-N16. Unfortunately I have wireless problems. After a day (or sometimes even quicker) the wireless transmission decreases to lower than 20 MBit/s. Normally it is about 78 MBit/s. With an older kingkong build 27.10.2011 I made similar experiences, but the time for slowing down was longer AND I was always able to resume "normal" wireless speed by clicking "Apply Settings" on the Wireless/Basic Setup page. I use the kingkong build without newd in the name. Is the newer wireless driver in this version as well ?
Currently after pressing "apply Settings" on Wireless/Basic Setup page my wireless repeater cannot be reached any more.
I have to reboot the router to fix this problem.

Kong
Kong's picture
mbo69 said: Hi, i am using

mbo69 said: Hi, i am using the KingKong build from 13.11.2011 on an Asus RT-N16. Unfortunately I have wireless problems. After a day (or sometimes even quicker) the wireless transmission decreases to lower than 20 MBit/s. Normally it is about 78 MBit/s. With an older kingkong build 27.10.2011 I made similar experiences, but the time for slowing down was longer AND I was always able to resume "normal" wireless speed by clicking "Apply Settings" on the Wireless/Basic Setup page. I use the kingkong build without newd in the name. Is the newer wireless driver in this version as well ? Currently after pressing "apply Settings" on Wireless/Basic Setup page my wireless repeater cannot be reached any more. I have to reboot the router to fix this problem.

What TX power did you set?

If you apply settings at the wireless tab, then you have to wait quite some time this triggers a few things, interfaces up down stopping/starting services. But I'll test this, just to make sure there is no bug.

mbo69
mbo69's picture
@Kong, the TX Power is

@Kong, the TX Power is unchanged (17 mW). I waited for more than 10 minutes and the repeater bridge was still not reachabele, but I could see it in the site survey.
@Wabe: I had smaller problem with the old kingkong build from 27.10.2011 as well.

Kong
Kong's picture
Just tested Apply Settings on

Just tested Apply Settings on wireless page, didn't see a problem. Next time you try, logon to the router and check messages with:

tail -f /var/log/messages

maybe something interesting comes up. You should logon via a cable connected box though, since apply settings will disable/enable wireless.

Teknowiz
Teknowiz's picture
Thanks for your hard work

Thanks for your hard work Kong. If you have some time, could you please look into the following two question.

1) Does the Newd King Kong build for Asus RT-N16 have the wi-fi fix recently posted on DD-WRT SVN?

http://svn.dd-wrt.com/ticket/2251

2) The bandwidth monitor script which is part of the MyPage script seems to no longer functions as shown below on the new builds. Any ideas what could be causing this issue?

http://www.dd-wrt.com/phpBB2/download.php?id=17134

Kong
Kong's picture
1)No as this fix doesn't fix

1)No as this fix doesn't fix the signal dropping problem in newd. The RT-N16 works fine with the older driver.

2)Just the bandwidth? Did you fix your mypage scripts, as noted here:

http://www.myopenrouter.com/forum/thread/31294/Kong-Mod-Update-build-176...

Dark_Shadow
Dark_Shadow's picture
@Teknowiz

@Teknowiz

You should download my newest version of my page.

http://www.dd-wrt.com/phpBB2/viewtopic.php?t=79941

Then install BWMon as per the thread

http://www.dd-wrt.com/phpBB2/viewtopic.php?t=81432

once bwmon is running properly it will show automatically in mypage.

eTaurus
eTaurus's picture
Hi Kong,tried to use MiniDLNA

Hi Kong,
tried to use MiniDLNA again after some time. I configured it in the same way in the GUI (as I can recall) as I did last time. But now when I issue

/usr/sbin/minidlna -R -f /tmp/minidlna.conf

I get this:

Media directory not accessible! [/tmp/mnt/disc-part3/Musik/]
root@DD-WRT:/#

What's wrong? Is it allowed to use a directory that is already shared via Samba?

As I used MiniDLNA last time it changed all characters like ö,ä,ü,á to "_" or other incomprehensible combinations of characters. Is this a known problem?

eTaurus

eTaurus
eTaurus's picture
wabe said: Etaurus: try to

wabe said: Etaurus: try to mount to /mnt instead of /tmp/mnt

Thanks a lot!!!

Csimbi
Csimbi's picture
So Kong,

So Kong,
it's been over a week.
When's the next build due? ;-)

Kong
Kong's picture
Once I'm done with replacing

Once I'm done with replacing the broken optware support in dd-wrt.

This involves replacing the discontinued broken ipkg with opkg + compiling and setting up a repository with dd-wrt compatible optware packages, since all optware packages that query network interfaces don't work with dd-wrt.

zoomlink
zoomlink's picture
Kong said: Once I'm done with

Kong said: Once I'm done with replacing the broken optware support in dd-wrt. This involves replacing the discontinued broken ipkg with opkg + compiling and setting up a repository with dd-wrt compatible optware packages, since all optware packages that query network interfaces don't work with dd-wrt.

You are doing God's work there my man.  We thank you.

Csimbi
Csimbi's picture
zoomlink said:

zoomlink said:

Kong said: Once I'm done with replacing the broken optware support in dd-wrt. This involves replacing the discontinued broken ipkg with opkg + compiling and setting up a repository with dd-wrt compatible optware packages, since all optware packages that query network interfaces don't work with dd-wrt.

You are doing God's work there my man.  We thank you.

Indeed. Thank you.

Pages