No apology necessary.
I honestly still don't know exactly how my DSL setup works (and do want to
know). I am aware there are many varying setups. I get DSL in Northern
Virginia (USA) through GTE. They did *zero* configuration to the modem -
just plugged it in and waited for 3 solid lights. This was the extent of
the install. SO I highly suspect I'm as open to abuse as those cable modem
guys.
So, I'd like to figure out exactly how it is setup, and works. Anyone have
suggestions how to go about this?
If I wasn't so damn busy, I'd love to see who else is doing in my
"neighborhood". Are there any nice front ends to things like tcpdump to
help filter the output and make sense of it?
thanks
charles
On Tue, 23 Nov 1999, 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.
