If you want to get around region blocking, you also need to play with DNS resolution for the names used by the Netflix service. In fact, a rule targeting just those IPs is guarenteed to still end up with content coming from the CDN data center serving your local region. CDNs play DNS games so when you lookup the name you get the IP of a nearer data center. For example, someone in New York doesn't want to deal with extra latency streaming content located in California, and someone in London doesn't want to deal with latency from content on a server in Germany. and then use those in any rules that you are writing on the system. DNS providers will resolve generic CDN names to local data centers so you get faster response times. All the other firewalls I have worked with have some form of this where you can set up a group of ports, IPs, etc. Some of this is handled by BGP IP routing, but DNS also plays a big part. What IPs you see depend on where you are.
The different criteria (matchers) are as follows: Source IP address Source port.
iptables is a command line firewall that uses the concept of chains to. Netflix uses a CDN (actually, more than one CDN) with a huge number of potential IPs. Untangle's Firewall applicationis a layer 7 firewall, whichmeans itcan. It uses the concept of IP addresses, protocols (tcp, udp, icmp, etc) and ports. Other people will see different IP ranges, and even you will see different IPs over time. Those are the IPs returned by your local DNS service.
0 kommentar(er)
