So, I have 2 clients and both of them using RB433 (v 4.x), but i got report that they experience slow internet connection, for example: when their employees open a website, most of times, it just loading for moments and then connection time out. Same problem while sending email too (using SMTP).

But, when i disable the MikroTik internal proxy and the NAT to Proxy. Then everything just fine. I try to keep disable the rule for "NAT to Proxy" and then enable again the MikroTik Proxy, it getting slow again.
So i think this because MikroTik internal Proxy!

So do you have any sugestion for this problem? and have you fix it?

Thanks,
Yudi


Notes: below is example of ping result when the proxy is enabled (too many request timed out):
ping www.google.com -t

Pinging www.l.google.com [209.85.175.99] with 32 bytes of data:

Reply from 209.85.175.99: bytes=32 time=398ms TTL=53
Request timed out.
Request timed out.
Reply from 209.85.175.99: bytes=32 time=344ms TTL=53
Request timed out.
Reply from 209.85.175.99: bytes=32 time=570ms TTL=53
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 209.85.175.99: bytes=32 time=236ms TTL=54
Request timed out.
Reply from 209.85.175.99: bytes=32 time=475ms TTL=53
Reply from 209.85.175.99: bytes=32 time=269ms TTL=53
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 209.85.175.99: bytes=32 time=402ms TTL=53
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 209.85.175.99: bytes=32 time=431ms TTL=53
Reply from 209.85.175.99: bytes=32 time=242ms TTL=54
Reply from 209.85.175.99: bytes=32 time=387ms TTL=53
Reply from 209.85.175.99: bytes=32 time=270ms TTL=54
Request timed out.
Reply from 209.85.175.99: bytes=32 time=258ms TTL=54
Reply from 209.85.175.99: bytes=32 time=390ms TTL=53
Reply from 209.85.175.99: bytes=32 time=432ms TTL=53
Reply from 209.85.175.99: bytes=32 time=381ms TTL=53
Request timed out.
Reply from 209.85.175.99: bytes=32 time=205ms TTL=54
Reply from 209.85.175.99: bytes=32 time=303ms TTL=53
Request timed out.
Reply from 209.85.175.99: bytes=32 time=385ms TTL=53
Request timed out.
Request timed out.
Request timed out.
Reply from 209.85.175.99: bytes=32 time=348ms TTL=53
Request timed out.
Reply from 209.85.175.99: bytes=32 time=436ms TTL=53
Request timed out.
Reply from 209.85.175.99: bytes=32 time=412ms TTL=53
Reply from 209.85.175.99: bytes=32 time=184ms TTL=54
Reply from 209.85.175.99: bytes=32 time=401ms TTL=53
Request timed out.
Reply from 209.85.175.99: bytes=32 time=441ms TTL=53
Request timed out.
Reply from 209.85.175.99: bytes=32 time=406ms TTL=53
Reply from 209.85.175.99: bytes=32 time=247ms TTL=54
Request timed out.
Reply from 209.85.175.99: bytes=32 time=284ms TTL=53
Request timed out.
Reply from 209.85.175.99: bytes=32 time=389ms TTL=53
Request timed out.

Ping statistics for 209.85.175.99:
Packets: Sent = 60, Received = 28, Lost = 32 (53% loss),
Approximate round trip times in milli-seconds:
Minimum = 184ms, Maximum = 570ms, Average = 354ms
Control-C
^C

come on? no help around here? because i already have 2 customers experience same problem..

come on? no help around here? because i already have 2 customers experience same problem..

my suggestion setup a transparent squid proxy.

If you are running ros 5 please confirm the CPU readings with Profiler, I am running a RB750G as a proxy i dont have any trouble, i am unable to find the ralationship between the ICMP times that increase while using the Proxy since they are completely unrelated?

U can have a look at the "serialize connection" option in the proxy, but that is related to the way the proxy handles http traffic, can you please show your Nat rule, and in addition show ping results where the proxy is disabled?

proxy can't affect ping times, is only affects web traffic. maybe you have some other bad config related to proxy, for example NAT?