you can configure MWG to use Squid as a next-hop proxy. An example rule set is part of the product.
MWG cannot read exceptions from a PAC file, you probably have to build the exceptions within MWG in rules, such as:
URL.Destination.IP is in range 192.168.0.0/24 Stop Rule Set
URL.Destination.IP is in range 10.0.0.0/8 Stop Rule Set
Always Stop Rule Set Enable Next-Hop Proxy(<Squid>)
Such a rule set would tell MWG to directly talk to 192.168.0.0/24 and 10.0.0.0/8 networks directly, while for all other destinations Squid will be used as a next-hop proxy.
Thank you Andre for the extremely quick reply, that was most helpful. I'll try doing what you said, and if I run into trouble, I will post again.
1 of 1 people found this helpful
Instead of separate rules for every IP-Range, it could be faster to either have IP Range List, or maybe it would be also easier to put all IP Ranges into text file, and host it somewhere outside of MWG & access it via External Lists...
P.S. another idea - extract IP ranges automatically from proxy.pac by providing filtering regex :-)
Thing is, I can't use IP ranges. To be more specific, I want to route traffic of certain domains through Squid and the rest needs to bypass Squid. I think the filtering regex idea sounds good.
Actually the IP Range was just an example. You have several hundrets of properties you can use to decide whether Squid should be used or not.