Want to understand the "random reboot" issue you have been facing with EAP2. Please provide some more details around what you have experienced. Thank you very much for your feedback.
The next EAP - EAP3 - has been put to final test in our own production systems. In a positive path - it usually go through a week or 10 days of soaking before we release it to our community contributors. Stay tuned.
Thanks PMParth. I hope you fix all the issues with DPI as some users are not able to use it as expected. I am one of the user.
FYI, I opened the thread on Catalina OS and worked with some devs to understand and share logs why the CAA does not work. Please keep going and improve performance on UI and web experience surfing.
At this point, I am not seeing any reason to run DPI instead of proxy. Don't want this thread to turn into DPI problems since we have other threads for that but proxy works so much better than DPI that it is not worth the headache even in a test environment. Also separate exception lists are just more overhead for admin to keep up with. I personally wouldn't use DPI until DPI Performance is clearly better than proxy and the exceptions lists etc. are more streamlined throughout the system.
I agree with Luk that the next release should focus more on polishing the system and eventually revisiting a GUI redesign in the near future where its easier to manage the workflow of the whole system instead of other new shiny functions that are not fully integrated yet.
At this point, I am not seeing any reason to run DPI instead of proxy. Don't want this thread to turn into DPI problems since we have other threads for that but proxy works so much better than DPI that it is not worth the headache even in a test environment. Also separate exception lists are just more overhead for admin to keep up with. I personally wouldn't use DPI until DPI Performance is clearly better than proxy and the exceptions lists etc. are more streamlined throughout the system.
