I was using MikroTIk 2.7 as a transparent proxy, with transparent proxy to point to my FreeBSD proxy. All was working well, until i upgraded to 2.8.11. Now, with the parent proxy specified in the mikrotik, it will not work. Any ideas? Is this a bug?
It must be a config problem as we have 2.8.11 working as a transparent proxy which in turn directs traffic to a central filtering proxy.
Double check the firewall rules, making sure that the proxy has access to the parent.
I just checked and there are no firewall rules preventing access. Also, it was working fine in v 2.7, but after the upgrade to 2.8.11, it no longer works. Nothing was changed between the working point, and now besides the version upgrade.
You’re going to have to do a little testing…
-
Does the transparent proxy work without the parent set?
-
If yes, you need to check that Mikrotik has access to the
parent (go to 2a). If no goto step 3
2a. Double check the firewall rules (again!) Perhaps
change the input/output rules default to “accept” if your
box is on a LAN. Does it work now? If it does you need to
tweak the firewall rules.
2b. Double check that the parent proxy is still operational
2c. Perhaps re-enter the parent proxy settings.
2d. We’re not running windows, but have you tried a reboot?
- It seems the transparent proxy isn’t working at all. Double check
the dst-nat rule is redirecting TCP Port 80 to the correct local port
(default 3128).
Hope that helps a little. Its really a case of troubleshooting the issue.
The box I have 2.8.11 running on started out as 2.8.x box, so it is
possible that something nasty happens when you upgrade from 2.7.
-nathan
Thanks for you help…any other ideas you can think of? I am thinking it was a problem with the upgrade because we have nothing in place that should prevent this from working (as it did before the upgrade).