Page 1 of 1

Web Proxy 6.28 ROS @ RB751U-2HnD

Posted: Tue Apr 28, 2015 2:47 pm
by vpritiskovic
Hi!

Boards:
HW1: ROS 6.28@RB751G-2HnD
HW2: ROS 6.28@RB751U-2HnD

I followed the http://wiki.mikrotik.com/wiki/Manual:IP ... on_example and prepared script to apply both on HW1&HW2. I have successfully configured transparent proxy on my HW1 device like in guide and it is working ok (I can see file list stored in cache and I see cache hits count). So far so good. Now, I have trouble with HW2 - I have applied same script to HW2 and proxy is working but I can't see any file stored in cache??

Can one help me out - same ROS version and config HW2 does not work as HW1.

Thanks!

Re: Web Proxy 6.28 ROS @ RB751U-2HnD

Posted: Tue Apr 28, 2015 7:44 pm
by DigitalBlueBiz
Hi vpritiskovic,
It's almost impossible that same configuration applied on 2 different boxes bring to 2 different results.
Can you please paste your script? Perhaps you have some nasty error there that you didn't spot.

Re: Web Proxy 6.28 ROS @ RB751U-2HnD

Posted: Tue Apr 28, 2015 8:39 pm
by vpritiskovic
Hi there, thanks for replaying!

I have searched and found the reason for this behaviour! While RB751G-2HnD has 64MB of RAM the RB751U-2HnD has only 32MB of RAM http://routerboard.com/RB751U-2HnD
And of course the ROS feature:
What's new in 6.23 (2014-Dec-04 14:46):

*) pptp - fixed problem where tunnel stopped transmitting packets under heavy load;
*) web proxy - caching in RAM for boards with 32MB or less RAM will not cache any content;
...

Re: Web Proxy 6.28 ROS @ RB751U-2HnD

Posted: Tue Apr 28, 2015 9:13 pm
by DigitalBlueBiz
vpritiskovic,
I have searched and found the reason for this behaviour! While RB751G-2HnD has 64MB of RAM the RB751U-2HnD has only 32MB of RAM http://routerboard.com/RB751U-2HnD
And of course the ROS feature:
What's new in 6.23 (2014-Dec-04 14:46):

*) pptp - fixed problem where tunnel stopped transmitting packets under heavy load;
*) web proxy - caching in RAM for boards with 32MB or less RAM will not cache any content;
...
IMHO this is not the solution to your issue, when a changelog displays entries like this, means that Mikrotik FIXED that issue. In this case they fixed the issue about caching in 6.23 so in 6.28 you should see something cached unless you spotted a regression.