Vulnerability Development mailing list archives

Re: chaging your @home IP address... could you take a bunch of them....probably... could you get something from it...maybe


From: "Hyb" <seclist.localhost () ntlworld com>
Date: Wed, 6 Feb 2002 02:57:13 -0000


----- Original Message -----
From: "Jon Zobrist" <kgb () ussr com>
To: <vuln-dev () securityfocus com>
Sent: Tuesday, February 05, 2002 9:52 PM
Subject: chaging your @home IP address... could you take a bunch of
them....probably... could you get something from it...maybe

I just read the @home IP change instructions in the Hacker's Digest and an
interesting idea came to me...

If @home uses IP addresses in parts of their bandwidth (upload)
throttling,
then could you just take more IP addresses and get more bandwidth?

Now, I don't have @home :( so I can't test it, but can anyone out there
test
this?

If so, I'd say the race is on to get @home addresses for more bandwidth..

Generally speaking, cable capping isn't performed on a per-IP basis.
Customers are normally distinguished at the headend by means of the cable
modem's external MAC address, and in turn you're given the relevant capping
file. At least this is the DOCSIS standard, I presume @home operate by the
same means.
Also, it'd be worth noting the DHCP server at their end is unlikely to dish
out two IP's.
Though I could just be very tired and talking rubbish, so feel free to
correct me. =]

- Hyb
- http://deviate.cx/


Current thread: