Article View: comp.dcom.modems.cable
Article #511Re: cable guy "vapor"-izes DSL 3X cable TV troll!
From: Lawrence Baldwin
Date: Wed, 31 Jan 2001 01:33
Date: Wed, 31 Jan 2001 01:33
88 lines
4756 bytes
4756 bytes
John Navas wrote: > > [POSTED TO comp.dcom.modems.cable; PLEASE REPLY THERE] > > In <3A76B6CA.73B36B26@mynetwatchman.com>, Lawrence Baldwin > <baldwinlSPAMMENOT@mynetwatchman.com> wrote: > > >I actually contend that DOCSIS cable (assuming encryption is turned on) is more > >secure than DSL. Since DSL isn't encrypted, it can be packet sniffed at > >any (relatively unsecured) cross box or pedestal, albeit with a VERY expensive > >analyzer. > > Am I missing something, or are you just referring to encryption between > the cable modem and the CMTS? Absolutely. > If the latter, then traffic beyond the > CMTS is unencrypted, and just as exposed as DSL traffic. Both are > secure on the local link; ADSL sure isn't secure on the local link, for reasons above. If typical cable modem isn't encrypted, than agree it's equally insecure. What irks me is when ADSL providers say: "ADSL is more secure than because your connection isn't shared between your home and central office". I think it's ridiculous to associate *shared* with *insecure* without obviously taking the time to understand the issues. Even worse, they're inferring that the *unshared* = *secure* (from all threats), which is dangerously mis-leading. I doubt packet sniffing the local link is a big concern anyway, so this is really pretty moot. I guess my only big concern would be with cable modem...I've heard that the modems get be put into an promiscous debug mode and and start forwarding *all* traffic out the Ethernet port. This would be a real threat as it means anyone with a shareware analyzer could Sniff. If this isn't possible, then you'd need a broadband analyzer, which would be out of most people reach. >both are exposed on shared links beyond the CMTS/DSLAM. Agreed. But presumably access to network infrasture is physically secured at these layers. Anybody can walk up to a pedestal and cross box and jack in without much trouble. > > I agree that most broadband ads are colorful nonsense. Nevertheless, > there is a real and important difference -- when the uplink saturates on > the typical consumer asymmetrical TCP/IP connection, downlink speed > takes a big hit down to about the uplink speed (e.g., your 128/1500 > service suddenly becomes 128/128). OK, but what percentage of users are impacted by this. > On DSL, that affects *only* the > subscriber's own downlink; on cable, that affects *all* subscribers on > the shared segment. It's the big dark secret that cable MSO's don't > want to talk about, and the probable reason that servers are typically > prohibited on cable, even with an uplink cap, but not on DSL. HUMMMM. VERY interesting point. Basically one porn server in the "neighborhood" and the whole darn thing is down even though there's tons of downstream bandwidth available. ....hmmmm.... DSL is looking better and better every day. I have no hands-on experience with cable infrastructure internals, but a lot of what you content would seem to depend on how cable is throttled. I know that DOCSIS has the *capability* of defining transmission slots such that the cable is no longer a CSMA/CD shared Ethernet...however, I'm pretty sure that almost no one implements this. Anyone know for sure?? -- ------------------------- Lawrence Baldwin Protocol Scientist 678-624-0924 http://www.mynetwatchman.com - I'm under attack, now what?
Technical Details
Message-ID:
<3A776B57.C495242C@mynetwatchman.com>Path:
arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!supernews.com!nntp-relay.ihug.net!ihug.co.nz!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.atl.bellsouth.net.MISMATCH!newsfeed.atl!news3.atl.POSTED!not-for-mailReferences:
<3A648E27.6A7029EF@erols.com> <20010116192016044.AAA95@adsl-209-204-185-87.sonic.net@john.navasgroup.com> <3A64B680.2A79F24D@erols.com> <3A76B6CA.73B36B26@mynetwatchman.com> <4OGd6.100$mW6.5202@typhoon.sonic.net>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1122a6,2145df83169cbbc6 X-Google-Attributes: gid1122a6,public X-Google-Thread: 113850,916316de6f72ceb X-Google-Attributes: gid113850,public X-Google-ArrivalTime: 2001-01-30 17:33:20 PST Path: arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!supernews.com!nntp-relay.ihug.net!ihug.co.nz!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.atl.bellsouth.net.MISMATCH!newsfeed.atl!news3.atl.POSTED!not-for-mail Message-ID: <3A776B57.C495242C@mynetwatchman.com> From: Lawrence Baldwin <baldwinlSPAMMENOT@mynetwatchman.com> X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.dcom.modems.cable,bellsouth.net.support.adsl Subject: Re: cable guy "vapor"-izes DSL 3X cable TV troll! References: <3A648E27.6A7029EF@erols.com> <20010116192016044.AAA95@adsl-209-204-185-87.sonic.net@john.navasgroup.com> <3A64B680.2A79F24D@erols.com> <3A76B6CA.73B36B26@mynetwatchman.com> <4OGd6.100$mW6.5202@typhoon.sonic.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Lines: 88 Date: Tue, 30 Jan 2001 20:33:11 -0500 NNTP-Posting-Host: 208.61.191.103 X-Trace: news3.atl 980904792 208.61.191.103 (Tue, 30 Jan 2001 20:33:12 EST) NNTP-Posting-Date: Tue, 30 Jan 2001 20:33:12 EST