No, Admin cannot see your identity while using a VPN.
No, Admin cannot see your identity while using a VPN.
Up until now, I thought only certain ports were safe for using VPNs, but I didn’t realize DPI could identify VPN traffic. Since the data is encrypted, it appears just like any normal site.
But how exactly? With our Netflow system it can identify VPN traffic when it connects via a recognized port to a VPN provider, yet such traffic remains the same as regular encrypted data.
I need to explain that for established VPN services it's relatively straightforward, but for limited or unfamiliar usage it becomes significantly more challenging to detect. Traffic analysis might offer some clues, though you can always find ways around it if you persist. Generally, if all VPNs are blocked, encrypted traffic will be the only one affected and specific exceptions will remain. Still, circumvention is possible, especially with certain tools available, making it harder to evade when patterns are known.
Linus mentioned on WANshow about his kids attempting to access pornography. He plans to monitor their computers and, if they try using a VPN, he intends to block them. He believes it’s quite simple to detect VPN activity. If Linus can do it, I’m confident a skilled network administrator could track you down without physically locating you. He thinks your account with the school would help identify you, allowing them to restrict access without needing to search for you.
It seems you're focusing on understanding the underlying patterns of a VPN. The idea that all traffic from a MAC address goes to a single IP is a common observation.
Earlier we mentioned that unless it connects through a shared port with a VPN service...it's quite challenging to locate this traffic. The data flows at the packet level just like when you visit your bank or YouTube.
Yep, I'm not fully familiar with all the detailed analysis for this, but when there are firewalls that spot and stop traffic using recognized malware patterns—even without knowing the exact version or encryption—the idea makes sense. It's not flawless, but it's fascinating. By examining the packets, headers, sending frequency, payload size, and other visible details, you can still gather clues about what’s happening, even if the actual data isn’t clear.
Check out Cisco's recent Assurance and Intent networking solutions. I often want to dive deeper, but time runs fast. I watched a demo where they showcased the DNA Center for Catalyst 9000 switches, added Alexa integration for entertainment, and quickly blocked infected devices while sending them to a patch server. The cloud-based approach makes data collection and analysis seamless—still impressive to see it in practice.
you can identify recognized VPN services and their ports, and once you start custom actions it becomes very tough to distinguish VPN traffic from HTTPS or SSH usage. therefore, if you launch a server in AWS and configure a VPN setup, there’s a high chance you’ll receive an IP address that hasn’t been used as a VPN before, which should work fine.