History of 127/8 as localhost/loopback addresses (2021)

Re:History of 127/8 as localhost/loopback addresses (2021) by X-Istence on Wednesday May 25, 2022 @01:00PM (#31507248)

That's because bandwidth caps are enforced by the cable modem and not further downstream. When you pay for 10 Mbps down, 1 Mbps up, that is enforced by the cable modem.

Earlier versions of cable modems had flaws that allowed consumers to push configs on the ethernet port and uncap their cable modems and gain higher speeds than they had paid for.

[ Parent | on HN ]

Re:History of 127/8 as localhost/loopback addresses (2021) by bell-cot on Wednesday May 25, 2022 @03:34PM (#31509439)

If the ISP could add a paragraph to their T&C's, then monitor the speed...

"Thank you for upgrading your service to our VVVIP Price Tier! Your first three months as a VVVIP customer is 50% off..."

[ Parent | on HN ]

Re:History of 127/8 as localhost/loopback addresses (2021) by vlan0 on Wednesday May 25, 2022 @05:24PM (#31510774)

>If the ISP could add a paragraph to their T&C's, then monitor the speed...

They did, but the overhead at the time was high. And they generally didn't peruse unless you were causing trouble....or slipped up on OPSEC.

Cable ISP network security back in the day was horrid. SNMP string would get leaked. With that you could snmpwalk the entire node you were on. It was amusing.

[ Parent | on HN ]

Re:History of 127/8 as localhost/loopback addresses (2021) by wyager on Wednesday May 25, 2022 @02:05PM (#31508231)

Yep, what a silly design. I almost want to hack it out of spite.

[ Parent | on HN ]