I recently switched from AT&T's DSL service to U-verse. It's their 300-level service; one bug report out there implied that routers work differently at different levels of U-verse service. I'm noticing flaky performance when establishing SSL connections. Symptoms:
1. Establishing an SSL connection is sometimes instantaneous and sometimes takes ~1 minute and sometimes never works.
2. If I establish a tunneling VPN connection (with ProXPN free demo), all problems disappear. Problem is clearly in the U-verse router and not my Apple computers.
3. If I go into Chrome incognito mode, SSL connection establishment is typically instantaneous, but not always.
4. I sometimes see a "bad certificate" message from the router.
I think whatever SSL certificate checking the router is doing is broken. I'd like to turn all of that nonsense off. Has anyone figured this out? Thanks.
1. Establishing an SSL connection is sometimes instantaneous and sometimes takes ~1 minute and sometimes never works.
2. If I establish a tunneling VPN connection (with ProXPN free demo), all problems disappear. Problem is clearly in the U-verse router and not my Apple computers.
3. If I go into Chrome incognito mode, SSL connection establishment is typically instantaneous, but not always.
4. I sometimes see a "bad certificate" message from the router.
I think whatever SSL certificate checking the router is doing is broken. I'd like to turn all of that nonsense off. Has anyone figured this out? Thanks.
Last edited: