Recently certain TCP connections through my router have been stalling after the connection has been setup. i.e. the connection is established but neither side sends any data or so it appears.
This is most noticeable when I visit certain websites. Web traffic to servers on port 80 is routed through my squid cache and suffers no similar stalling. However https connections are not routed through my squid, and they are the best example of this problem.
If I try to direct my browser to webmail.cornell.edu (this will redirect to a secure website for login), I get so far as having the website's title displayed (CUWebLogin), and at that point the connection inexplicably stalls.
Netstat shows the connection as established:
netstat -an | grep 443
TCP 192.168.1.100:2030 220.127.116.11:443 ESTABLISHED
I'm fairly certain that packets associated with these connections are not being dropped as they are placed in a specific htb class that has the highest priority with other interactive traffic, and looking at the stats for the class indicates it hasn't dropped any packets.
This issue occurs regardless of whether my upstream is saturated. I'd appreciate any suggestions you all have.
DSL connection with Verizon