Web Proxy causes router crash

Anyone know when V3.x will have a working web proxy package?

Currently on v3.1 on a PC, the Web Proxy crashes every so many hours (high usage I would guess). I set the number of users and connections upwards and downwards to no avail. I am unable to get a supout when it crashes - all I get is a kernel panic so no supout gets created.

This is just your everyday 1Ghz Pentium type machine with a 40Gb hard drive a couple of different 3Com nics, 512MB of ram. Nothing fancy…

I have not upgraded to v3.2 as of yet, I did not see where the web proxy issue has been addressed in the change log. If anyone has any info or has upgraded to v3.2 and your web proxy issues went away - I’d like to hear from you.

I’m using web-proxy on my router for 3.0, 3.1 and 3.2.
I do not see any reboots.
Try to generate support file after router was rebooted (desirable with 3.2 version).
Is your router working stable, when proxy is disabled on the router ?

I haven’t face any problem running ver 3 web proxy, and I’m sure it’s better than previous one. galaxynet I think you should check you hdd first, you can check your hdd with the MT OS > system check-disk then press Y, it’ll reboot your MT and check your hdd for few mins depand on your hdd. I hope it’ll fix your problem.

BTW I am having full support from my web proxy by downloading cache with pcq rules. It’s cool.

Thanks n regards

Upgrading to v3.2 tonight.

HD has been checked with the system check disk function…came out fine.

Web Proxy has been off for three days now and no issues with the PC running ROS v3.1

I will manually generate a supout file the next time it crashes after the proxy gets re-enabled under v3.2

Thom

Make sure its not a dual core processor or something like that with SMP turned on. This can cause this as well.

we use dual core processor with webproxy in a small wire network and there no any router crashes. at this moment.

Ok - Updated to 3.2, using system drive as proxy - crashes in less than 24 hours. Added new ‘secondary’ drive. Did format / check / started up Webproxy, has been up up for a few weeks now…

Thom