Hacker News Reader

Comment by gen220 | Hacker News Reader

My corporate laptop is affected. My roommate’s corporate laptop is totally unaffected. We’re on the same router/gateway.

Any theories out there to explain this phenomenon? Fascinating.

(My theory is a network partition, where my roommate’s IP addresses happen to be in regions that are on “our side” of the partition, whereas my IP Addresses are on the “other”, unreachable side).

View on HN

Are you using different DNS servers? My work laptop was using 8.8.8.8 and is getting name resolution errors, but my personal computer is using 1.1.1.1 and working fine.

Interestingly enough, they’re both deferring DNS to our router, and the router is configured to use DNS servers dynamically provided by the ISP.

its most likely your companies RDP infrastructure (or local environment) operates on AWS. Which is down because of this "cut"

I didn't do any digging but it seems like once you have a connection established, it's not too bad. Is your roommate on a full-tunnel VPN?

They weren’t on a VPN, but my guess is that they got IP addresses from their DNS requests that were on our side of the partition.

In any case, it looks like it’s ended for us. The window for gathering evidence slides closed...

It’ll be interesting to read the post mortem on this one.

Thanks for the tip; connecting to a full-tunnel VPN seems to fix this for me. (FiOS in Brooklyn).

Is your roommate on a VPN? It looks like Verizon is having trouble only with traffic to certain destinations (perhaps Google and AWS).

They’re not. I’m on a split VPN, for what it’s worth. Disconnecting even from the split VPN does not help my laptop.

Reply on news.ycombinator.com