Hello I just got done setting up OpenVPN on my PfSense box but now I cant watch any of my Netflix content. I was reading up and saw that I can't use my VPN because Netflix blocks anyone using a VPN. I just want to set a rule to push all traffic going to Netflix through my ISP. I have tried 2 list that I found online but I still get blocked. Does anyone here have a good list I can use or a better solution. I mean it would be nice if Netflix just publicized there list of IP if they are going to go out and block VPN users. That way they could just go in and fix this themselves but they don't and make this hard for the end user.
pic related its my lan rules and part of my Netflix Aliases.
If only there was some sort of domain name resolving service you could use to find their IPs yourself.
>>59714052
do you not see the large list of ip of Ip's that i have set. do you not think that i have already used whois and wireshark to try and get more IP's
:~$ dig moviecontrol.netflix.com
; <<>> DiG 9.10.3-P4-Ubuntu <<>> moviecontrol.netflix.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9194
;; flags: qr rd ra; QUERY: 1, ANSWER: 10, AUTHORITY: 4, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;moviecontrol.netflix.com. IN A
;; ANSWER SECTION:
moviecontrol.netflix.com. 300 IN CNAME moviecontrol.geo.netflix.com.
moviecontrol.geo.netflix.com. 1800 IN CNAME moviecontrol.eu-west-1.prodaa.netflix.com.
moviecontrol.eu-west-1.prodaa.netflix.com. 60 IN A 54.173.193.109
moviecontrol.eu-west-1.prodaa.netflix.com. 60 IN A 54.174.25.52
moviecontrol.eu-west-1.prodaa.netflix.com. 60 IN A 54.83.242.85
moviecontrol.eu-west-1.prodaa.netflix.com. 60 IN A 54.83.174.41
moviecontrol.eu-west-1.prodaa.netflix.com. 60 IN A 52.73.149.37
moviecontrol.eu-west-1.prodaa.netflix.com. 60 IN A 54.86.222.192
moviecontrol.eu-west-1.prodaa.netflix.com. 60 IN A 54.86.47.138
moviecontrol.eu-west-1.prodaa.netflix.com. 60 IN A 54.87.11.181
;; AUTHORITY SECTION:
prodaa.netflix.com. 172800 IN NS ns-1489.awsdns-58.org.
prodaa.netflix.com. 172800 IN NS ns-1606.awsdns-08.co.uk.
prodaa.netflix.com. 172800 IN NS ns-375.awsdns-46.com.
prodaa.netflix.com. 172800 IN NS ns-749.awsdns-29.net.
;; Query time: 688 msec
;; SERVER: 10.25.16.1#53(10.25.16.1)
;; WHEN: Mon Apr 03 10:05:35 CEST 2017
;; MSG SIZE rcvd: 393
We l33t h4x00rs call it DNS resolution.
>>59715014
you are a l33t haxor that dig tool is pretty neet.
>>59715014
use short next time
but i'm still getting blocked even after I added all the ip on that answer section.
>>59715014
but this method did get me past Namecheaps VPN filter.
>>59715098
Add the IPs for netflix.com and for moviecontrol.netflix.com (their CDN). Resolve that with your usual DNS, not the VPN provided ones as those results are provably conditional to your location.
If this fails I don't think it would be too hard to take a wireshark dump / tcpdum while you try to connect and grep your way around what IPs you missed to route through your ISP gateway.
>>59715305
Netflix is a jumbled mess to my understanding. there whole system works off micro services on AWS so there is no way of knowing what server is sending me what packets. on top of that they are always spawning new micro services with new Ip's so this list is contently evolving. This is a pain in the ass I add the Ip's I get off wireshark added to my list of IPs. then refresh the page and 5 new IP are knocking at my door. its like playing wack a mole.
>>59715305
A video I found
https://www.youtube.com/watch?v=CZ3wIuvmHeM&t=848s
>>59715582
https://youtu.be/CZ3wIuvmHeM?t=10m3s
meant to post with a timestamp