Transparent Proxy in MT 3.14

Can someone tell me how to f…k set up transparent proxy on MT 3.14 ??? Firewall rule works fine in redirect, proxy seems to work fine too , bo all i se in proxy log is : not fount : 1275 , hits: 0…What’s with this ???

Thanks for answer.

But… with so little informations HOW we can help you?
Please post more informations,data etc.
More informations = MORE help you receive
Regards
Alex

enabled: yes 
src-address: 0.0.0.0 
port: 8080 
parent-proxy: 0.0.0.0 
parent-proxy-port: 0 
cache-drive: system 
cache-administrator: "webmaster" 
max-cache-size: unlimited 
cache-on-disk: yes 
max-client-connections: 600 
max-server-connections: 600 
max-fresh-time: 3d 
serialize-connections: no 
always-from-cache: yes 
cache-hit-dscp: 4

Proxy is running.

Now rule in firewall:

/ip firewall nat add chain=dstnat action=redirect to-ports=8080 src-address=192.168.xx.xx/24 dst-port=80 protocol=tcp

this works fine in 2.9.xx, but in 3.14 not.
Rules in web-proxy access are added. I se many requests but 0 hits, and pages don’t display.

just try… /ip firewall nat add chain=srcnat out-interface=your_uplink action=masquerade

Masquerade to transparent proxy ??? you kidding…
I want to make rule that all my clients opening some websites , will be redirected to proxy server on my MT , is that so hard ???

In 2.9 there were 2 web proxies:

  • “Proxy”: typically only available to hotspot users.
  • “Web-Proxy”: to use at your own discretion (just enable it on default port 3128, enable the transparent proxy option and manually insert rules in nat->dst-nat for protocl=tcp dst-port=80 with action=redirect to-port=3128).

Some differences:

  • Web-proxy had more options and could have a cache.
  • “Proxy” was associated to hotspot users by default.
  • You could configure “proxy” to use “web-proxy” as a parent proxy.
  • They used different internal ports.

No it’s not hard at all. The rule that Chupaka posted is the masquerade rule that will need to be in place for the redirect to work in the first place. Client’s default route is the Mikrotik router, Mikrotik router does NAT(masquerade), any outgoing connection destined for port 80 gets redirected to port 8080 on Mikrotik router.

Did you tried? Is it so hard? If you do not need any help - you are not welcome here

Try this rule - web-proxy in v3.x had a bug with src-address of proxy connections to remote websites