Usually, what most people see is only the broadcast type traffic like
DHCP, NetBIOS, certain UDP thingies, occasionally arps, etc... The bridge
usually does not pass all the traffic, but there is no guarantee of that.
Particularly with cable modem where your whole subdivision is on the same
physical wire.
On Tue, Nov 23, 1999 at 10:08:21PM -0800, Gordon Messmer wrote:
> I'd like to apologise for what was probably some really bad advice, and
> thank those people who made that clear :)
>
> Not that explanations make up for lack of paranoia, but my own exposure
> to real use of DSL is limited. It's just being rolled out in my neck of
> the woods. The modems that Ellensburg Telephone plan to offer come in
> network, and USB flavors. The network model does NAT itself, so it's
> basically a secure firewall/hub all by itself. Local traffic is not
> broadcast.
>
> >From accounts I'd heard of, cable modems are usually configured to
> accept only traffic for IP's that it knows are local, and broadcast only
> data to IP's that are not local. It didn't clearly register that some
> modems may not behave in this fashion.
>
> I stand corrected.
>
> MSG
>
>
> PS: Out of curiosity, how many of you DSL users can actually use
> tcpdump, or (gasp) ngrep, to watch what your neighbors are doing??
>
> I can see it now... People in a network segment getting an email
> w/Subject "I know what you did last summer...."
> <insert long list of adult-only sites for yourself.>
>
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
>
--
J. Scott Kasten
jsk AT tetracon-eng DOT net
"That wasn't an attack. It was preemptive retaliation!"
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
