Hey K, What RouterOS version are you using? Also, what rules have you applied? If there is a very long delay and then a failure you should verify that the rules you wrote are proper to your environment. You should route packets based on connection marks and mark only new connections from LAN IP addresses and only on the LAN interface. As I showed in the demo video it’s very simple to implement. Let me know if you are still having issues. Eliezer ---- Eliezer Croitoru NgTech, Tech Support Mobile: +972-5-28704261 Email: ngtech1ltd@xxxxxxxxx My-Tube: https://tube.ngtech.co.il/ From: M K <mohammed.khallaf@xxxxxxxxx> Thank you for your quick reply. The text-drawing actually changed with different font; the squid server is effectively connected to MikroTik router, not the same physical link as the client. The MikroTik router sits between the client and squid server. That said, I can confirm that the MikroTik router is effectively able to route/DNat client packets going to ports 80 and 443 to squid server. Depending on router rules be it route or dnat, the client browser effectively displays the error page of squid, or goes into a very long delay then failure. I will retry and let you know. K On Wed, Aug 10, 2022, 10:08 <ngtech1ltd@xxxxxxxxx> wrote:
|
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
