I worked for a ISP. A cable company. We were getting our local offair channels from a site that was in easy reception of them. They had a large amount of bandwidth and did the same thing for dish and direct tv. The man who ran network side had a stroke and died. The hack that ran the broadcast side of their main business took over. Next thing I know I’m having all kinds of problems with our multicast tunnel. I port scanned the IP range and discover they have opened the whole thing up. We had a conference call where I detailed my concerns. Later that day the hack called my boss with his boss on the line and we had another meeting where I told them that they were exposed with default passwords and it could be a real problem.
After I was given verbal permission to demonstrate my concerns with some limitations I took over all default password equipment and sent a large amount short stories to their printers. I ended it with the story superiority by Author C. Clark. Some back and forth a day later and they needed a new sysadmin.
phx@lemmy.ca 3 days ago
Uh… you can’t just “expose a LAN network to the Internet” in this manner. Local subnets aren’t routable over the Internet, so you can’t just enter 192.168.2.3 and end up on somebody else’s private LAN.
geeksforgeeks.org/…/non-routable-address-space/
They would have needed to either have all their internal devices being assigned public IP’s or had NAT+firewall rules explicitly routing ports from their outside address(es) to the inside ones. The former is unlikely as normally ISPs don’t allocate that many to a given client, or at least not by DHCP. the latter would require a specific configuration mapping the outside addresses/ports to inside devices, likely on a per device+port basis.
Either your story is missing key details or you’ve misunderstood/made-up something.
bobo@lemmy.world 2 days ago
They did indicate that the subnet they provided in the example was not the actual one they used.