this post was submitted on 16 Jul 2024
211 points (97.3% liked)
Technology
60084 readers
4914 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Sounds like they could have been lazy and simply disabled/blocked your dns lookups, or stopped providing your route to 0.0.0.0/0. VPN provides new dns provider and a route to the internet at large, and you’re back in business.
It couldn't be a routing issue, because they'd never be able to get past the modem out to the rest of the world.
The DNS one is a pretty good guess. Another is that they were just doing HTTP redirects on every lookup. If this was >14 years ago, FireSheep had not been released yet (2010) and most sites only did HTTPS for authentication, and browsers didn't really try HTTPS first. So a lazy but semi competent admin could just redirect all the port 53/80 traffic and hose a normal browsing session, but a VPN coming up with direct IP config would bypass that and bring them back online.