Avoid deep packet inspection by using alternative methods to analyze network traffic.
Avoid deep packet inspection by using alternative methods to analyze network traffic.
I’m facing a problem with my network that restricts me to only seven MAC addresses, each tied to a fixed IP. I attempted to expand the network using a budget Tplink router or Wi-Fi AP, but once the system identifies it as a router, it blocks internet access until it recognizes the change. Switching MAC addresses or hostnames didn’t help, suggesting packets are being checked for NAT. I bought a PC Engine APU2C2 to run pfSense and enable a VPN to hide traffic, aiming to reduce bandwidth usage (30-40Mbps on up to 100Mbps connections) and improve ping performance. Currently, I rely on PIA as my VPN provider.
You can try adjusting certain settings to improve performance. It's possible the PIA Servers are limiting speed. Since you invested £170 in the PFSense box, you'd prefer it to last longer rather than replace it soon. After moving in July, you won't need the MAC Address restriction anymore, so the VPN tunnel won't be necessary. Edited February 24, 2018 by MaroonLance Added second paragraph
You could simply ask the network administrator or your ISP to approve your router. Check if they are willing to do that first.
Your ISP doesn't permit firewalls or routers? That seems odd. If the virtual machines are behind the host, it's challenging to detect them as separate hosts. Yes, it's simpler to request permission than facing restrictions for being clever. Still, I don't understand how DPI relates, since packet inspection just identifies the data stream, not the host itself.