|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
X-Original-To: nanog@nanog.org To: "Paul Stewart" <paul@paulstewart.org> From: Rob Seastrom <rs@seastrom.com> Date: Fri, 30 Jan 2015 06:48:38 -0500 In-Reply-To: <011701d03bad$86476030$92d62090$@paulstewart.org> (Paul Stewart's message of "Thu, 29 Jan 2015 05:22:44 -0500") Cc: nanog@nanog.org Errors-To: nanog-bounces@nanog.org "Paul Stewart" <paul@paulstewart.org> writes: > That has been my experience as well (only from the RF side) and I would > believe this was a design choice. The ISP usually wants to keep control > over the firmware versions of the CM for various technical/support reasons > versus having consumers mess with the firmware. 15 years ago, in certain circles it was well-understood how to load one's own (possibly patched) software from the Ethernet side on the old LanCity (pre-DOCSIS) cablemodems. You can imagine what kind of hilarity ensued. -r
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |