3 ms·
>Reading through, this outlines a way to avoid using deep packet inspection by using Squid and Tomcat instead. Huh? It sure seems to be using deep packet inspe
by Buge 9y ago
>Reading through, this outlines a way to avoid using deep packet inspection by using Squid and Tomcat instead.
Huh? It sure seems to be using deep packet inspection to me. If it's looking at the data section of your packet, that's deep packet inspection. And Squid and Tomcat do that. They're not just inspecting the packets, they're altering them, creating new packets, splitting packets, etc. The "RFC" seems to be outright lying by claiming they don't do DPI.
- exikyut 9y agoHmmmm. > Pre-established TCP sessions on port 80 are identified by the SMB and forwarded with no impact. (SMB = Session Management Broker) How does the system identify a "pre-established session"? This seems to corroborate what you're saying
- Dylan16807 9y agoThat part just requires looking at the TCP header. So I guess the answer is "no deep packet inspection until it picks a connection to inject, and then it inspects everything in that connection". Which simplifies to "yes deep packet inspection".