Just wondering if anybody else saw the problem and how to resolve it.
Installed latest Kong Mod on a 3500L and all worked fine. tried a little ipkg and installed a few packages.
I opened https for remote management. today is the first time I connect it remotely. It worked fine for a while and then stop responding.
I was able to ssh into the box try kill httpd and restart "httpd -S" but it didn't help.
Are you using the openvpn build?
Did you enabled proxy in transparent mode?
What output do you get when running:
ls -la /jffs/etc/config/*.web* /opt/etc/config/*.web*
Thanks for the reply.
After restarting httpd a couple times and so far it seems to be working. so it could be a temp network hiccup.
I am using openvpn build and didn't touch any proxy setting.
I have been running tomato for a long time on linksys 54gl. So far dd-wrt seems to be working fine on 3500L. 64M ram is really nice compare with 16m on linksys.
only thing I missing on tomato is the bandwidth history graph (day, week)and qos.
the problem is still there. Looks like this only happen when I access from Internet, not from internal.
netstat -atn shows queues on port 443 and stuck there for a very long time, and the web interface just stop responding
root@ngear:/# netstat -ant|grep 443
tcp 10 0 0.0.0.0:443 0.0.0.0:* LISTEN
tcp 121 0 192.168.111.3:443 206.16.x.x:35605 CLOSE_WAIT
tcp 121 0 192.168.111.3:443 206.16.x.x:54942 CLOSE_WAIT
tcp 121 0 192.168.111.3:443 206.16.x.x:34166 CLOSE_WAIT
tcp 0 12500 192.168.111.3:443 206.16.x.x:5054 ESTABLISHED
tcp 121 0 192.168.111.3:443 206.16.x.x:44638 CLOSE_WAIT
tcp 120 0 192.168.111.3:443 206.16.x.x:26497 ESTABLISHED
tcp 121 0 192.168.111.3:443 206.16.x.x:47287 CLOSE_WAIT
tcp 24 0 192.168.111.3:443 192.16.x.x:3382 CLOSE_WAIT
tcp 120 0 192.168.111.3:443 206.16.x.x:27706 ESTABLISHED
tcp 121 0 192.168.111.3:443 206.16.x.x:30028 CLOSE_WAIT
tcp 121 0 192.168.111.3:443 206.16.x.x:39888 CLOSE_WAIT
tcp 121 0 192.168.111.3:443 206.16.x.x:6002 CLOSE_WAIT