Cable Forum - View Single Post

qasdfdsaq · 10-05-2015, 00:50

If it says "Waiting for" then that suggests it has managed to successfully connect to the server, so ruling out any routing or range-blocking issues. Given that it's still ISP specific, I'd guess something in the TCP/IP stack is breaking things.

Could be a problem with PMTU/MSS, or an intermediate hop/transparent proxy/filter breaking when faced with window scaling, fragmentation or something like that. A Wireshark trace would help, esp. one with and without VPN, though with MTU issues being more likely I'd try just setting that down first. Or their implementation of SPDY or pretty much anything else on layer 3 through 6.

Regardless, anything other than an MTU problem would suggest your ISP is intercepting and/or tampering with your connection to the server.

10-05-2015, 00:50	#14
qasdfdsaq cf.mega poster Join Date: Aug 2004 Posts: 11,207	Re: Cover City If it says "Waiting for" then that suggests it has managed to successfully connect to the server, so ruling out any routing or range-blocking issues. Given that it's still ISP specific, I'd guess something in the TCP/IP stack is breaking things. Could be a problem with PMTU/MSS, or an intermediate hop/transparent proxy/filter breaking when faced with window scaling, fragmentation or something like that. A Wireshark trace would help, esp. one with and without VPN, though with MTU issues being more likely I'd try just setting that down first. Or their implementation of SPDY or pretty much anything else on layer 3 through 6. Regardless, anything other than an MTU problem would suggest your ISP is intercepting and/or tampering with your connection to the server.