ADSL Mail Log from John DeWolfe
Following is John DeWolfe's e-mail log documenting the process
he went through to get ADSL installed at his home.
When you read the log, be sure to read the whole
history before you make conclusions, because even John's
conclusions change through the history.
From john Fri May 1 17:09:28 1998
Return-Path:
Received: by alpha.dewolfe.com. (SMI-8.6/SMI-SVR4)
id RAA07313; Fri, 1 May 1998 17:09:11 -0600
From: john (John R. DeWolfe)
Message-Id: <199805012309.RAA07313 at alpha.dewolfe.com.>
Subject: DSL in Denver
To: kooros at kooros.com, quent@csn.net, petersky@earthlink.net
Date: Fri, 1 May 1998 17:09:10 -0600 (MDT)
Cc: john (John R. DeWolfe)
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1026
Status: O
Fri May 1 17:01:52 MDT 1998
Just so you know, I have an actuall install date for DSL to my house of
May 18th. This is 256Kbits/sec Internet access over existing phone lines
from US West. Cost $300 install, $60/mon. We'll see if it really happens
or not, but I am excited. I'll let you know what happens. There are a lot
of issues, but if you want more info, let me know.
Later,
P.S. I was the very first person the US West sales rep signed up. Can you
spell "Guinie Pig"? :-)
P.P.S. Paul Kooros, I just signed up with US West as the ISP. Things are
so shakey I didn't even want to try to complicate things trying to introduce
NetTracks as the ISP. Once things settle down, I'll look into alternatives.
Hope Barb isn't to mad at me, she seemed very emphatic when I talked to her
about this last week!
--
----------------------------------------------------------------------------
John R. DeWolfe email : John.DeWolfe at dewolfe.com
DeWolfe Enterprises voice : (303) 722-4461
From john Mon May 4 15:38:09 1998
Return-Path:
Received: by alpha.dewolfe.com. (SMI-8.6/SMI-SVR4)
id PAA04895; Mon, 4 May 1998 15:37:58 -0600
From: john (John R. DeWolfe)
Message-Id: <199805042137.PAA04895 at alpha.dewolfe.com.>
Subject: DSL questions
To: sgailla at uswest.com
Date: Mon, 4 May 1998 15:37:58 -0600 (MDT)
Cc: john (John R. DeWolfe)
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 4487
Status: O
Mon May 4 12:36:19 MDT 1998
Hello,
My name is John DeWolfe and I am scheduled for DSL installation at my
house in Denver on May 18th. It is being installed at 303-744-9625. I am a
sophisticated end-user and have several DSL related questions. I was given
your name and email address by Ian at NetSpeed/Cisco. He said you could
either provide answers or provide further contact information for questions
that I had about US West's DSL deployment.
1) I understand that DSL will be deployed as a bridged environment. How
broad is the bridged area? Exchange? Central Office? Neighborhood? Broader?
2) Since the environment is bridged, will I be seeing all traffic from all
other DSL subscribers appearing on my DSL connection, or maybe just broadcast
traffic? I am worried about security and the ability of others to capture
password information from telnet, ftp, etc. connections.
3) Is US West doing anything to prevent home DHCP servers from wrecking havoc
with other bridged customers by giving out bad IP addresses? This has been
a problem for many cable modem providers on the East and West coasts.
4) Will US West be providing both forward and reverse DNS for the DHCP
addresses? Enough FTP sites require both and that forward and reverse
match, to make this a requirement in many regards. I don't care what the
name is (cust127.dsl.denvera.uswest.com, etc.) As long as forward and reverse
are both available and match.
5) Rather than using a DSL filter on every phone, I would rather use the
whole house splitter that is available from NetSpeed/Cisco. I am perfectly
willing to install this myself. Can I buy that through US West? NetSpeed
said that I should contact you for sales of this device.
6) I've been told that static IP addressing will be rolled out in the Jun/Jul
timeframe. Is this correct? Is there an extra charge for this? If so, how
much?
7) Are there any plans to offer routed instead of bridged networks? This would
make me feel more comfortable about security.
8) If I change computers or network cards, do I have to call US West to let
them know that I have a new MAC address before the new hardware will work
with your DSL connection? I was planning on experimenting with two different
computers as my DSL connection. This would be a problem if I had to call
US West every time.
9) What is to prevent someone from hooking up two computers and getting
assigned two different DHCP addresses for each system? Is this answered by
question 8, registered MAC addresses?
10) Are you only supporting IP protocols? Can I use other transports like
NetBUI or IPX/SPX? You are probably not routing these protocols, but if these
are not screened at the DSL modem, this would allow me to play network games
or share files with neighbors in my local DSL bridged subnet. (I have equally
techy neighbors)
11) Are you doing any firewalling/filtering of any kind? Either outgoing or
incoming? If I need to connect to some obscure port, or put up a server
listening on such a port, would there be anyting to prevent this? I know the
IP address of my system is dynamic, but aside from that? If I want some
sort of custom filtering, could you provide that service?
12) I am using US West as my ISP. Does this come with any services such as
news, email addresses, web space, proxy servers, remote dialin, etc.?
13) In the interest of saving your own internal bandwidth, will you be
requiring that users use a US West proxy server for web access?
14) Are there any guarantees on my bandwidth? If I purchase a 512K line, am
I guaranteed 512K will be available? Is it more like cable modems where I
am sharing something like 1.5Mb of bandwidth with everyone within my DSL
bridge? In this case I am limited by the speed I pay for, but there is a
total limit as well. If not proprietary, can you tell me how much bandwidth
is available at each central-office?
15) Will each central office act as a single DSL bridge, or could there be
many bridges at each central office? Is central office the correct term for
where my DSL line originates withing US West? Is there a term for the DSL
bridge subnets I have been referring to?
Thank you so much for your help. I am really (REALLY) looking forward to
this new service!
--
----------------------------------------------------------------------------
John R. DeWolfe email : John.DeWolfe at dewolfe.com
DeWolfe Enterprises voice : (303) 722-4461
From john Thu May 14 11:59:29 1998
Return-Path:
Received: by alpha.dewolfe.com. (SMI-8.6/SMI-SVR4)
id LAA12504; Thu, 14 May 1998 11:59:12 -0600
From: john (John R. DeWolfe)
Message-Id: <199805141759.LAA12504 at alpha.dewolfe.com.>
Subject: Re: #2 DSL install in Denver!
To: dsl, john (John R. DeWolfe)
Date: Thu, 14 May 1998 11:59:12 -0600 (MDT)
In-Reply-To: <199805141649.KAA21548 at zek.co.symbios.com> from "Quentin Johnson" at May 14, 98 10:49:48 am
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 2955
Status: OR
>
> According to US West:
>
> They're using 3 different boxes on the subscriber end: a PCI bus card,
> bridge or a router. The bridge is the $300 box and they can download
> software to it. I'm pretty curious about the details of that thing. The
> router would be nice to have but I think its $900. The stuff is made
> by Netspeed, which Cisco just bought. I doubt USWest can answer about
> details of the hardware, but Cisco and Netspeed have good web sites :-)
>
I am going to have to recnfirm with NetSpeed, but NetSpeed told me on
several occations that the $300 (model 202/204) CAN do both routing and
bridging.. US West is doing bridging initially. Maybe the confusion is over
what exactly "routing" means. I'm not sure what US West had in mind, but
when operated in "routing" mode, the 202/204 can do packet filtering, network
address translation, etc. In bridge mode, it cannot do any of that. I'll
reconfirm again with netspeed on this. But that is what both technical
support and the product manager told me on several different occations. They
also told me that the 204 has exactly the same functionallity of the 202, but
is cheaper to make (and consequently to sell).
> The USWest person said that initially your ADSL connection is just a point-to-
> point, but soon they'll offer (for more money) the option for you to switch
> between 4 different connections - that would be nice if I had an ISP and
> a work connection.
>
That is cool. I had not heard of that. Don't have an immediate use for it,
but you never know.
> I want to know whether I can get to my home system from other places. Indra's
> Net is going to assign static IP addresses but they're concerned about people
> setting up web servers and killing their bandwidth.
>
> If USWest is using DHCP, that poses a problem. In the past I've had
> my machine email me (at work) its IP address when the PPP connection comes
> up. That's good enough for now, but someday I might want to let others
> access my home network.
>
This is a big deal for me. US West is supposedly rolling out static IP
addresses in Jun/Jul. Until then, I will be working on dynically updating my
DNS server every time my IP address changes. I have a DNS server under my
control that is located elsewhere with a static IP address, so this will work
for me. I could proably do other domains to if needed. I'll have to set the
timeout to something like 20 minutes to make this work, but is better than
nothing. I heard a rumour that, at least initially, US West was going to
force renewels every 24 hours. It gets more complicated because I will also
try to dynamically update my firewall with the same new IP information!
Talk about looking for trouble! :-)
--
----------------------------------------------------------------------------
John R. DeWolfe email : John.DeWolfe at dewolfe.com
DeWolfe Enterprises voice : (303) 722-4461
From quentinj at zek.co.symbios.com Thu May 14 11:28:43 1998
Return-Path:
Received: from gatekeeper-r90.dewolfe.com by alpha.dewolfe.com. (SMI-8.6/SMI-SVR4)
id LAA12238; Thu, 14 May 1998 11:28:41 -0600
Received: from mpdgw2.symbios.com (mpdgw2.symbios.com [204.131.200.2])
by gatekeeper-r90.dewolfe.com (8.8.8/8.8.8) with SMTP id KAA02399
for ; Thu, 14 May 1998 10:52:27 -0600 (MDT)
Received: (from root at localhost) by mpdgw2.symbios.com (8.6.8.1/8.6.6) id KAA13729 for ; Thu, 14 May 1998 10:51:15 -0600
Received: from aztec.co.symbios.com(153.72.199.214) by mpdgw2.symbios.com via smap (V1.3)
id sma013409; Thu May 14 10:50:43 1998
Received: from zek.co.symbios.com (root at zek.co.symbios.com [153.72.240.235]) by Symbios.COM (8.6.8.1/8.6.6) with ESMTP id KAA00225 for ; Thu, 14 May 1998 10:50:41 -0600
Received: from zek (quentinj at localhost [127.0.0.1]) by zek.co.symbios.com with ESMTP (8.7.6/8.7.1) id KAA21548; Thu, 14 May 1998 10:49:49 -0600 (MDT)
Message-Id: <199805141649.KAA21548 at zek.co.symbios.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: John.DeWolfe at dewolfe.com (John R. DeWolfe)
cc: quentinj at zek.co.symbios.com
Subject: Re: #2 DSL install in Denver!
In-Reply-To: Message from John.DeWolfe at dewolfe.com (John R. DeWolfe)
of "Wed, 13 May 1998 18:38:24 MDT." <199805140038.SAA05154 at alpha.dewolfe.com.>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 14 May 1998 10:49:48 -0600
From: Quentin Johnson
Content-Length: 1773
Status: OR
> Wish I could have been there for that. Any big questions that I should get
> answered before install time?
They're using 3 different boxes on the subscriber end: a PCI bus card,
bridge or a router. The bridge is the $300 box and they can download
software to it. I'm pretty curious about the details of that thing. The
router would be nice to have but I think its $900. The stuff is made
by Netspeed, which Cisco just bought. I doubt USWest can answer about
details of the hardware, but Cisco and Netspeed have good web sites :-)
The USWest person said that initially your ADSL connection is just a point-to-
point, but soon they'll offer (for more money) the option for you to switch
between 4 different connections - that would be nice if I had an ISP and
a work connection.
I want to know whether I can get to my home system from other places. Indra's
Net is going to assign static IP addresses but they're concerned about people
setting up web servers and killing their bandwidth.
If USWest is using DHCP, that poses a problem. In the past I've had
my machine email me (at work) its IP address when the PPP connection comes
up. That's good enough for now, but someday I might want to let others
access my home network.
> It is possible that that CO is not modern enough to support DSL so it is
> actually coming from someplace else. Who knows!
My CO (cottonwood) is on the list of offices with ADSL. I'm pretty sure
that the "loop qualification" is only a database lookup and the database
isn't up to date.
I'll probably be able to get ADSL, it just won't be as soon as I thought.
If not, I'll get an ISDN connection - my line does qualify for that and
USWest has a good deal - 128K Internet service with no time limit for $39.95.
Quent
From quentinj at zek.co.symbios.com Mon May 11 15:46:34 1998
Return-Path:
Received: from gatekeeper-r90.dewolfe.com by alpha.dewolfe.com. (SMI-8.6/SMI-SVR4)
id PAA12462; Mon, 11 May 1998 15:46:32 -0600
Received: from mpdgw2.symbios.com (mpdgw2.symbios.com [204.131.200.2])
by gatekeeper-r90.dewolfe.com (8.8.8/8.8.8) with SMTP id PAA26075
for ; Mon, 11 May 1998 15:46:15 -0600 (MDT)
Received: (from root at localhost) by mpdgw2.symbios.com (8.6.8.1/8.6.6) id PAA17888 for ; Mon, 11 May 1998 15:45:43 -0600
Received: from aztec.co.symbios.com(153.72.199.214) by mpdgw2.symbios.com via smap (V1.3)
id sma016804; Mon May 11 15:43:46 1998
Received: from zek.co.symbios.com (root at zek.co.symbios.com [153.72.240.235]) by Symbios.COM (8.6.8.1/8.6.6) with ESMTP id PAA29413 for ; Mon, 11 May 1998 15:43:44 -0600
Received: from zek (quentinj at localhost [127.0.0.1]) by zek.co.symbios.com with ESMTP (8.7.6/8.7.1) id PAA12935 for ; Mon, 11 May 1998 15:42:54 -0600 (MDT)
Message-Id: <199805112142.PAA12935 at zek.co.symbios.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: John.DeWolfe at dewolfe.com (John R. DeWolfe)
Subject: Re: #2 DSL install in Denver!
In-Reply-To: Message from John.DeWolfe at dewolfe.com (John R. DeWolfe)
of "Mon, 11 May 1998 13:33:51 MDT." <199805111933.NAA11550 at alpha.dewolfe.com.>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 11 May 1998 15:42:53 -0600
From: Quentin Johnson
Content-Length: 93
Status: OR
I've been inquiring Indra's Net about their ADSL service.
I might just go for it!
Quent
From john Mon May 11 13:34:45 1998
Return-Path:
Received: by alpha.dewolfe.com. (SMI-8.6/SMI-SVR4)
id NAA11550; Mon, 11 May 1998 13:33:51 -0600
From: john (John R. DeWolfe)
Message-Id: <199805111933.NAA11550 at alpha.dewolfe.com.>
Subject: #2 DSL install in Denver!
To: dsl
Date: Mon, 11 May 1998 13:33:51 -0600 (MDT)
Cc: john (John R. DeWolfe), bfield at advtech.mnet.uswest.com
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 5978
Status: OR
Mon May 11 12:36:41 MDT 1998
Here is the latest on DSL. I got a call from MicroAge today. I am still
on for May 18th for an install date. US West is contracting with MicroAge
to actually bring the modem out and set it up at the customers house. I spoke
to the person who was coming o, and he tokd me I would be the second person
in the area to have DSL installed. The first person was in Boulder and that
went in last Thu. There were a few problems getting it going, but it was
working successfully the same day it was installed. That is certainly good
news!!!
Here is some more that I have learned:
The DSL signal is transmitted over the same pair of wires that is used for
one of your existing telephone numbers. It is a high frequency signal that
was designed to not interfere with standard telephone equipment that you
already have plugged in. However there have been some problems afterall and
this can be solved by using a splitter or filter. The splitter gets installed
where the phone line enters the house and a new phone line gets run to the
location where the DSL modem will be connected. The other option, the filter,
instead is connected to every telephone device in the house and protects each
individual device by filtering out the DSL signals before they get to your
phone. These "microfilters" are simply plugged into the telephone jack where
your phone normally connects and then you plug the phone into the filter.
There is a separate version for wall mount phones. Since installing a splitter
requires that a US West person come to your house to install the splitter and
run the new telephone line for your DSL modem, this is expensive for US West.
For this reason, they are instead giving you enough "microfilters" to use
on all your phone devices instead. I personnally don't like this solution for
a couple of reasons. First of all, I see these as easily getting lost or
broken (especially with kids). Secondly, what do I do when I get a new phone,
or move a phone, or someone brings over their laptop and wants do dialup
somewhere? Lastly, see the next section. Currenly US West is offering
the microfilters as the only option.
We use a Radio Shack intercom at our house that uses the phone line instead
of other wired or wireless technologies. I called netspeed, the makers of
the modems to see if this might interfere with the DSL signal. They actually
went out and bought one to test and found out that it would indeed interfere
with the DSL signal. Putting microfilters on each one would eliminate the
interference, but would prevent the intercoms from working as well. I am now
trying to get a splitter from NetSpeed, because US West is not selling them.
NetSpeed is not set up for retail sales, so it is not necessarilly going to
be easy. My fallback is to use a microfilter in place of the splitter. It
will not be as "neat", but should work just as well.
DSL is initially being rolled out using a bridged rather than routed
environment. This may be a security issue, since in a bridged environment,
you may see other peoples traffic on your net. US West says that this should
not be a problem, it is being filtered someplace. I'm not taking there word
for it though. I'll let you know.
DSL is also using DHCP (dynamic IP addresses) initially. This will make
it difficult to put up a web site or other such services at home, since the IP
address of the system may change. I am going to try to use some scripts to
update DNS whenever the IP address changes, but am not real confident of this.
Static IP addresses are supposed to be available in Jun/Jul, but there is
commitment to this and it is unknown if that will cost extra.
You are only assigned a single dynamic address, so if you have a network
at home, you will need to do either proxy, or NAT (network address translation)
to get other systems to be able to use the network. NAT can be difficult in
a DHCP environment.
The DSL modem itself will be supporting NAT in the Jun/Jul release, but this
will only work when the modem is operated in a routed rather than the initial
bridged environment. The modem also supports packet filters now, but again
this is only good in a routed environment. US West may switch to a routed
environment when it offers static IP addresses, but this is also speculation.
I will be trying to use a Sun workstation as the DSL client. This is
totally unsupported by US West, and if needed I will fall back to an NT system
which is supported. I think I can make the Sun work though. I will be
attempting to use both NAT and packet filters with this link. Again difficult
in a DHCP environment, but we will see.
The connection between the DSL modem and the PC is a network connection
rather than a serial connection. This requires the installation of a network
card in the PC (or whatever) that connects to the DSL modem. This is why
someone from MicroAge is coming out to do the installation. Most DSL users
will not know how to do this. If you know who to do, or already have it, there
may be an installation cost price break, but I can't find out for sure. In
any case, while I already have network cards installed, having someone who
knows what telephone numbers to call if there is a problem will be good to
have for my install. Especially being only the second person in the area!
The network connection between the DSL modem and the PC will be a
10baseT crossover cable. There is no reason why a hub and standard straight
cables could not be used instead. It is an open question what would happend
if two computers where attached in this fashion to the DSL modem and both
requested DHCP addresses. I will test this and let you know ;-).
That's all for now,
--
----------------------------------------------------------------------------
John R. DeWolfe email : John.DeWolfe at dewolfe.com
DeWolfe Enterprises voice : (303) 722-4461
From isuhrstedt at netspeed.com Fri May 8 09:19:08 1998
Return-Path:
Received: from gatekeeper-r90.dewolfe.com by alpha.dewolfe.com. (SMI-8.6/SMI-SVR4)
id JAA10816; Fri, 8 May 1998 09:19:06 -0600
Received: from nsexc01.netspeed.com ([12.5.168.239])
by gatekeeper-r90.dewolfe.com (8.8.8/8.8.8) with ESMTP id JAA24359
for ; Fri, 8 May 1998 09:18:43 -0600 (MDT)
Received: by NSEXC01 with Internet Mail Service (5.0.1457.3)
id ; Fri, 8 May 1998 10:16:03 -0500
Message-ID: <18EBC826ABCAD111959400A0C995135002C2EE at NSEXC01>
From: Ian Suhrstedt
To: "'John.DeWolfe at dewolfe.com'"
Subject: RE: Radio Shack Intercom
Date: Fri, 8 May 1998 10:16:01 -0500
X-Priority: 3
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1457.3)
Content-Type: text/plain
Content-Length: 848
Status: OR
John,
I talked with USWEST about getting you a tabletop POTS splitter.
They informed me that you need to order that directly from us. I have a
contact for you but he is researching the accounting procedures and
sales prices for selling those direct. I should have an answer by
Monday. In any case, the USWEST person I was talking to indicated that
there are two choices for installation: 1) USWEST sends someone to hook
up the SpeedRunner and/or ethernet card if necessary, and charges you
for the install, or 2) they drop-ship the router and microfilters and
you install it yourself. I think I know which option you'll choose...
I'll get you more info on Monday.
Ian
=================
Ian Suhrstedt
Customer Service Engineer
Cisco Systems - Austin (formerly NetSpeed)
isuhrstedt at netspeed.com
phone: 800.550.2375 x3143
pager: 512.624.0987
From isuhrstedt at netspeed.com Fri May 15 10:34:56 1998
Return-Path:
Received: from gatekeeper-r90.dewolfe.com by alpha.dewolfe.com. (SMI-8.6/SMI-SVR4)
id KAA21834; Fri, 15 May 1998 10:32:04 -0600
Received: from nsexc01.netspeed.com ([12.5.168.239])
by gatekeeper-r90.dewolfe.com (8.8.8/8.8.8) with ESMTP id KAA02995
for ; Fri, 15 May 1998 10:31:31 -0600 (MDT)
Received: by NSEXC01 with Internet Mail Service (5.0.1457.3)
id ; Fri, 15 May 1998 11:28:47 -0500
Message-ID: <18EBC826ABCAD111959400A0C995135002C31C at NSEXC01>
From: Ian Suhrstedt
To: "'John.DeWolfe at dewolfe.com'" ,
Tech Support
Cc: john at alpha-r3.dewolfe.com
Subject: RE: US West confusion about DSL modems
Date: Fri, 15 May 1998 11:28:44 -0500
X-Priority: 3
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1457.3)
Content-Type: multipart/mixed;
boundary="---- =_NextPart_000_01BD7FF4.A040C8F0"
Content-Length: 509116
Status: OR
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------ =_NextPart_000_01BD7FF4.A040C8F0
Content-Type: text/plain;
charset="iso-8859-1"
In an effort to make these questions on DSL modem abilities go away:
The information in your e-mails below is correct. The 202 and
204 will both route or bridge. They can only do one or the other at a
time but no hardware mods are necessary in the SpeedRunner to make it do
either. Release 2.0 in the late July timeframe (firmware update only)
will have new features including NAT. The PCI card only acts as a
router (bridging will be implemented in the future). The 202 and 204 in
routing mode have the same features, including basic IP filtering. In
bridge mode, the 202/204 basically connects the ethernet port directly
to the ADSL port (simplified explanation) and pretty much acts like a
wire that just passes all data through without examining it.
In addition, both the 202 and 204 support up to 4 virtual WAN
connections, so you could hook up to your ISP and work or anywhere else
you have an account you can access.
Here is a marketing doc on the 204.
Hopefully this clears up some confusion,
Ian
=================
Ian Suhrstedt
Customer Service Engineer
Cisco Systems - Austin (formerly NetSpeed)
isuhrstedt at netspeed.com
phone: 800.550.2375 x3143
pager: 512.624.0987
> -----Original Message-----
> From: John.DeWolfe at dewolfe.com [SMTP:John.DeWolfe@dewolfe.com]
> Sent: Friday, May 15, 1998 10:47 AM
> To: support at netspeed.com
> Cc: john at alpha-r3.dewolfe.com
> Subject: US West confusion about DSL modems
>
> Forwarded message:
> From john Thu May 14 11:59:29 1998
> From: john (John R. DeWolfe)
> Message-Id: <199805141759.LAA12504 at alpha.dewolfe.com.>
> Subject: Re: #2 DSL install in Denver!
> To: dsl, john (John R. DeWolfe)
> Date: Thu, 14 May 1998 11:59:12 -0600 (MDT)
> In-Reply-To: <199805141649.KAA21548 at zek.co.symbios.com> from "Quentin
> Johnson" at May 14, 98 10:49:48 am
> X-Mailer: ELM [version 2.4 PL23]
> MIME-Version: 1.0
> Content-Type: text/plain; charset=US-ASCII
> Content-Transfer-Encoding: 7bit
> Content-Length: 2955
>
> This question about Netspeed DSL modem capabilities just won't go
> away.
> At two separate seminars on DSL, US West representives have said that
> the
> cheap Netspeed modem can only act as a bridge. Even some local ISP's
> that
> want to deploy DSL are saying this as well. Ian and others in
> Netspeed
> tech support have told me this is not true. What they have said is
> that
> the model 204 can act as either a bridge or a router. US West is
> initially
> deploying this in a bridge mode, but the modems being deployed today
> by
> US West can be reconfigured from bridge to router mode with no
> hardware
> changes. Netspeed has also told me that release 2.0 firmware was
> coming out
> in the Jun/Jul timeframe. This firmware would add some additional
> capabilities to the existing router capabilities of the 204 modem.
> One such
> enhancement is Network Address Translation. This upgrade is a
> firmware
> only upgrade and does not require new hardware, and can be done by
> simply
> downloading the new firmware to the modem. I've also been told that
> the
> existing 204 as deployed by US West also supports basic packet
> filtering
> when operated in router mode. No NAT, filtering, etc. is possible
> when
> operated in bridge mode.
>
> Is there any chance at all that US West is deploying some special
> version
> of the 204 that only has bridging capabilities? Something that would
> allow
> them to sell it for $300 instead of $900? See the messages below to
> see
> what I mean by this.
>
> Can you please confirm the information as I have stated it above?
> If you
> could do this via email, I will diseminate this as needed to try to
> correct
> the bad information out there. If there is ANYTHING that is not
> correct
> in what I said above (or below), please, let me know.
>
> Thanks,
> John DeWolfe
> 303-818-7752
>
> >
> > According to US West:
> >
> > They're using 3 different boxes on the subscriber end: a PCI bus
> card,
> > a bridge, or a router. The bridge is the $300 box and they can
> download
> > software to it. I'm pretty curious about the details of that thing.
> The
> > router would be nice to have but I think, its $900. The stuff is
> made
> > by Netspeed, which Cisco just bought. I doubt USWest can answer
> about
> > details of the hardware, but Cisco and Netspeed have good web sites
> :-)
> >
> I am going to have to reconfirm with NetSpeed, but NetSpeed told me
> on
> several occations that the $300 (model 202/204) CAN do both routing
> and
> bridging.. US West is doing bridging initially. Maybe the confusion
> is over
> what exactly "routing" means. I'm not sure what US West had in mind,
> but
> when operated in "routing" mode, the 202/204 can do packet filtering,
> network
> address translation, etc. In bridge mode, it cannot do any of that.
> I'll
> reconfirm again with netspeed on this. But that is what both
> technical
> support and the product manager told me on several different
> occations. They
> also told me that the 204 has exactly the same functionallity of the
> 202, but
> is cheaper to make (and consequently to sell).
>
> > The USWest person said that initially your ADSL connection is just a
> point-to-
> > point, but soon they'll offer (for more money) the option for you to
> switch
> > between 4 different connections - that would be nice if I had an ISP
> and
> > a work connection.
> >
> That is cool. I had not heard of that. Don't have an immediate
> use for it,
> but you never know.
>
> > I want to know whether I can get to my home system from other
> places. Indra's
> > Net is going to assign static IP addresses but they're concerned
> about people
> > setting up web servers and killing their bandwidth.
> >
> > If USWest is using DHCP, that poses a problem. In the past I've had
> > my machine email me (at work) its IP address when the PPP connection
> comes
> > up. That's good enough for now, but someday I might want to let
> others
> > access my home network.
> >
> This is a big deal for me. US West is supposedly rolling out
> static IP
> addresses in Jun/Jul. Until then, I will be working on dynamically
> updating my
> DNS server every time my IP address changes. I have a DNS server
> under my
> control that is located elsewhere with a static IP address, so this
> will work
> for me. I could proably do other domains to if needed. I'll have to
> set the
> timeout to something like 20 minutes to make this work, but is better
> than
> nothing. I heard a rumour that, at least initially, US West was going
> to
> force renewels every 24 hours. It gets more complicated because I
> will also
> try to dynamically update my firewall with the same new IP
> information!
> Talk about looking for trouble! :-)
>
> --
> ----------------------------------------------------------------------
> ------
> John R. DeWolfe email : John.DeWolfe at dewolfe.com
> DeWolfe Enterprises voice : (303) 722-4461
>
>
> --
> ----------------------------------------------------------------------
> ------
> John R. DeWolfe email : John.DeWolfe at dewolfe.com
> DeWolfe Enterprises voice : (303) 722-4461
------ =_NextPart_000_01BD7FF4.A040C8F0
Content-Type: application/msword;
name="SpeedRunner204.doc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="SpeedRunner204.doc"
(Document deleted for Web posting)
------ =_NextPart_000_01BD7FF4.A040C8F0--
From quentinj at zek.co.symbios.com Fri May 15 16:59:35 1998
Return-Path:
Received: from gatekeeper-r90.dewolfe.com by alpha.dewolfe.com. (SMI-8.6/SMI-SVR4)
id QAA24674; Fri, 15 May 1998 16:59:34 -0600
Received: from mpdgw2.symbios.com (mpdgw2.symbios.com [204.131.200.2])
by gatekeeper-r90.dewolfe.com (8.8.8/8.8.8) with SMTP id QAA03192
for ; Fri, 15 May 1998 16:59:31 -0600 (MDT)
Received: (from root at localhost) by mpdgw2.symbios.com (8.6.8.1/8.6.6) id QAA07172 for ; Fri, 15 May 1998 16:58:59 -0600
Received: from aztec.co.symbios.com(153.72.199.214) by mpdgw2.symbios.com via smap (V1.3)
id sma006963; Fri May 15 16:58:35 1998
Received: from zek.co.symbios.com (root at zek.co.symbios.com [153.72.240.235]) by Symbios.COM (8.6.8.1/8.6.6) with ESMTP id QAA23691 for ; Fri, 15 May 1998 16:58:33 -0600
Received: from zek (quentinj at localhost [127.0.0.1]) by zek.co.symbios.com with ESMTP (8.7.6/8.7.1) id QAA26647 for ; Fri, 15 May 1998 16:57:40 -0600 (MDT)
Message-Id: <199805152257.QAA26647 at zek.co.symbios.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: John.DeWolfe at dewolfe.com (John R. DeWolfe)
Subject: Re: US West confusion about DSL modems (fwd)
In-Reply-To: Message from John.DeWolfe at dewolfe.com (John R. DeWolfe)
of "Fri, 15 May 1998 16:29:50 MDT." <199805152229.QAA24471 at alpha.dewolfe.com.>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 15 May 1998 16:57:40 -0600
From: Quentin Johnson
Content-Length: 325
Status: OR
Interesting. Thanks for forwarding the info.
That doc they included only showed the PCI card and the router.
At the RMIUG meeting, the US west person showed a photo of those
and a 3rd gadget, about the size of a modem, which I understood to
be the bridging device. It must have been the 202.
Have a great weekend!
Quent
From barb at netrack.net Fri May 15 19:35:18 1998
Return-Path:
Received: from gatekeeper-r90.dewolfe.com by alpha.dewolfe.com. (SMI-8.6/SMI-SVR4)
id TAA25765; Fri, 15 May 1998 19:35:16 -0600
Received: from netrack.net (windom.netrack.net [206.168.112.49])
by gatekeeper-r90.dewolfe.com (8.8.8/8.8.8) with ESMTP id TAA03242
for ; Fri, 15 May 1998 19:34:34 -0600 (MDT)
Received: (from barb at localhost)
by netrack.net (8.8.8/8.8.5) id TAA08282;
Fri, 15 May 1998 19:43:23 -0600 (MDT)
Date: Fri, 15 May 1998 19:43:23 -0600 (MDT)
From: Barb Dijker
Message-Id: <199805160143.TAA08282 at netrack.net>
To: John.DeWolfe at dewolfe.com, dsl@alpha-r3.dewolfe.com
Subject: RE: US West confusion about DSL modems (fwd)
Cc: jdewolfe at mediaone.com
Content-Length: 9
Status: OR
Thanks!!
From isuhrstedt at netspeed.com Fri May 15 10:12:11 1998
Return-Path:
Received: from gatekeeper-r90.dewolfe.com by alpha.dewolfe.com. (SMI-8.6/SMI-SVR4)
id KAA21693; Fri, 15 May 1998 10:12:09 -0600
Received: from nsexc01.netspeed.com ([12.5.168.239])
by gatekeeper-r90.dewolfe.com (8.8.8/8.8.8) with ESMTP id KAA02970
for ; Fri, 15 May 1998 10:12:06 -0600 (MDT)
Received: by NSEXC01 with Internet Mail Service (5.0.1457.3)
id ; Fri, 15 May 1998 11:09:28 -0500
Message-ID: <18EBC826ABCAD111959400A0C995135002C31B at NSEXC01>
From: Ian Suhrstedt
To: "'John.DeWolfe at dewolfe.com'"
Subject: RE:POTS splitter
Date: Fri, 15 May 1998 11:09:27 -0500
X-Priority: 1
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.0.1457.3)
Content-Type: text/plain
Content-Length: 2229
Status: OR
We can get you the splitter, but I don't know if it can make it by
Monday. The price for the tabletop pots splitter is $70. I'm working
on getting shipping info to see if we can make it by Monday. Here's the
info we'll need to sell it directly to you via credit card:
-Credit Card #
-Expiration Date
-Name on Card
-Shipping Address
-Billing Address for Credit Card
You can either reply to this e-mail with the info or call me. Let me
know if you are still interested as soon as possible. Thanks
Ian
=================
Ian Suhrstedt
Customer Service Engineer
Cisco Systems - Austin (formerly NetSpeed)
isuhrstedt at netspeed.com
phone: 800.550.2375 x3143
pager: 512.624.0987
> -----Original Message-----
> From: John.DeWolfe at dewolfe.com [SMTP:John.DeWolfe@dewolfe.com]
> Sent: Friday, May 15, 1998 10:51 AM
> To: isuhrstedt at netspeed.com
> Subject: Re: Radio Shack Intercom
>
> >
> > John,
> > I talked with USWEST about getting you a tabletop POTS splitter.
> > They informed me that you need to order that directly from us. I
> have a
> > contact for you but he is researching the accounting procedures and
> > sales prices for selling those direct. I should have an answer by
> > Monday. In any case, the USWEST person I was talking to indicated
> that
> > there are two choices for installation: 1) USWEST sends someone to
> hook
> > up the SpeedRunner and/or ethernet card if necessary, and charges
> you
> > for the install, or 2) they drop-ship the router and microfilters
> and
> > you install it yourself. I think I know which option you'll
> choose...
> > I'll get you more info on Monday.
> >
>
> Hi Ian,
>
> I have been gone to a conference all week. What is the status of
> getting
> the splitter from Netspeed? My line goes in Mon, May 18th. That is
> in
> three days! Any chance of getting this splitter by then? I can
> always put
> it in later, but would be easier if I didn't have to rewire a second
> time.
>
> Please let me know,
> John DeWolfe
> 303-818-7752
>
> --
> ----------------------------------------------------------------------
> ------
> John R. DeWolfe email : John.DeWolfe at dewolfe.com
> DeWolfe Enterprises voice : (303) 722-4461
From john Mon May 18 22:16:35 1998
Return-Path:
Received: by alpha.dewolfe.com. (SMI-8.6/SMI-SVR4)
id WAA20069; Mon, 18 May 1998 22:16:20 -0600
From: john (John R. DeWolfe)
Message-Id: <199805190416.WAA20069 at alpha.dewolfe.com.>
Subject: INSTALL DAY!
To: dsl
Date: Mon, 18 May 1998 22:16:20 -0600 (MDT)
Cc: john (John R. DeWolfe)
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 9424
Status: O
Mon May 18 20:12:57 MDT 1998
Today is the day for my DSL install. Someone from MicroAge was supposed to
come by at 9am this morning. They didn't show, but about 9:30 I got a call
saying that there was some big meeting the installers had to be at and he
would be by about 1pm. About 1:30pm I got another call, the installer was
trying to get a login and password for my account and was having a difficult
time getting it from US West. He said about another 1/2 hour. About 2:15
he called again and said that he had finally received the information, but
he was actually working on someone elses and having problems and would be
a while. The problems seemed be US West DHCP server related. About 3:30 I
got another call, saying there were still problems and he wasn't sure if
could actually make it, but was going to try. About 4:30, I got yet another
call from the installer, but lo and behold he was actually calling from my
front porch! He was just verifying he had the right address. There were
actually two people, Paul Baker and Tom somebody. It was Tom's first day.
They had the modem with them as well as cables, network card, etc. The
modem turned out to be the old model 202, not the newer 204. I was told that
the 204 wasn't actually available yet and US West was installing 202's until
the 204's were available. Netspeed had told me they were identical
functionally, so I wasn't to concerned, but it is considerably bigger (about
the size of a big hard-back book, like the new Joy of Cooking) and didn't
fit where I had planned. I quickly found another spot though and hooked it
up. The installed also had a bunch of micro-filters, but I just took one and
put into a spot I had prepared where the phone line enters the house, so that
I could just use one for the whole house. The filter worked like a champ.
It is about 2x1x1/2 and has two female RJ-11 jacks as well has a 2 inch male
male phone cable.
After putting in the filter, placing the modem, attaching the phone line,
connecting at patch cable from the modem two the hub where I had plugged in
my Sun, and attaching a serial cable used for configuration, we were ready.
He had brought a cross-over 10baseT patch cable, but I preferred my hub.
The serial connector is a female DB9 and the modem comes with a M-DB9 to F-DB9
which can plug directly into a standard PC serial port. The installer brought
a laptop, plugged the cable in, brought up HyperTerm under win95, set baud to
9600, hit enter and had a login prompt. He logged in as root, was prompted
for a password, hit enter (no password by default), and was at a command
prompt. He then changed the configuration from router mode to bridge mode
using commands that I didn't catch, and was done configuring. We power-cycled
the modem and we had Wan connectivty! The modem has 5 indicator lights:
power, WAN link, WAN data activity, LAN link, and LAN data activity. Both
the WAN link and LAN link lights were on. I had already setup my Sun to
be a DHCP client, so we should have been in business. No go though. No DHCP
address was assigned. After snooping the line for a while, it was obvious
that the DHCP server was just not responding. There was not network activity
of any kind as shown by both snoop and the WAN/LAN activity lights. The
only packets were DHCP broadcasts from my Sun and some sort of RIP query from
the modem when it was first turned on. (Don't know what that is, but since
I don't like RIP, I need to look at that). I tried several things, including
using a PC instead of my Sun, but to no avail. The good news was that
because we had a WAN link light, the DSL transport was working correctly at
least. Essentially, the network was operational, but the server was down.
I forgot to mention that there were two pieces of configuration information
for my computer that the installer brought with him:
1) DNS server information. Hostname (mdewolfe), two DNS server IP addresses,
and a domain (uswest.net). Why this isn't handled via DHCP, I don't know. I
suspect the hostname is based on US West telephone account information. My
wife (Michele) appears first, so I think thats where the "m" in "mdewolfe"
came from. I'm going to check more into the hostname. Mine already have
hostnames and I would prefer to keep my own. Maybe a DNS CNAME...
2) username and password. The username was the same as the hostname. The
password was , (sorry the password has been automatically deleted for security
reasons). I am not sure what these are for. It may be for some accounting
web page, for some sort of unknown sign on, your guess is as good as mine.
At this point, the MicroAge guy got on the phone and after about 20 minutes,
said that Interact, (US West's Internet branch? I know my work gets its
Internet connectivity through Interact) was down. Now if all of Interact was
down, my pager would have been going off from work like crazy, so I am sure
just some DSL piece of it was not working correctly. There was nothing more
for the MicroAge people to do at this point. They said that there was nothing
else that needed to be configured at my end and that if the Interact DHCP
server came up, I should get an IP address automatically and things should
just start working. I couldn't think of anything else either, so they left.
They did leave several microfilters as well as a modem manual (had to ask for
that, it had been left in the car), and information on !nterprise, MegaBit,
etc.
At about 6:30pm, I got a call from "Bob" who was with US West (not MicroAge)
and he was calling to apologise for not getting out here to install my modem!
I told him that people from MicroAge had already been out and it was all
installed, but we were not getting a DHCP address. He said "great!" (one less
thing for him to do I suppose) and then asked what problems we were having.
I told him we had LAN/WAN link lights, but not addresses. He said that there
was a problem with the server at Interact and then gave me all of the following
sometimes mutually exclusive reasons why it was down:
1) The server had an ATM DS3 connection, but was actually connected to a
T1. Signalling mismatches between the two were causing:
a) connectivity slowdowns
b) total outage
2) The server was connected via a T1 instead of a DS# and with all of the
traffic from current DSL users being forced through such a small pipe, the
server couldn't respond to my (and other) DHCP requests.
3) Part of the server was not responding to DHCP requests, which is why some
DSL users had connectivity, but others didn't.
I asked when it would be back up/straightened out and he said hopefully
tomorrow, but may be a couple of days. He then volunteered to call me every
evening with a status report until it was operational again! I then asked
him some DHCP questions, and had told me the following:
US West is initially setting the DHCP lease time at 4 hours, with the server
doing a lease check at 2 hours. If you leave your computer on all the time,
you should be able to keep your IP address for an extended period of time.
From all of the above, I deduced the following information:
US West is using one or more DS3's to connect to the Internet in
the Denver area.
US West is funneling ALL DHCP requests to a possibly single server
located at the US West Interact facility in (Broomfield?).
The short DHCP lease time may indicate a shortage of IP addresses in
the DHCP pool, or a possible need for many DHCP changes during this
first roll out.
Purely guess work on my part.
So, I am now in a wait and see mode. All in all it boils down to this:
The good news is that EVERYONE I have dealt with so far has been extremely
friendly and helpful (at least within there knowledge base). They have also
been extrordinarily communicative. To get 4 phone calls from the installer
over the course of the day as opposed to the usual none is way beyond my
normal experience. Also to have the US West guy offer to call me every
evening with an update is also amazing. Also good news is the ease of
installation. No special drivers, adapters, wiring, etc. If the server
had been working, it really could have been a ship to me, plug it in, and it
works installation.
The bad news is that nobody still really understands what is going on and
what all the players are. The MicroAge people had had several installations
today (I guess I wasn't really 2nd in Denver) that all failed like mine.
However it wasn't until my installation that they found out that Interact
was down. In fact one of the installers said something that led me to
believe Interact had actually stopped working on Sat. This leads to the
next obvious bad news, things are a long way from stable, and internal
US West communications, must less escallation policies are obviously lacking.
I kind of expected that here in the beginning, but possibly 4 days of down
time on a critical server sounds a bit excessive. It also means redundancy
is apparently lacking as well.
Well enough of this novel for tonight. I'll keep you up to date on what
happens. I may try to write a script to page me when the line becomes active.
Good night,
--
----------------------------------------------------------------------------
John R. DeWolfe email : John.DeWolfe at dewolfe.com
DeWolfe Enterprises voice : (303) 722-4461
From john Wed May 20 00:31:08 1998
Return-Path:
Received: by alpha.dewolfe.com. (SMI-8.6/SMI-SVR4)
id AAA22126; Wed, 20 May 1998 00:27:59 -0600
From: john (John R. DeWolfe)
Message-Id: <199805200627.AAA22126 at alpha.dewolfe.com.>
Subject: DSL Working!
To: dsl
Date: Wed, 20 May 1998 00:27:59 -0600 (MDT)
Cc: john (John R. DeWolfe)
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 5461
Status: O
Tue May 19 23:54:00 MDT 1998
DSL is working! Someone from US West came to the house about 4pm today
to troubleshoot the connection. They tried troubleshooting at my house.
First they tried there own laptop rather than my Sun. Next they got a new
modem and tried that. Next they took the laptop and the new modem outside
and plugged into the DI on the outside of the house (to eliminate inside
wireing problems). This didn't work so they took everything to the CO (which
turns out to be located about 5 blocks from my house). I talked them into
letting me go along! In the CO they tried it again and still had the same
problem (no DHCP assigned IP addresses). They finally figured out that the
switch for my DSL connection had been turned off! Turned out that several
CO's had not been configured properly for DSL and US West had been fixing that
earlier today. After doing that though, they still had a problem with one CO.
They started turning off DSL lines trying to isolate the problem. It finally
turned out to be a bad DSL card which they replaced. This fixed the problem,
but they had forgotton to turn my DSL connection back on. After turning on
the connection, it all started working!
My Sun immediately acquired an IP address and I was off and running!
Several test file transfers via FTP yielded consistent 45-55Kbytes/sec
transfer rates. Web browsing is MUCH faster. I love it!
The vice president of network operations was along on this call to find
out what was happeing in the field. He was very friendly and had some
knowledge of how things were setup. Here are some gleanings from our
conversations:
1) Doesn't know when the model 204 modems will be available.
2) Will probably be switching from (CAP?) to (DMT?) dsl technology sometime
this year. He said that (DMT?) was becoming more of an industry standard.
3) If they switched to DMT and the netspeed modems could not be upgraded to
DMT (NetSpeed is being slow in this area), US West would replace the existing
modems with the correct ones for free! Since we actually buy these modems,
rather than rent, or lease, this is good news. I was worried about being
stuck with obsolete technology.
4) A CO handles about a 10mile diameter circle of houses.
5) Current limitations on distance are about 3 miles from the CO. Internal
testing has shown they can go considerably farther but can't guarantee
results.
6) They are working on testing and deploying a fiber version of DSL. This
will dramatically increase the distance it can be run.
7) Everything currently is routed through Interact in Thorton, not Broomfield
like I thought earlier.
8) Even though it is a bridged environment, packets from adjoining DSL modems
never mix and do not show up on your local or somebody elses DSL line.
9) They are using DS3's between CO's and Thorton. They are working on
upgrading this to a Sonet ring. Faster and better reliability.
10) Demand is high!
11) DSL is way cheaper than ISDN to deploy. ISDN waits for installation are
mainly due to not being able to get ISDN equipment from Lucent Technologies
fast enough.
12) He wants to get to the point where it is all on a single PC card that
comes with the PC when you buy it. No more external modems with network
issues. Told him that would be a problem for those of us not using a PC.
Some of us need external modems!
13) If you leave your equipment on, the DHCP address should remain fairly
static.
14) He said there were NO current time frames for static IP addresses. This
is a direct contrast to a Sales rep who had said July.
*****
This is what my DHCP address looked like:
le1: flags=4843 mtu 1500
inet 206.196.151.69 netmask ffffff00 broadcast 206.196.151.255
# ifconfig le1 dhcp status
Interface Status Sent Received Rejects
le1 RENEWING 4 0 0
(Began,Expires,Renew) = (05/19/1998 22:14, 05/20/1998 02:14, 05/20/1998 00:14)
I am also seeing some weird packets coming in on the DSL line addressed to
me:
output from my ip_filter firewall of blocked packets:
19/05/1998 23:48:19.007770 le1 at 0:9 b 169.152.79.3,39332 -> 206.196.151.69,113 PR tcp len 20 44 -S
20/05/1998 00:14:13.670936 le1 at 0:9 b 172.16.2.180,67 -> 206.196.151.69,68 PR udp len 20 341
20/05/1998 00:14:17.537278 le1 at 0:9 b 172.16.2.180,67 -> 206.196.151.69,68 PR udp len 20 341
20/05/1998 00:14:25.447760 le1 at 0:9 b 172.16.2.180,67 -> 206.196.151.69,68 PR udp len 20 341
20/05/1998 00:14:41.449989 le1 at 0:9 b 172.16.2.180,67 -> 206.196.151.69,68 PR udp len 20 341
These are bootp type packets. No idea who 169.152.79.3 or 172.16.2.180 are.
Reverse DNS is apparently not working for my assigned IP address.
I just got a "dhcpagent[9020]: DHCP renewal on le1 failed" message. I wonder
if the bootp is some sort of DHCP renewal query?
Experimenting shows that the 172 addresses are indeed DHCP related. I allowed
these through and was able to renew my DHCP address. When I released the
address and then asked for a new one, I did get the same address again. Good
news as well. Some DHCP servers will try to allocate the same one allocated
before. Maybe US West is doing something similar.
Time for bed!
--
----------------------------------------------------------------------------
John R. DeWolfe email : John.DeWolfe at dewolfe.com
DeWolfe Enterprises voice : (303) 722-4461
From john Thu May 21 13:27:32 1998
Return-Path:
Received: by alpha.dewolfe.com. (SMI-8.6/SMI-SVR4)
id NAA24444; Thu, 21 May 1998 13:27:29 -0600
From: john (John R. DeWolfe)
Message-Id: <199805211927.NAA24444 at alpha.dewolfe.com.>
Subject: DSL network questions
To: haustin at uswest.net
Date: Thu, 21 May 1998 13:27:29 -0600 (MDT)
Cc: john (John R. DeWolfe)
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 5509
Status: O
Thu May 21 12:46:41 MDT 1998
Hi,
I spoke with you on the phone about some DSL questions and you asked that
I email them to you. DSL is new to all of us and I am not sure where to
get these types of questions answered. Here is my list:
1) Can you setup forward and reverse DNS for your DSL customers? Currently
there is not a reverse DNS lookup at least for my DHCP assigned address
(206.196.151.69). There are man FTP sites on the net that require at
minimum an IP address be mapped into a hostname (reverse DNS lookup). There
are others that require that the IP address be mapped to a hostname AND the
hostname be mapped to the same IP address (forward DNS lookup). An example
session to an FTP site that requires at least the reverse follows:
nemesis% ftp vic.cc.purdue.edu
Trying to connect to vic.cc.purdue.edu...
User [anonymous]: ftp
The name server used by vic.cc.purdue.edu cannot convert your network
address to a host name. Therefore, vic.cc.purdue.edu will not accept
your connection request. Consult your DNS provider about why reverse
lookup does not work for your address.
Even without having proper DNS reverse lookup, you may be able to get
lsof from one of these mirror sites:
ftp://coast.cs.purdue.edu/pub/tools/unix/lsof
ftp://ftp.auscert.org.au/pub/mirrors/vic.cc.purdue.edu/lsof
.
.
.
ftp://wuarchive.wustl.edu/packages/security/lsof
User ftp access denied..
This particular site does offer alternative FTP sites, but not all do.
2) Can I read my pop based email from non-uswest.net locations. For instance
can I read my email from work which is connected to the Internet via different
ISP?
3) Does US West offer any kind of web proxy server. These can help customers
retrieve files faster if they have already been cached from some other queiry,
and also cut down on traffic out to the Internet saving you bandwidth. This
is common in the ISP world. Someone already said you do not offer this, but
thought I would ask again to be sure.
4) Does you offer any NTP (network time protocol) servers I can sync my system
to. Cisco routers can all be configured as NTP servers and can be used for
this. If you do offer NTP, can you give me the IP address(s) to use?
5) Do you offer news servers? What name or IP address would I use for this.
6) Do you offer news feeds? If so, who do I contact about getting that set
up?
7) DHCP can be used to supply many different network related configuration
parameters besides an IP address. I am actually using a Sun workstation to
connect to my DSL modem and would like to find out which of these uswest.net
is currently supporting: The standard DHCP list of available parameters
includes:
I am particularly interested in Subnet, DNSserv, NTPservs, IpFwdF, & Broadcst.
(from Unix man page on "dhcptab" on Sun Solaris 2.6)
Symbol Code Description
Subnet 1 Subnet Mask, dotted Internet address (IP).
UTCoffst 2 Coordinated Universal time offset (seconds).
Router 3 List of Routers, IP.
Timeserv 4 List of RFC-868 servers, IP.
IEN116ns 5 List of IEN 116 name servers, IP.
DNSserv 6 List of DNS name servers, IP.
Logserv 7 List of MIT-LCS UDP log servers, IP.
Cookie 8 List of RFC-865 cookie servers, IP.
Lprserv 9 List of RFC-1179 line printer servers, IP.
Impress 10 List of Imagen Impress servers, IP.
Resource 11 List of RFC-887 resource location servers, IP.
Hostname 12 Client's hostname, value from hosts database.
Bootsize 13 Number of 512 octet blocks in boot image, NUMBER.
Dumpfile 14 Path where core image should be dumped, ASCII.
DNSdmain 15 DNS domain name, ASCII.
Swapserv 16 Client's swap server, IP.
Rootpath 17 Client's Root path, ASCII.
ExtendP 18 Extensions path, ASCII.
IpFwdF 19 IP Forwarding Enable/Disable, NUMBER.
NLrouteF 20 Non-local Source Routing, NUMBER.
NLrouteF 20 Non-local Source Routing, NUMBER.
PFilter 21 Policy Filter, IP,IP.
MaxIpSiz 22 Maximum datagram Reassembly Size, NUMBER.
IpTTL 23 Default IP Time to Live, (1==68, NUMBER.
SameMtuF 27 All Subnets are Local, NUMBER.
Broadcst 28 Broadcast Address, IP.
MaskDscF 29 Perform Mask Discovery, NUMBER.
MaskSupF 30 Mask Supplier, NUMBER.
RDiscvyF 31 Perform Router Discovery, NUMBER.
RSolictS 32 Router Solicitation Address, IP.
StaticRt 33 Static Route, Double IP (network router).
TrailerF 34 Trailer Encapsulation, NUMBER.
ArpTimeO 35 ARP Cache Time out, NUMBER.
EthEncap 36 Ethernet Encapsulation, NUMBER.
TcpTTL 37 TCP Default Time to Live, NUMBER.
--
----------------------------------------------------------------------------
John R. DeWolfe email : John.DeWolfe at dewolfe.com
DeWolfe Enterprises voice : (303) 722-4461
From john Thu May 21 14:16:19 1998
Return-Path:
Received: by alpha.dewolfe.com. (SMI-8.6/SMI-SVR4)
id OAA24591; Thu, 21 May 1998 14:16:07 -0600
From: john (John R. DeWolfe)
Message-Id: <199805212016.OAA24591 at alpha.dewolfe.com.>
Subject: DSL DHCP answers
To: haustin at uswest.net
Date: Thu, 21 May 1998 14:16:07 -0600 (MDT)
Cc: dsl, john (John R. DeWolfe)
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 705
Status: O
Thu May 21 14:11:58 MDT 1998
Through testing, I found out that US West is supplying the following
parameters via DHCP: (These are of course for my system)
Subnet
255.255.255.0
Router
206.196.151.254
DNSserv
206.80.192.1
206.196.128.1
DNSdmain
dnvr.uswest.net
Broadcst
206.196.151.255
LeaseTim
14400
T1Time
7200
T2Time
12600
The rest of the possible parameters are not currently being supplied.
Thanks,
John DeWolfe
--
----------------------------------------------------------------------------
John R. DeWolfe email : John.DeWolfe at dewolfe.com
DeWolfe Enterprises voice : (303) 722-4461
From sgailla at uswest.com Fri May 22 12:58:31 1998
Return-Path:
Received: from gatekeeper-r90.dewolfe.com by alpha.dewolfe.com. (SMI-8.6/SMI-SVR4)
id MAA26410; Fri, 22 May 1998 12:58:28 -0600
Received: from uswgco3.uswc.uswest.com (uswgco3.uswest.com [206.196.133.82])
by gatekeeper-r90.dewolfe.com (8.8.8/8.8.8) with ESMTP id MAA02459
for ; Fri, 22 May 1998 12:58:25 -0600 (MDT)
Received: from egate2.mnet.uswest.com (mailgate.uswc.uswest.com [151.117.138.135])
by uswgco3.uswc.uswest.com (8.8.5/8.8.5) with ESMTP id MAA12174
for ; Fri, 22 May 1998 12:57:54 -0600 (MDT)
Received: from easthub.mnet.uswest.com (easthub.mnet.uswest.com [151.117.26.86]) by egate2.mnet.uswest.com (8.7.1/8.7.1) with SMTP id NAA13258 for ; Fri, 22 May 1998 13:57:53 -0500 (CDT)
Received: from netmail2.mnet.uswest.com (nmal-ut2.uswc.uswest.com [148.157.59.136]) by easthub.mnet.uswest.com (8.6.11/8.6.11) with ESMTP id NAA16391 for ; Fri, 22 May 1998 13:52:02 -0500
Received: from sgailla ([172.28.63.81]) by netmail2.mnet.uswest.com
(Netscape Mail Server v2.02) with ESMTP id AAA29553
for ; Fri, 22 May 1998 12:57:50 -0600
Message-ID: <3565CAAF.948115DC at netmail2.mnet.uswest.com>
Date: Fri, 22 May 1998 13:57:51 -0500
From: sgailla at uswest.com (Sara Gaillard)
Reply-To: sgailla at uswest.com
X-Mailer: Mozilla 4.0 [en] (WinNT; I)
MIME-Version: 1.0
To: "John R. DeWolfe"
Subject: Re: DSL questions
X-Priority: 3 (Normal)
References: <199805042137.PAA04895 at alpha.dewolfe.com.>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 5384
Status: OR
John,
I am glad to hear of your enthusiasm for our MegaBit Services offering
and am hoping the installation has gone well.
I apologize for my delay in responding. As I was reading your
questions, I realized that a few of them were more technical than what I
am capable of answering. Also, some were questions that need to be
answered by one of the U S WEST.net (U S WEST's Internet access team)
members. I forwarded the questions to two other U S WEST employees who
should be able to answer them.
If you haven't heard anything in a while, please let me know.
Thank you,
Sara Gaillard
MegaBit Services Product Specialist
John R. DeWolfe wrote:
> Mon May 4 12:36:19 MDT 1998
>
> Hello,
>
> My name is John DeWolfe and I am scheduled for DSL installation at
> my
> house in Denver on May 18th. It is being installed at 303-744-9625. I
> am a
> sophisticated end-user and have several DSL related questions. I was
> given
> your name and email address by Ian at NetSpeed/Cisco. He said you
> could
> either provide answers or provide further contact information for
> questions
> that I had about US West's DSL deployment.
>
> 1) I understand that DSL will be deployed as a bridged environment.
> How
> broad is the bridged area? Exchange? Central Office? Neighborhood?
> Broader?
>
> 2) Since the environment is bridged, will I be seeing all traffic from
> all
> other DSL subscribers appearing on my DSL connection, or maybe just
> broadcast
> traffic? I am worried about security and the ability of others to
> capture
> password information from telnet, ftp, etc. connections.
>
> 3) Is US West doing anything to prevent home DHCP servers from
> wrecking havoc
> with other bridged customers by giving out bad IP addresses? This has
> been
> a problem for many cable modem providers on the East and West coasts.
>
> 4) Will US West be providing both forward and reverse DNS for the DHCP
>
> addresses? Enough FTP sites require both and that forward and reverse
>
> match, to make this a requirement in many regards. I don't care what
> the
> name is (cust127.dsl.denvera.uswest.com, etc.) As long as forward and
> reverse
> are both available and match.
>
> 5) Rather than using a DSL filter on every phone, I would rather use
> the
> whole house splitter that is available from NetSpeed/Cisco. I am
> perfectly
> willing to install this myself. Can I buy that through US West?
> NetSpeed
> said that I should contact you for sales of this device.
>
> 6) I've been told that static IP addressing will be rolled out in the
> Jun/Jul
> timeframe. Is this correct? Is there an extra charge for this? If
> so, how
> much?
>
> 7) Are there any plans to offer routed instead of bridged networks?
> This would
> make me feel more comfortable about security.
>
> 8) If I change computers or network cards, do I have to call US West
> to let
> them know that I have a new MAC address before the new hardware will
> work
> with your DSL connection? I was planning on experimenting with two
> different
> computers as my DSL connection. This would be a problem if I had to
> call
> US West every time.
>
> 9) What is to prevent someone from hooking up two computers and
> getting
> assigned two different DHCP addresses for each system? Is this
> answered by
> question 8, registered MAC addresses?
>
> 10) Are you only supporting IP protocols? Can I use other transports
> like
> NetBUI or IPX/SPX? You are probably not routing these protocols, but
> if these
> are not screened at the DSL modem, this would allow me to play network
> games
> or share files with neighbors in my local DSL bridged subnet. (I have
> equally
> techy neighbors)
>
> 11) Are you doing any firewalling/filtering of any kind? Either
> outgoing or
> incoming? If I need to connect to some obscure port, or put up a
> server
> listening on such a port, would there be anyting to prevent this? I
> know the
> IP address of my system is dynamic, but aside from that? If I want
> some
> sort of custom filtering, could you provide that service?
>
> 12) I am using US West as my ISP. Does this come with any services
> such as
> news, email addresses, web space, proxy servers, remote dialin, etc.?
>
> 13) In the interest of saving your own internal bandwidth, will you be
>
> requiring that users use a US West proxy server for web access?
>
> 14) Are there any guarantees on my bandwidth? If I purchase a 512K
> line, am
> I guaranteed 512K will be available? Is it more like cable modems
> where I
> am sharing something like 1.5Mb of bandwidth with everyone within my
> DSL
> bridge? In this case I am limited by the speed I pay for, but there
> is a
> total limit as well. If not proprietary, can you tell me how much
> bandwidth
> is available at each central-office?
>
> 15) Will each central office act as a single DSL bridge, or could
> there be
> many bridges at each central office? Is central office the correct
> term for
> where my DSL line originates withing US West? Is there a term for the
> DSL
> bridge subnets I have been referring to?
>
> Thank you so much for your help. I am really (REALLY) looking forward
> to
> this new service!
>
> --
> --
> -------------------------------------------------------------------------
>
> John R. DeWolfe email : John.DeWolfe at dewolfe.com
> DeWolfe Enterprises voice : (303) 722-4461
From sgsmit3 at uswest.com Mon May 25 19:08:54 1998
Return-Path:
Received: from nemesis-i0.dewolfe.com by alpha.dewolfe.com. (SMI-8.6/SMI-SVR4)
id TAA02743; Mon, 25 May 1998 19:08:53 -0600
Received: from uswgco3.uswc.uswest.com (uswgco3.uswest.com [206.196.133.82])
by nemesis-i0.dewolfe.com (8.8.8/8.8.8) with ESMTP id TAA02763
for ; Mon, 25 May 1998 19:08:52 -0600 (MDT)
Received: from egate.mnet.uswest.com (mailgate.uswc.uswest.com [151.119.130.8])
by uswgco3.uswc.uswest.com (8.8.5/8.8.5) with ESMTP id TAA28802
for ; Mon, 25 May 1998 19:08:12 -0600 (MDT)
Received: from easthub.mnet.uswest.com (easthub.mnet.uswest.com [151.117.26.86]) by egate.mnet.uswest.com (8.7.1/8.7.1) with SMTP id TAA15866 for ; Mon, 25 May 1998 19:08:12 -0600 (MDT)
Received: from netmail2.mnet.uswest.com (nmal-ut2.uswc.uswest.com [148.157.59.136]) by easthub.mnet.uswest.com (8.6.11/8.6.11) with ESMTP id UAA07723 for ; Mon, 25 May 1998 20:01:37 -0500
Received: from sgsmit3 ([151.119.58.10]) by netmail2.mnet.uswest.com
(Netscape Mail Server v2.02) with SMTP id AAA21663;
Mon, 25 May 1998 19:08:06 -0600
From: "Scott Smith"
To: "John R. DeWolfe" ,
Cc: "Susan Davey"
Subject: RE: DSL questions
Date: Mon, 25 May 1998 20:08:03 -0500
Message-ID: <002801bd8842$bbe26f40$0a3a7797 at sgsmit3.acs.uswest.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
In-Reply-To: <199805042137.PAA04895 at alpha.dewolfe.com.>
Content-Length: 8261
Status: OR
Answers below: Susan, I need your help on one of them.
> -----Original Message-----
> From: John R. DeWolfe [mailto:John.DeWolfe at dewolfe.com]
> Sent: Monday, May 04, 1998 4:38 PM
> To: sgailla at uswest.com
> Cc: John R. DeWolfe
> Subject: DSL questions
>
>
>
> Mon May 4 12:36:19 MDT 1998
>
> Hello,
>
> My name is John DeWolfe and I am scheduled for DSL installation at my
> house in Denver on May 18th. It is being installed at
> 303-744-9625. I am a
> sophisticated end-user and have several DSL related questions. I
> was given
> your name and email address by Ian at NetSpeed/Cisco. He said you could
> either provide answers or provide further contact information for
> questions
> that I had about US West's DSL deployment.
>
> 1) I understand that DSL will be deployed as a bridged environment. How
> broad is the bridged area? Exchange? Central Office?
> Neighborhood? Broader?
>
Denver POP
> 2) Since the environment is bridged, will I be seeing all traffic from all
> other DSL subscribers appearing on my DSL connection, or maybe
> just broadcast
> traffic? I am worried about security and the ability of others to capture
> password information from telnet, ftp, etc. connections.
>
Typically, you will see all DSL traffic served off of the same
MegaCentral. If security is a major issue, I suggest using a VPN
solution to whomever your exchanging files with or hang in there
until July when NetSpeed/Cisco release a software patch for the
SpeedRunner which will enable NAT, DHCP, and routed PPP sessions. Or,
you could put a firewall or proxy server between your NetSpeed
device and your LAN.
> 3) Is US West doing anything to prevent home DHCP servers from
> wrecking havoc
> with other bridged customers by giving out bad IP addresses?
> This has been
> a problem for many cable modem providers on the East and West coasts.
>
Giving out bad addresses has not been an issue. There has been a single
case where one subscriber statically assigned an address that was
dynamically assigned to another subscriber. This will be a problem
until the software patch.
> 4) Will US West be providing both forward and reverse DNS for the DHCP
> addresses? Enough FTP sites require both and that forward and reverse
> match, to make this a requirement in many regards. I don't care what the
> name is (cust127.dsl.denvera.uswest.com, etc.) As long as forward
> and reverse
> are both available and match.
Yes
>
> 5) Rather than using a DSL filter on every phone, I would rather use the
> whole house splitter that is available from NetSpeed/Cisco. I am
> perfectly
> willing to install this myself. Can I buy that through US West? NetSpeed
> said that I should contact you for sales of this device.
>
I don't think so at this time, you would have to contact MegaBit services
on this one. I'm CC'ing Susan Davey.
> 6) I've been told that static IP addressing will be rolled out in
> the Jun/Jul
> timeframe. Is this correct? Is there an extra charge for this?
> If so, how
> much?
>
A block of 8 static IP addresses is now available to Internet
Office or Office LAN customers. Out of the 8 addresses, 5
are user assignable (6 when the software patch is made available).
The cost is $14.95 per month plus a one time $25.00 charge to
configure our routers. These do not come out of the same pool
as the Dynamic DHCP addresses. You provision them directly from
within the web site, and the addresses will be routable within
one business day.
> 7) Are there any plans to offer routed instead of bridged
> networks? This would
> make me feel more comfortable about security.
>
We are switching all customers to routed mode in July.
> 8) If I change computers or network cards, do I have to call US
> West to let
> them know that I have a new MAC address before the new hardware will work
> with your DSL connection? I was planning on experimenting with
> two different
> computers as my DSL connection. This would be a problem if I had to call
> US West every time.
>
No problem. Each computer behind the NetSpeed device that
requests an address will get one.
> 9) What is to prevent someone from hooking up two computers and getting
> assigned two different DHCP addresses for each system? Is this
> answered by
> question 8, registered MAC addresses?
>
Unfortunately, due to bridging limitations, if two computers on a
LAN get addresses from different subnets they may not be able to
communicate at the IP level. July...
> 10) Are you only supporting IP protocols? Can I use other transports like
> NetBUI or IPX/SPX? You are probably not routing these protocols,
> but if these
> are not screened at the DSL modem, this would allow me to play
> network games
> or share files with neighbors in my local DSL bridged subnet. (I
> have equally
> techy neighbors)
I believe we only route IP.
>
> 11) Are you doing any firewalling/filtering of any kind? Either
> outgoing or
> incoming? If I need to connect to some obscure port, or put up a server
> listening on such a port, would there be anyting to prevent this?
> I know the
> IP address of my system is dynamic, but aside from that? If I want some
> sort of custom filtering, could you provide that service?
>
We are working on it, but we don't offer it at this time.
> 12) I am using US West as my ISP. Does this come with any
> services such as
> news, email addresses, web space, proxy servers, remote dialin, etc.?
>
Internet Access: 2 e-mail accounts, 2 MB of web hosting
Internet Office: 5 ", 5", DNS support, domain name registration/modify
Internet Office LAN: 25 ", 5 MB, ditto
> 13) In the interest of saving your own internal bandwidth, will you be
> requiring that users use a US West proxy server for web access?
>
No. The MegaCentral serving all subscribers will be oversubscribed.
> 14) Are there any guarantees on my bandwidth? If I purchase a
> 512K line, am
> I guaranteed 512K will be available? Is it more like cable modems where I
> am sharing something like 1.5Mb of bandwidth with everyone within my DSL
> bridge? In this case I am limited by the speed I pay for, but there is a
> total limit as well. If not proprietary, can you tell me how
> much bandwidth
> is available at each central-office?
In Denver, we currently have at least one T1 turned up and our
DS3 (45 Mbps) will be available any day now.
No, you are not guaranteed any bandwidth. There are several choke
points
(1) RADSL - stands for rate adaptive and it is just that
(2) MegaCentral oversubscription - to achieve a low price point we
have to oversubscribe the serving connection from MegaBit Services
(3) Backbone oversubscription - in Denver we have dual DS3s that
we share with all customers, Frame, ATM, dial, ISDN, DSL, etc.
(4) The Internet is relatively slow, especially if you have
to go through a NAP (MAE-East for example).
>
> 15) Will each central office act as a single DSL bridge, or could there be
> many bridges at each central office? Is central office the
> correct term for
> where my DSL line originates withing US West? Is there a term for the DSL
> bridge subnets I have been referring to?
>
I'm not sure of your question, but here goes:
Your DSL connection runs from your house to your serving CO (just like
your regular phone service). The DSL connection is between your
SpeedRunner 202/204 and a LoopRunner at the central office. The
protocols used are ATM at Layer 2 and a proprietary CAP based DSL
encoding technique at Layer 1. At your home the conversion is to
Ethernet, at the CO the ATM DSL signal is stripped off and switched
back to MegaBit Services central switching office. At that point,
all DSL subscribers that are using U S WEST.net as their ISP are
aggregated into a large pipe (a MegaCentral) and switched back to
U S WEST.net's POP and terminated into a Cisco router. All traffic
at that point is IP.
Hope this helps. Even with its initial shortcomings, DSL is a
great service!
Scott
> Thank you so much for your help. I am really (REALLY) looking forward to
> this new service!
>
> --
> ------------------------------------------------------------------
> ----------
> John R. DeWolfe email : John.DeWolfe at dewolfe.com
> DeWolfe Enterprises voice : (303) 722-4461
>
From srdavey at uswest.com Tue May 26 09:35:18 1998
Return-Path:
Received: from nemesis-i0.dewolfe.com by alpha.dewolfe.com. (SMI-8.6/SMI-SVR4)
id JAA03534; Tue, 26 May 1998 09:35:18 -0600
Received: from uswgco3.uswc.uswest.com (uswgco3.uswest.com [206.196.133.82])
by nemesis-i0.dewolfe.com (8.8.8/8.8.8) with ESMTP id JAA03300
for ; Tue, 26 May 1998 09:35:16 -0600 (MDT)
Received: from egate3.mnet.uswest.com (mailgate.uswc.uswest.com [151.119.114.51])
by uswgco3.uswc.uswest.com (8.8.5/8.8.5) with ESMTP id JAA20773
for ; Tue, 26 May 1998 09:34:37 -0600 (MDT)
Received: from westhub.mnet.uswest.com (localhost [127.0.0.1]) by egate3.mnet.uswest.com (8.8.8/8.8.8) with SMTP id JAA24733 for ; Tue, 26 May 1998 09:34:34 -0600 (MDT)
Received: from netmail6.uswc.uswest.com (netmail6.uswc.uswest.com [151.117.81.8]) by westhub.mnet.uswest.com (8.6.11/8.6.11) with ESMTP id JAA15805 for ; Tue, 26 May 1998 09:33:40 -0600
Received: from uswest.com ([151.116.115.32]) by netmail6.uswc.uswest.com
(Netscape Mail Server v2.02) with ESMTP id AAA21363;
Tue, 26 May 1998 09:34:32 -0600
Message-ID: <356AE090.B3CD4128 at uswest.com>
Date: Tue, 26 May 1998 09:32:32 -0600
From: susan davey
X-Mailer: Mozilla 4.03 [en] (WinNT; I)
MIME-Version: 1.0
To: Scott Smith
CC: "John R. DeWolfe" , sgailla@uswest.com
Subject: Re: DSL questions
References: <002801bd8842$bbe26f40$0a3a7797 at sgsmit3.acs.uswest.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Length: 8938
Status: OR
On number 5. We don't stock the POTS splitter. I forwarded your message to the
appropriate people at Netspeed. They will contact you and sell this to you
directly. In the case that you don't hear from them in the next two weeks,
please let me know. Susan
Scott Smith wrote:
> Answers below: Susan, I need your help on one of them.
>
> > -----Original Message-----
> > From: John R. DeWolfe [mailto:John.DeWolfe at dewolfe.com]
> > Sent: Monday, May 04, 1998 4:38 PM
> > To: sgailla at uswest.com
> > Cc: John R. DeWolfe
> > Subject: DSL questions
> >
> >
> >
> > Mon May 4 12:36:19 MDT 1998
> >
> > Hello,
> >
> > My name is John DeWolfe and I am scheduled for DSL installation at my
> > house in Denver on May 18th. It is being installed at
> > 303-744-9625. I am a
> > sophisticated end-user and have several DSL related questions. I
> > was given
> > your name and email address by Ian at NetSpeed/Cisco. He said you could
> > either provide answers or provide further contact information for
> > questions
> > that I had about US West's DSL deployment.
> >
> > 1) I understand that DSL will be deployed as a bridged environment. How
> > broad is the bridged area? Exchange? Central Office?
> > Neighborhood? Broader?
> >
> Denver POP
>
> > 2) Since the environment is bridged, will I be seeing all traffic from all
> > other DSL subscribers appearing on my DSL connection, or maybe
> > just broadcast
> > traffic? I am worried about security and the ability of others to capture
> > password information from telnet, ftp, etc. connections.
> >
> Typically, you will see all DSL traffic served off of the same
> MegaCentral. If security is a major issue, I suggest using a VPN
> solution to whomever your exchanging files with or hang in there
> until July when NetSpeed/Cisco release a software patch for the
> SpeedRunner which will enable NAT, DHCP, and routed PPP sessions. Or,
> you could put a firewall or proxy server between your NetSpeed
> device and your LAN.
>
> > 3) Is US West doing anything to prevent home DHCP servers from
> > wrecking havoc
> > with other bridged customers by giving out bad IP addresses?
> > This has been
> > a problem for many cable modem providers on the East and West coasts.
> >
> Giving out bad addresses has not been an issue. There has been a single
> case where one subscriber statically assigned an address that was
> dynamically assigned to another subscriber. This will be a problem
> until the software patch.
>
> > 4) Will US West be providing both forward and reverse DNS for the DHCP
> > addresses? Enough FTP sites require both and that forward and reverse
> > match, to make this a requirement in many regards. I don't care what the
> > name is (cust127.dsl.denvera.uswest.com, etc.) As long as forward
> > and reverse
> > are both available and match.
> Yes
>
> >
> > 5) Rather than using a DSL filter on every phone, I would rather use the
> > whole house splitter that is available from NetSpeed/Cisco. I am
> > perfectly
> > willing to install this myself. Can I buy that through US West? NetSpeed
> > said that I should contact you for sales of this device.
> >
> I don't think so at this time, you would have to contact MegaBit services
> on this one. I'm CC'ing Susan Davey.
>
> > 6) I've been told that static IP addressing will be rolled out in
> > the Jun/Jul
> > timeframe. Is this correct? Is there an extra charge for this?
> > If so, how
> > much?
> >
> A block of 8 static IP addresses is now available to Internet
> Office or Office LAN customers. Out of the 8 addresses, 5
> are user assignable (6 when the software patch is made available).
> The cost is $14.95 per month plus a one time $25.00 charge to
> configure our routers. These do not come out of the same pool
> as the Dynamic DHCP addresses. You provision them directly from
> within the web site, and the addresses will be routable within
> one business day.
>
> > 7) Are there any plans to offer routed instead of bridged
> > networks? This would
> > make me feel more comfortable about security.
> >
> We are switching all customers to routed mode in July.
>
> > 8) If I change computers or network cards, do I have to call US
> > West to let
> > them know that I have a new MAC address before the new hardware will work
> > with your DSL connection? I was planning on experimenting with
> > two different
> > computers as my DSL connection. This would be a problem if I had to call
> > US West every time.
> >
> No problem. Each computer behind the NetSpeed device that
> requests an address will get one.
>
> > 9) What is to prevent someone from hooking up two computers and getting
> > assigned two different DHCP addresses for each system? Is this
> > answered by
> > question 8, registered MAC addresses?
> >
> Unfortunately, due to bridging limitations, if two computers on a
> LAN get addresses from different subnets they may not be able to
> communicate at the IP level. July...
>
> > 10) Are you only supporting IP protocols? Can I use other transports like
> > NetBUI or IPX/SPX? You are probably not routing these protocols,
> > but if these
> > are not screened at the DSL modem, this would allow me to play
> > network games
> > or share files with neighbors in my local DSL bridged subnet. (I
> > have equally
> > techy neighbors)
>
> I believe we only route IP.
>
> >
> > 11) Are you doing any firewalling/filtering of any kind? Either
> > outgoing or
> > incoming? If I need to connect to some obscure port, or put up a server
> > listening on such a port, would there be anyting to prevent this?
> > I know the
> > IP address of my system is dynamic, but aside from that? If I want some
> > sort of custom filtering, could you provide that service?
> >
> We are working on it, but we don't offer it at this time.
>
> > 12) I am using US West as my ISP. Does this come with any
> > services such as
> > news, email addresses, web space, proxy servers, remote dialin, etc.?
> >
> Internet Access: 2 e-mail accounts, 2 MB of web hosting
> Internet Office: 5 ", 5", DNS support, domain name registration/modify
> Internet Office LAN: 25 ", 5 MB, ditto
>
> > 13) In the interest of saving your own internal bandwidth, will you be
> > requiring that users use a US West proxy server for web access?
> >
> No. The MegaCentral serving all subscribers will be oversubscribed.
>
> > 14) Are there any guarantees on my bandwidth? If I purchase a
> > 512K line, am
> > I guaranteed 512K will be available? Is it more like cable modems where I
> > am sharing something like 1.5Mb of bandwidth with everyone within my DSL
> > bridge? In this case I am limited by the speed I pay for, but there is a
> > total limit as well. If not proprietary, can you tell me how
> > much bandwidth
> > is available at each central-office?
>
> In Denver, we currently have at least one T1 turned up and our
> DS3 (45 Mbps) will be available any day now.
>
> No, you are not guaranteed any bandwidth. There are several choke
> points
> (1) RADSL - stands for rate adaptive and it is just that
> (2) MegaCentral oversubscription - to achieve a low price point we
> have to oversubscribe the serving connection from MegaBit Services
> (3) Backbone oversubscription - in Denver we have dual DS3s that
> we share with all customers, Frame, ATM, dial, ISDN, DSL, etc.
> (4) The Internet is relatively slow, especially if you have
> to go through a NAP (MAE-East for example).
>
> >
> > 15) Will each central office act as a single DSL bridge, or could there be
> > many bridges at each central office? Is central office the
> > correct term for
> > where my DSL line originates withing US West? Is there a term for the DSL
> > bridge subnets I have been referring to?
> >
>
> I'm not sure of your question, but here goes:
>
> Your DSL connection runs from your house to your serving CO (just like
> your regular phone service). The DSL connection is between your
> SpeedRunner 202/204 and a LoopRunner at the central office. The
> protocols used are ATM at Layer 2 and a proprietary CAP based DSL
> encoding technique at Layer 1. At your home the conversion is to
> Ethernet, at the CO the ATM DSL signal is stripped off and switched
> back to MegaBit Services central switching office. At that point,
> all DSL subscribers that are using U S WEST.net as their ISP are
> aggregated into a large pipe (a MegaCentral) and switched back to
> U S WEST.net's POP and terminated into a Cisco router. All traffic
> at that point is IP.
>
> Hope this helps. Even with its initial shortcomings, DSL is a
> great service!
>
> Scott
>
> > Thank you so much for your help. I am really (REALLY) looking forward to
> > this new service!
> >
> > --
> > ------------------------------------------------------------------
> > ----------
>
> > John R. DeWolfe email : John.DeWolfe at dewolfe.com
> > DeWolfe Enterprises voice : (303) 722-4461
> >
From john Wed Jul 15 17:24:41 1998
Return-Path:
Received: by alpha.dewolfe.com. (SMI-8.6/SMI-SVR4)
id RAA03876; Wed, 15 Jul 1998 17:24:24 -0600
From: john (John R. DeWolfe)
Message-Id: <199807152324.RAA03876 at alpha.dewolfe.com.>
Subject: static IP's
To: dsl
Date: Wed, 15 Jul 1998 17:24:24 -0600 (MDT)
Cc: john (John R. DeWolfe)
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 5838
Status: O
Wed Jul 15 16:14:40 MDT 1998
I finally got my static IP addresses today. I have been fighting this
battle for over 1 1/2 months now. It only took about 50 phone calls with an
average of 8 a day on the days that I tried to get it done. About a 1 1/2
months ago I tried to get upgraded to static IP addresses. I was told that
in order to do that I had to upgrade from MegaPak to MegaOffice. MegaOffice
includes 5 static IP's, a speed increase to 512K, 5 uswest.net email boxes,
and some increase in uswest.net web page space. Since I wanted the speed
increase anyway, I went ahead. Then my problems began. I left several
messages for my normal sales rep and eventually found out they were on
vacation, so I put the order in through someone else. They gave me an install
date about 3 weeks out, which is typical, and then I waited. The install
date came and went and I gave them an extra day or so since they were supposed
to be busy. I finally called and found out that there were now two orders in
the system for the upgrade. Turns out my original sales rep got my messages
when they got back from vacation and went ahead and keyed in the order with
out talking to me first. With two orders in the system, I would have expected
to get two installation calls, but people kept saying that they canceled
each other out, but nobody called me about it. Anyway, after much digging I
found this out and then started calling trying to get it resolved. I guess
I don't really want to go into all of it, but the upshot is that different
groups do the speed increase, vs. the static IP's and neither group knows
anything about the other. It took me 2 weeks to get the line speed increase.
This was after I had the problem "escalated" on three different occasions. In
the end, I just happened to get a hold of the correct person who knew how to
do the increase. The static IP's had to be ordered three times and I again
had to be lucky enough to find the right person that knew how to do that as
well. Things are still screwed up somewhere, I am still listed as having two
DSL lines, both using the same telephone number, but it is working and I have
my static IP addresses and a 512K line.
Things I learned along the way:
1) Currently there is a one to one mapping of DSL lines to DHCP assigned
IP addresses. That is why I continue to get the same IP address every time
I boot my system. My DHCP address only changed when I changed network
interface cards, with a corresponding change in MAC address. US West tells
me that this will change after enough new subscribers come on board.
2) Currently virtually all DSL customers who signed up with the 256K basic
DSL package are getting 512K download speeds. I was told by a US West person
that that will be changing in the near future and everyone will be cut back
to 256K. That is what they signed up for and the 512K is just a bonus for
now according to the US West person. So everyone may experience a slow down
when and if they implement this.
3) Once you find a tech support person who can help you, be sure to get their
direct line phone number. I was told on many occasions that a) we are not
allowed to give out our last names, b) we are not allowed to give out direct
line phone numbers, and c) you only need a first name, I'm the only person
here with that first name. Being the only person with the first name may or
may not be true, but what I found was I couldn't get back to the same
department to ask for that person. Most phone calls involved a seemingly
ever changing voice menu tree, and once I talked to a person I was inevitably
transferred to someone else. Even if I kept a close log on what menu options
I chose, a transfer would prevent me from getting back to the right department.
The only success I had was in getting a direct call-back number. I came to
the conclusion that those people who were not willing to give it out, were
not the people that would be able to help me anyway.
4) If you run into problems with tech support, don't hesitate to demand to
talk to a "tier 2" or "supervisor" before accepting that the problem lies with
another department, organization, etc. The tier 2 people are much more likely
to know what is going on and how things tie together than the people that
first answer the phone. I was told on more than one occasion that since I am
using a Sun workstation, which is a non-supported platform, that DSL would
not work at all with my system. The tier 2 people were more likely to
understand that while a Sun is unsupported from a configuration standpoint,
that that has nothing to do with whether the speed increase was done or not.
5) Virtually everyone at US West was more than willing to try to help me, but
in most cases did not have the knowlege, authority, access, or contacts to
help me. Most calls resulted in 4 different people giving me 5 different
phone numbers to call. Each said they could not help me themselves but this
other number would reach the department that could help me. On at least three
occasions I was given three diffent phone numbers that had been disconnected.
Compared to my first experience with DSL where things happened quickly and
mostly on time, this has been a nightmare. I'm glad it is over with and
I can get onto other things.
P.S. on Jul 23rd, the FRUUG (Front Range Unix Users Group) is having a meeting
in Boulder and I will be one of 4-5 people giving a short talk on DSL
experiences. There will be two end-users and three DSL ISP's (including
US West). Might be an interesting time. Let me know if you want more details
on where and when.
--
----------------------------------------------------------------------------
John R. DeWolfe email : John.DeWolfe at dewolfe.com
DeWolfe Enterprises voice : (303) 722-4461
From kathryn.ragucci at awl.com Mon Jul 20 11:55:36 1998
Return-Path:
Received: from nemesis-i0.dewolfe.com by alpha.dewolfe.com. (SMI-8.6/SMI-SVR4)
id LAA05557; Mon, 20 Jul 1998 11:55:35 -0600
Received: from mail.awl.com (mail.awl.com [192.207.117.222])
by nemesis-i0.dewolfe.com (8.8.8/8.8.8) with ESMTP id LAA06270
for ; Mon, 20 Jul 1998 11:55:31 -0600 (MDT)
Received: from tarah.awl.com (dhcp-188.stoneham.awl.com [10.8.248.188])
by mail.awl.com (8.8.8/8.8.7) with SMTP id OAA28061
for ; Mon, 20 Jul 1998 14:00:25 -0400 (EDT)
Message-Id: <3.0.5.32.19980720135433.007f0d50 at pop.awl.com>
X-Sender: ragucck at pop.awl.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Mon, 20 Jul 1998 13:54:33 -0400
To: john.dewolfe at dewolfe.com
From: Katie Ragucci
Subject: ADSL books
Mime-Version: 1.0
Content-Type: text/enriched; charset="us-ascii"
Content-Length: 2121
Status: OR
Hi John,
My name is Kathryn Ragucci and I am an editorial assistant at
Addison-Wesley Longman. I publish books in the engineering sector of
Addison-Wesley's Professional Group (http://www2.awl.com/cseng/). I am
interested in the emerging technology of ADSL and I was forwarded the
outline of the ADSL panel being held by the Front Range Unix Users Group
this month. I see that you are a key speaker at the July 23rd meeting on
ADSL. Subsequently, I am very interested in your opinions about the
future of ADSL and what you see as resulting educational needs for the
people who want to use this technology.
I have found a handful of published books on ADSL including:
ADSL (Computer Communications), Walter Goralski,
1998.
Demystifying Atm/Adsl, Michael Busby, 1998.
DSL: Specilization Techniques and Standards Developments for
Digital Subscribers Lines, Walter Chen, 1998.
Are you familiar with any of these books,and if so which do feel deals
best with ADSL? Are there any other books on ADSL that you feel are
particularly strong?
I am also very interested in the educational needs that still need to be
addressed and fulfilled. What are the areas in ADSL that have not yet
been covered (or need updating)? Who is the group (audience) that needs
information on ADSL? As a new technology, ADSL appears to be progressing
very quickly. How do you see the market for ADSL?
I value your comments and insights on ADSL. I would also like to inquire
whether you are considering publishing in this area in the future. If
you have considering writing (or would like to), please feel free to
contact me to discuss a possible book with Addison-Wesley. If you are
not planning to write at this time, who else do you feel would be the
best person to write in this area?
Thank you for taking time to answer my questions. I look forward to
hearing from you.
Best,
Kathryn Ragucci
Editorial Assistant
Addison-Wesley Longman
Professional Publishing Computer & Engineering Group
781-944-3700 x4941
kathryn.ragucci at awl.com
From john Mon Jul 20 14:47:19 1998
Return-Path:
Received: by alpha.dewolfe.com. (SMI-8.6/SMI-SVR4)
id OAA05811; Mon, 20 Jul 1998 14:47:18 -0600
From: john (John R. DeWolfe)
Message-Id: <199807202047.OAA05811 at alpha.dewolfe.com.>
Subject: Re: ADSL books
To: kathryn.ragucci at awl.com (Katie Ragucci)
Date: Mon, 20 Jul 1998 14:47:17 -0600 (MDT)
In-Reply-To: <3.0.5.32.19980720135433.007f0d50 at pop.awl.com> from "Katie Ragucci" at Jul 20, 98 01:54:33 pm
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 5042
Status: O
Hi Kathryn,
Thank you for soliciting my opinion on DSL technology. I am afraid I
have not read any of the three books you mentioned, so can't offer any
opinions on those. I have not run across any other books either, so can't
help you there either.
To try to answer the other questions you asked:
What are the areas in ADSL that have not yet been covered (or need updating)?
I have not seen a "Dummies" or "Idiots" type book for this market. I think
this might be a useful book for the end-user. DSL seems pretty user
friendly from an en-user perspective, but with companies such as US West
offering to let people install DSL themselves, a book that talks about
how to install this yourself, or things that might go wrong once the line is
up and running. That would be a possiblity.
Who is the group (audience) that needs information on ADSL?
Again, I think there is a need for books aimed at the end-user. There
may also be a need for books aimed at the ISP to help with decisions related
to deployment of DSL. DHCP vs static IP addresses, end-user security, shared
bandwidth, carrier gotcha's, and network architecture, would all be possible
subject areas for ISP's. This is obviously a smaller audience, but there
might be a need in this area.
As a new technology, ADSL appears to be progressing very quickly. How do you
see the market for ADSL?
I see the market for ADSL (and other low-cost high-speed Internet access
technologies, like cable modems) as taking off fast. From everything I hear,
the demand for ADSL from US West has far out-stripped anticipated demand.
Computer penetration into homes is still under 50% I believe, even after almost
20 years. Within that group though, Internet usage is around 45% after only
about 5 years, so based on this trend and the growth of the Internet as a
whole, I expect the growth to continue. While I admittedly hang out in a
high-tech circle, I have not run into many non-technical people that have not
liked the Internet itself after being introduced to it. What I have found is
that people do not like "accessing" the Internet. Modems are to slow, tie
up the telephone line, and take to long to connect. DSL solves all of that
and I see that as fueling the high-speed Internet access boom.
Hope this is helpful.
P.S. With regard to doing some ADSL publishing, I was a contributor to
the Peter Norton Guide to Java, but am probably not personally interested in
further publishing. My wife continues to write technical books, and I will
forward your message to her.
Thanks again,
>
>
> My name is Kathryn Ragucci and I am an editorial assistant at
> Addison-Wesley Longman. I publish books in the engineering sector of
> Addison-Wesley's Professional Group (http://www2.awl.com/cseng/). I am
> interested in the emerging technology of ADSL and I was forwarded the
> outline of the ADSL panel being held by the Front Range Unix Users Group
> this month. I see that you are a key speaker at the July 23rd meeting on
> ADSL. Subsequently, I am very interested in your opinions about the
> future of ADSL and what you see as resulting educational needs for the
> people who want to use this technology.
>
>
> I have found a handful of published books on ADSL including:
>
>
> ADSL (Computer Communications), Walter Goralski,
> 1998.
>
>
> Demystifying Atm/Adsl, Michael Busby, 1998.
>
>
> DSL: Specilization Techniques and Standards Developments for
> Digital Subscribers Lines, Walter Chen, 1998.
>
>
>
> Are you familiar with any of these books,and if so which do feel deals
> best with ADSL? Are there any other books on ADSL that you feel are
> particularly strong?
>
> I am also very interested in the educational needs that still need to be
> addressed and fulfilled. What are the areas in ADSL that have not yet
> been covered (or need updating)? Who is the group (audience) that needs
> information on ADSL? As a new technology, ADSL appears to be progressing
> very quickly. How do you see the market for ADSL?
>
>
>
> I value your comments and insights on ADSL. I would also like to inquire
> whether you are considering publishing in this area in the future. If
> you have considering writing (or would like to), please feel free to
> contact me to discuss a possible book with Addison-Wesley. If you are
> not planning to write at this time, who else do you feel would be the
> best person to write in this area?
>
>
> Thank you for taking time to answer my questions. I look forward to
> hearing from you.
>
>
> Best,
>
> Kathryn Ragucci
>
> Editorial Assistant
>
> Addison-Wesley Longman
>
> Professional Publishing Computer & Engineering Group
>
> 781-944-3700 x4941
>
> kathryn.ragucci at awl.com
>
>
>
--
----------------------------------------------------------------------------
John R. DeWolfe email : John.DeWolfe at dewolfe.com
DeWolfe Enterprises voice : (303) 722-4461
Last Updated: $Date: 1999/09/20 15:26:47 $
Problems? Contact webmaster at fruug.org