The Great Firewall of Yale
162.209.96.128
The Great Firewall of Yale
1–10 of 135 posts
Re: The Great Firewall of Yale
#2Re: The Great Firewall of Yale
#3Still, this is a stupid move by Yale.
Re: The Great Firewall of Yale
#4You would think that the Yale administrators would know better than this.
Re: The Great Firewall of Yale
#5Re: The Great Firewall of Yale
#6I don't think blocking a specific set of IP addresses constitutes deep packet inspection. If they were reading the payload contents for strings matching the CourseTable site, that would qualify. Still, this is a stupid move by Yale.
... not that that constitutes DPI either.
Re: The Great Firewall of Yale
#7Re: The Great Firewall of Yale
#8Re: The Great Firewall of Yale
#9They claimed I was creating excess load, which is silly because if they really did the math, given how many people were using my service I was probably saving them resources.
Re: The Great Firewall of Yale
#10I don't think blocking a specific set of IP addresses constitutes deep packet inspection. If they were reading the payload contents for strings matching the CourseTable site, that would qualify. Still, this is a stupid move by Yale.
If they were only blocking based on IP address then students wouldn't be able to ping the server. So they're blocking on at least the TCP layer. ... not that that constitutes DPI either.