Sorry, i think i haven't explained it correctly. I've asked my coworkers - the guys that did it - regarding that issue, and they told me that this now only works when bridging is enabled. If you turn on bridging, you can set that checkbox. As long as bridging is off, the fully transparent mode cannot be enabled.
This has been decided by our Product Management team, and i have put this issue into Mantis and i am currently waiting for Feedback (see the betabot-post above, it states "BUG -> FEEDBACK/OPEN").
Please feel free to flame me if you don't like that decision. I'll take your input and let the product marketing guys know about it.
When they say you have to use bridging, it makes no sense, cause Full Transparent Web proxy is working when using web proxy profile. And why should I use a Bridge, when I want to use Web proxy, this makes absolutly no sense.
Astaro user since 2001 - Astaro/Sophos Partner since 2008
Hasn't this been like that since a couple of (stable) releases? This behaviour is not unique to the v8.2 Beta.
In my opinion, Full Transparent mode is dangerous, if enabled without knowledge about the consequences. There are only two different use cases - bridge mode and parent proxy where you want to see the original client IP for reporting - where this feature is useful.
I can live with the fact that you'll have to use the profiles to enable this feature for the 2nd use case - as it's rather specific. Also "full transparent" sounds more powerful and "correct" for not so experienced users - hence they'd enable it and generate a lot of support cases.
+1 for keeping it the way it is right now (but please don't disable the feature in the profiles!)
