Oops, missed the original response.
>>> >So, I'd like to figure out exactly how it is setup, and works. Anyone have
>>> >suggestions how to go about this?
>>>
>>> As I said, who cares. All it does is extend your ethernet connection to
>>> your ISP. Just consider it a RJ-45 cable extender.
>>
>>I care. I like to know how things work. It never ceases to amaze me when I
>>meet people who drive a car every day and couldn't care less how it works.
>>I care! I've taken practical every component of a car apart (and put
>>most of them back together again :) ), because I like to know what makes
>>them tick. Admittedly this has usually only occured when something has
>>gone wrong, and you could argue that in this case I don't have a problem.
Semantics. I read the posting to mean that you wanted to know how to set up,
i.e., configure the modem. I responded that you don't configure them, so
you don't care.
What you are really asking is how the DSL technology WORKS. You choice of
words led me down the wrong path.
In any event, the response from the Pacbell guy pretty much answered that.
The setup that we have here is pretty much the same.
>>> I only see traffic intended for my IP. If they were to send all of the
>>> TCP, UDP, etc traffic down my line that was at the rack on the other end
>>> of my DSL line I wouldn't have any bandwidth what-so-ever. Sorry, but you
>>> will only see IP traffic intended for you.
>>
>>Hmm. This is a very good point. However, I'd like to verify this for
>>myself before accepting it. Also, as I stated earlier, I can see other
>>windows workgroups on my PC behind my gateway - where the hell are they
>>coming from then?
>>charles
When I first had the DSL isnstalled and before I put my web site up on it
(it was operational elsewhere), there was very little traffic. If I were
to see everyone else that was on the DSLAM, the green traffic lights would
be constantly lit. They weren't. As it turns out, before I went on line,
there was a ping flood attack that had one node hitting me. It caused all
kinds of grief. But that is neither here nor there. While working with
the various places, I was running tcpdump to watch the traffic and the
only traffic on my DSL was meant for me, or came from me.
If you mentioned your home configuration before, I must admit that I have
forgotten it. Where is your Linux box in all this, or are you saying that
your PC is your Linux box? If your Linux box is the only computer attached
to your DSL and you can see other computer traffic via tcpdump, then a
call will be necessary to your ISP to get the routing fixed. You are
not paying for your DSL bandwidth to be eaten up by packets meant for others.
MB
--
e-mail: [EMAIL PROTECTED]
[Where do you think Microsoft would be today if they waited]
[until their software worked? (Hyperion Bay - 10/12/98)]
Visit - URL:http://www.vidiot.com/ (Your link to Star Trek and UPN)
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
