A few questions about this:
Must have slipped through the cracks.
Yes it's supported, albeit in a limited fashion. In a future release (soon, but no promises) SOCKS support including authentication will be built into the policy, currently the SOCKS proxy just proxies the traffic and any authentication or ACLs must be done via the socks config.
It does add load, but without knowing what protocols and amount there is no way to guess how much. In the current implementation, since we do not scan, the load will not be massive, but as I said, not enough info.
SOCKS runs on a different port, so the interface doesn't particularly matter.
There are a number of customers with this implemented, generally for very specific use cases (scp to partners or ftp) so feel free to use it if you have need.
--ChristopherMessage was edited by: cnewman on 10/4/13 2:12:30 PM CDT
That is excellent news, Christopher. Could you be just a tiny tad more specific in regards to what version we can expect this? Will this come in the 7.4 series or do we have to wait longer than that?
We are currently migrating away from a custom built SOCKS and WW6 infrastructure towards MWG7 and we need a replacement for our SOCKS gateway. So if you're looking for beta testers, I'd be happy to jump on the train.
I was at FOCUS last week and during the web gateway preso, this SOCKS coming into the MWG product itself thing was mentioned. In my notes I have that it'll probably be in 7.4.1 is the current plan. And that came with the usual caveats of no promises, etc.