The problem here is that many places segment their guest network away from the internal one, but they use the same DNS server for both, so guests can still resolve internal hostnames and perform rev DNS queries.
I usually like to run a traceroute or two (to some arbitrary external IP like 1.1.1.1 or 8.8.8.8) whenever I connect to a new network. As traceroute does rev dns by default, if you see the internal hostname for your default gateway (and possibly other hosts inbetween you and the wider internet), those IPs are likely good starting points for your rev DNS shenanigans.
dig -x 192.168.1.1 @224.0.0.251 -p 5353
Saw the Vaddio logo and had to chime in. Gotta stick up for my Minnesota devs.
> How’d IT know it was me? I yapped about it for two weeks!
You know, I think maybe the first part is how they found out about you, rather than that they just happened to follow you on social media :)
This must be happening in some alternate universe.
I once stood up a DHCP server without realizing I'd start serving addresses to my entire dorm. I shut it down after just a minute or so having served 10 or 15 addresses out. A few minutes later my dorm phone rang asking about what I had done. Fortunately I could say with a straight face I'd already shut it down.
(Before anyone says "why didn't they just", this would be 1997 or 1998. Networks and their tooling have come a long way since then.)
I think "kid did a hacking, adults called the cops" is less common than people think, it just doesn't usually make the news when that happens, only when the cops get involved the media get involved, so essentially survivor bias.
So I found some always on lab machine and ran squid on it, so I could get on the Internet through the labs from my dorm.
Turns out some tech found it after a few months, and tried to kill it but ended up fork bombing the system. And it fork bombed again whenever they rebooted it. That system apparently was the one used for scheduling anything at the college and they weren't happy with it going down.
At like 8am one day 3 techies knocked on my door and were like "uhhh..please don't run squid any more" and that was that.
It was a glorious 3 months though when I was getting 1mb/s downloads and everyone else around me was getting 75kb/s
There are so many of these tools that simply re-stream the RTSP CCTV feed with no support for using any sort of authentication though - the expectation is you configure firewall rules appropriately so only the "correct" devices can view the feed on the open port.
> I used ai for a single rust scope issue that google wasn’t giving me clear answers for.
Nowadays, this needs to be highlighted. Congrats
And eventually the knowledge gets out anyway and someone who doesn't care does more damage that's harder to clean up.
what, the university using default passwords on freaking cameras? agreed!
If this was written 20-25 years ago sure, but in 2026? Wild.
Why?! ;_;
...and intentionally pushing campus-wide infrastructure really hard (mostly because something isn't happening as fast as you would prefer), breaking the entire campus network (of a school with 7,000 students), and then proudly bragging that you broke that infrastructure.
...and then proudly bragging about that...
This kid has a huge ego that is going to get him into a lot of trouble some day when he swings his dick on a network where people are Not Amused.
I'm going to guess his next run-in will be at an internship or his first job, and he'll get fired.
Getting hauled into the dean's office and being told he'd lost the privilege to do any network 'investigating' outside of direct supervision in a pre-approved academic project would do a great job of correcting the inflation level of his ego and keep him from doing the same thing later where the people who run it are Not Amused and there are serious consequences.