its easier to explain with a little illustration....
your mac is 6 bytes (48 bits) long, 3 bytes (24 bits) are used to identifier the manufacturer, and the other 3 bytes (24 bits) are used as the serial number of the device. a manufacturer could make a 250 modem, a surfboard modem or a 100 modem, each with the same manufacturer code. but the first couple of bits for the serial number of the mac will be the same for each particular model of modem.
255 = 00:01:02:03:04:05
SB51000 = 00:01:02:07:08:09
100 = 00:01:02:11:22:33
its likely a manufacturer has a different manufacturer id for each modem model, but thats a different issue.
the point is.... my app uses the last byte of the mac, using the first 5 as a base, therefore, its gonna return macs based on the same model of modem as the original mac.
the app was intended to comply with the DOCSIS spec, but it was a rush job that never got finished, i think i only spent a weekend or 2 on it, and i could only really test it in an NTL area, martsmall and nozzer on DW helped me sort issues that were happening on TW but as for it working 100% in a TW i really dont know.
i know that gentlex has mentioned the possible issue with TW, but the next app im working on (when i have the time
) is based on the DOCSIS spec, so it should be plug and play with any area.
im also trying to figure out how to make an environment-aware modem, which will basically have my software as the firmware lol
hope this helps...