I've got an Asus wl500gp with Kamikaze 7.09 installed that freezes once every 4-10 hours and I am trying to figure out why. Here's a timeline of my meddling:

1. Flashed the firmware, installed Kamikaze 7.09 without any problems. I then proceeded to the installation of X-Wrt which went smoothly. After that I connected two computers to the router (one wired and one wireless).
2. Due to lack of time the router remained like that for one week without any modifications to the firmware. I had an uptime of 7 days, so there was no problem with the config.
3. A few days ago I installed an external usb 2.0 hard drive on the router using this HOWTO. No problems whatsoever, I added the automount to the router's startup and everything was going great.
4. I then installed SAMBA using ipkg and created my own cfg file.
5. I installed vsftpd using ipkg and did not edit the cfg file.

The SAMBA and vsftpd install were done pretty much one after another.

Now, the router freezes once every few hours and I can't figure out what the problem is. The network drops, the router does not respond to ping - the only solution is to pull the power cord to reset it.

I don't realize what's going on. I don't think it can overheat since there is plenty of free ram and processor left. Any ideas?

Attach a serial console so that you can see what the kernel spits out before dying on you.
Maybe remote syslog can help too.

Do you use the original broadcom wireless nic? It seems that there is a problem with the broadcom nic or the driver when copying large amounts over it, see that post.

KanjiMonster,

I've got exactly the same problem since updating from Kamikaze 7.07 to 7.09.
Unfortunately your link to the particular post is not working - could you please repost it?

Thanks!

Sorry, somewhere I forgot to put the link in, it's this post (this time I'll preview). Essentially it's replacing the included broadcom nic with an atheros based "fixed" it.

I figured it out, apparently some SAMBA parameters caused the router to freeze, i removed them and it works just fine now

thanks for the help

(Last edited by ghostwriter on 23 Jan 2008, 22:43)

Could you post which parameters these were? Might be interesting for others having the same problem.

Install samba3 from optware

I'm not sure which one was causing the problem. I tried removing several parameters in the global section on smb.conf but I am not sure which one did the trick - my money is on the socket options

socket options = TCP_NODELAY IPTOS_LOWDELAY SO_RCVBUF=65536 SO_SNDBUF=65536

Anyway, I encountered the problem only when I copied large files (>1GB) over the wireless network. Thanks for the help.

(Last edited by ghostwriter on 26 Jan 2008, 12:53)

Hi ghostwriter. I'm having the same issue. You mind posting your smb.conf?