Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Anybody @home?

3 views
Skip to first unread message

James Long

unread,
Dec 1, 2001, 8:12:16 PM12/1/01
to
So are any of our cable-modem friends still on-line?

I have only one acquaintance who used cable IP service,
but that IP address is not answering pings. I did a
quick scan of that /24 and a couple others, and got no
replies from any of them.

wize1

unread,
Dec 1, 2001, 8:39:19 PM12/1/01
to
yep. outage only lasted 45 minutes.. now on attbi.com system... Portland
looks like one of the first systems to transfer over to ATT...


"James Long" <james_...@nospam.museum.rain.com> wrote in message
news:3C097FF0...@nospam.museum.rain.com...

Joe Winton

unread,
Dec 1, 2001, 8:52:17 PM12/1/01
to
"Scott Willsey" <hangtown@no_spam_tectradev.com> wrote in message
news:bj1j0uc6da0laus8r...@4ax.com...
>
> Yes, we had a smooth transition in PDX, though of course people are
> whining about the 1.5Mbps downstream cap. I'm not thrilled about it,
> but we still have broardband, still have an internet connection, and
> are still getting service cheaper than the equivalent DSL plans.
>
> Some people are never happy, I guess.

If you think the PDX whining about the cap is bad wait until the other
800,000 people get back online!

I'm with you though... I'm definitely not happy about the speed reduction
but I am pleased about the swift transition. It could have been a lot
worse.

- Joe

Randy Rhine

unread,
Dec 1, 2001, 8:53:41 PM12/1/01
to
Speaking of which...yes...it went fairly smoothly for me...except...I
cannot get it to work consistantly with my Linksys router. For awhile it
was working fine. Then I turned off the PC for a few hours and when I
turned it back on, the only thing I can get when using the Linksys is
the ATTBI transition screen. When I connect the cable model directly to
my PC, it works fine.

Anybody got any ideas? I'm about ready to give it up and go have a
pizza and try again tomorrow.

On the + side, it appears that attbi has more options with regard to
email forwarding, etc than @home did. I don't mind them changeing...I
just hope they leave it alone for awhile.

randy

Scott Willsey wrote:


>
> On Sun, 02 Dec 2001 01:39:19 GMT, "wize1" <wiz...@attbi.com> wrote:
>
> >yep. outage only lasted 45 minutes.. now on attbi.com system... Portland
> >looks like one of the first systems to transfer over to ATT...
> >
>

> Yes, we had a smooth transition in PDX, though of course people are
> whining about the 1.5Mbps downstream cap. I'm not thrilled about it,
> but we still have broardband, still have an internet connection, and
> are still getting service cheaper than the equivalent DSL plans.
>
> Some people are never happy, I guess.
>

> BTW, to the first gentleman: your friend's IP address will have
> changed to a new one. That's why you can't ping the old one.
>
> Scott
>
> --
> "The great pleasure of a dog is that you may make
> a fool of yourself with him and not only will he
> not scold you, but he will make a fool of
> himself too." - Samuel Butl

Joe Winton

unread,
Dec 1, 2001, 9:04:38 PM12/1/01
to
"Randy Rhine" <rrr...@attbi.com> wrote in message
news:3C098A7B...@attbi.com...

> Speaking of which...yes...it went fairly smoothly for me...except...I
> cannot get it to work consistantly with my Linksys router. For awhile it
> was working fine. Then I turned off the PC for a few hours and when I
> turned it back on, the only thing I can get when using the Linksys is
> the ATTBI transition screen. When I connect the cable model directly to
> my PC, it works fine.
>
> Anybody got any ideas? I'm about ready to give it up and go have a
> pizza and try again tomorrow.

Is it mainly having problems resolving addresses (i.e. DNS problems)?

I was having similar problems earlier today. Entering the IP address of my
router in the DNS section of each computer's TCP/IP Properties seemed to fix
the problem. For instance, I checked 'Use the following DNS server
addresses' and then entered '192.168.1.1' as the 'preferred DNS server'.

- Joe

James Long

unread,
Dec 1, 2001, 10:42:23 PM12/1/01
to
Scott Willsey wrote:
>
> BTW, to the first gentleman: your friend's IP address will have
> changed to a new one. That's why you can't ping the old one.

Hopefully they have informed him what the new IP will be. That
system used to have a static IP. The IP/netmask/gateway are
printed right on the installation work order. If it's now DHCP,
that's going to be fun for the DNS setup. How were you notified
that your IP would be changed? Or have you ever been on a static
IP with @home?

Just curious, how big a change was made? home.net appears to own
a netblock at 65.0.0.0/12. Have your IPs moved around within
that block or into a different block entirely?

And if that machine will now have to use DHCP, what is your exper-
ience on how dynamic those IPs really are? Has your lease ever
changed, and if so, how often?

Roger Bingham

unread,
Dec 1, 2001, 11:41:59 PM12/1/01
to
I'm using a Linksys BEFSR41 router and all I had to do was to set the router
for dhcp to the WAN ("obtain an IP address automatically" checkbox) and then
all I could get to was the transition screen UNTIL I did a release/renew on
each computer. I'm running 4 win98 boxes and 2 win2k boxes and all of them
are relying soley on the Linksys DHCP server, so I'm not entering any DNS
information anywhere. Anyway, all machines have had uninterrupted access so
far (since about 9am this morning) Email is working fine too.
Roger

"Joe Winton" <j...@winton.org> wrote in message
news:j_fO7.2039$R84.898@rwcrnsc52...

Roger Bingham

unread,
Dec 1, 2001, 11:44:28 PM12/1/01
to
Oops - I forgot to mention that I also had to change the email domains from
@home.com to @attbi.com, and the mail servers to mail.attbi.com and the news
server to netnews.attbi.com.
Roger

"Roger Bingham" <roger.c...@attbi.com> wrote in message
news:riiO7.2359$KY6.1054@rwcrnsc53...

Joe Winton

unread,
Dec 1, 2001, 11:59:37 PM12/1/01
to
"Roger Bingham" <roger.c...@attbi.com> wrote in message
news:riiO7.2359$KY6.1054@rwcrnsc53...
> I'm using a Linksys BEFSR41 router and all I had to do was to set the
router
> for dhcp to the WAN ("obtain an IP address automatically" checkbox) and
then
> all I could get to was the transition screen UNTIL I did a release/renew
on
> each computer. I'm running 4 win98 boxes and 2 win2k boxes and all of
them
> are relying soley on the Linksys DHCP server, so I'm not entering any DNS
> information anywhere. Anyway, all machines have had uninterrupted access
so
> far (since about 9am this morning) Email is working fine too.
> Roger

That's basically what I did... For some reason, I had to actually enter my
router's IP address into the DNS settings of my Win2k and WinXP machines.
If I just set 'obtain DNS automatically' they would eventually quit
resolving addresses (and then work again for a few minutes after doing a
'ipconfig /renew'). My WinME machine had no problems at all with the
automatic configuration.


Roger Bingham

unread,
Dec 2, 2001, 12:30:23 AM12/2/01
to
hmmm... I double-checked my Win2k machines and they are set for "obtain DNS
auto-magically". It's very strange that you would have sporradic DNS
service - it seems like it should either work or not. Dunno what to think
about it.
Roger

"Joe Winton" <j...@winton.org> wrote in message

news:ZyiO7.1425$Px.43887@rwcrnsc54...

Brian Lorton

unread,
Dec 2, 2001, 1:27:47 AM12/2/01
to
Excite@home changed to ATT Broadband Internet

All Emails for @home users changed from na...@home.com to na...@attbi.com

OLD EMAIL ADDRESS: na...@home.com
NEW EMAIL ADDRESS: na...@attbi.com
IP: DHCP
smtp: mail.attbi.com
POP3: mail.attbi.com
newsgroup: netnews.attbi.com
http://www.attbi.com/

Hope that helps

respond only in the newsgroup as my email cerant is changed to stop spam

david parsons

unread,
Dec 2, 2001, 5:01:10 PM12/2/01
to
In article <bj1j0uc6da0laus8r...@4ax.com>,

Scott Willsey <hangtown@no_spam_tectradev.com> wrote:
>On Sun, 02 Dec 2001 01:39:19 GMT, "wize1" <wiz...@attbi.com> wrote:
>
>>yep. outage only lasted 45 minutes.. now on attbi.com system... Portland
>>looks like one of the first systems to transfer over to ATT...
>>
>
>Yes, we had a smooth transition in PDX, though of course people are
>whining about the 1.5Mbps downstream cap. I'm not thrilled about it,
>but we still have broardband, still have an internet connection, and
>are still getting service cheaper than the equivalent DSL plans.

It's noticably slower than the @home service was. And the AT&T
routers are located in Seattle instead of Portland (I have a machine
on an @home T-1 downtown; before 2am Saturday it was 8 hops from
home to that machine and I never got outside the city limits of
Portland, and now the traffic rolls up to Seattle, bounces around
there a while, the trickles back.) Plus at&t has some sort of http
proxy on the line -- I've got a 10 machine computational cluster at
home which has been idle and only doing seti@home for the past few
weeks, and after the changeover half of those boxes couldn't
retrieve workunits via my local proxy server so I had to set up a
proxy server on my downtown machine [1].

[1: colocation sucks, but it's a lot cheaper than $1000/month +
US West charges.]


____
david parsons \bi/ I suppose AT&T needs the ratecap so they can sell
\/ premium services.

Robert

unread,
Dec 2, 2001, 6:56:04 PM12/2/01
to
For the record, i had my system set up static, obviously couldn't get
anywhere since everyones ip address changed. I set up for dhcp and still
couldn't get anywhere. Called tech support who as usual was very little
help. The level ones like most companies are helpful to help newbies make
sure everything's set right, but not much beyond that. Graduated to level 2
tech, who seemed to know a bit more but she started BSing me near the end of
the call just before everything started working suddenly. Access was
intermittent for a few hours, today everything seems fine. Agreed, happy
with the changeover- yeah, could have been alot worse.

Downstream capped at 1.5? Anyone know what the rated bandwidth was
originally?

Rob
"david parsons" <o...@pell.portland.or.us> wrote in message
news:9ue8b6$g...@pell.pell.portland.or.us...

Chris Jaggers

unread,
Dec 2, 2001, 8:51:15 PM12/2/01
to
Here's a big load of DNS INFO for you all
ns1.attbi.com | 204.127.198.4 | Bridgewater, NJ 08807
ns2.attbi.com | 216.148.227.68 | Redwood City, CA 92191
ns3.attbi.com | 204.127.68.4 | Bridgewater, NJ 08807
ns4.attbi.com same as above
ns5.attbi.com 204.127.202.4 same location
ns6.attbi.com 63.240.76.4 San Diego, CA 92121
ns7.attbi.com 204.127.68.11 Bridgewater, NJ (shared as proxy.attbi.com too)
ns8.attbi.com same as above
ns9.attbi.com same as above
same with ns10. I think i'll stop here check what DNS you've been assigned,
some may be in NJ. Maybe it will help some with speed, but then again, from what
im getting everything is being routed through NJ. For example......(hopfully
this tables format wont get messed up in the mail)
==================================================
=== VisualRoute report on 02-Dec-01 6:10:03 PM ===
==================================================

Real-time report for ns6.attbi.com [63.240.76.4] (80% done)

Analysis: 'ns6.attbi.com' was found in 15 hops (TTL=49).

---------------------------------------------------------------------------------------------------------------------------------------

| Hop | %Loss | IP Address | Node Name |
Location | Tzone | ms | Graph | Network |
---------------------------------------------------------------------------------------------------------------------------------------

| 0 | | 192.168.0.100 | GREENBOX |
... | | | | (private use) |
| 1 | | 192.168.0.1 | - |
... | | 1 | x | (private use) |
| 2 | | 10.88.89.1 | - |
... | | 13 | x | (private use) |
| 3 | | 12.244.84.1 | - | ?Middletown, NJ
07748 | | 13 | x- | AT&T ITS |
| 4 | | 12.244.72.34 | - | ?Middletown, NJ
07748 | | 17 | x- | AT&T ITS |
| 5 | | 12.123.44.61 | gbr2-p70.st6wa.ip.att.net | Seattle, WA,
USA | -08:00 | 17 | x | AT&T ITS |
| 6 | | 12.122.5.169 | gbr4-p80.st6wa.ip.att.net | Seattle, WA,
USA | -08:00 | 18 | x- | AT&T ITS |
| 7 | | 12.122.2.230 | gbr4-p10.cgcil.ip.att.net | Chicago, IL,
USA | -06:00 | 61 | x | AT&T ITS |
| 8 | | 12.122.1.125 | gbr3-p60.cgcil.ip.att.net | Chicago, IL,
USA | -06:00 | 63 | x- | AT&T ITS |
| 9 | | 12.122.2.1 | gbr3-p10.n54ny.ip.att.net | New York, NY,
USA | -05:00 | 93 | x- | AT&T ITS |
| 10 | | 12.122.5.245 | gbr2-p60.n54ny.ip.att.net | New York, NY,
USA | -05:00 | 80 | x- | AT&T ITS |
| 11 | | 12.123.1.133 | gar1-p370.n54ny.ip.att.net | New York, NY,
USA | -05:00 | 82 | x- | AT&T ITS |
| 12 | | 12.122.255.162 | - | ?Middletown, NJ
07748 | | 82 | x-- | AT&T ITS |
| 13 | | 63.240.64.246 | - | ?San Diego, CA
92191 | | 126 | --x--- | AT&T CERFnet |
| 14 | | 63.240.88.74 | - | ?San Diego, CA
92191 | | 78 | x | AT&T CERFnet |
| 15 | | 63.240.76.4 | ns6.attbi.com | ?San Diego, CA
92121 | | 81 | x | Project Redwood ISP |
---------------------------------------------------------------------------------------------------------------------------------------

Roundtrip time to ns6.attbi.com, average = 81ms, min = 81ms, max = 86ms --
02-Dec-01 6:10:03 PM

user

unread,
Dec 3, 2001, 1:18:12 PM12/3/01
to

>
> Downstream capped at 1.5? Anyone know what the rated bandwidth was
> originally?
>


i don't know what the rated bandwidth was, but i was regularly seeing
4-5mbps. it's not all useful speed, as most servers aren't going to be able
to send the data that fast, but it's really useful with programs like winmx
where you can have multiple downloads running at the same time.

Jack Price

unread,
Dec 3, 2001, 1:38:29 PM12/3/01
to
Roger,
Glad you posted this info. I too use a BEFSR41. I spent all weekend dorking
with the router settings with no luck, though I could get any one out of my
5 PCs on the net when connected directly to the modem. I even flashed the
router with the latest firmware with no luck. I'll try a release/renew on
each PC tonight.

I did finally get through to a level 2 tech, who said that the reason I
could not connect is because AT&T moved away from using an assigned Host
name and will be using the router's MAC address, but this capability is not
yet ready.
Jack


"Roger Bingham" <roger.c...@attbi.com> wrote in message
news:riiO7.2359$KY6.1054@rwcrnsc53...

Robert

unread,
Dec 3, 2001, 3:10:45 PM12/3/01
to
A level 2 told me last night they stopped using MAC address assigned to
modem and started using the one assigned to the net card..

Rob


"Jack Price" <jack....@intel.com> wrote in message
news:9uggr6$h...@news.or.intel.com...

Robert

unread,
Dec 3, 2001, 3:13:43 PM12/3/01
to

Yeah, i was seeing higher accumulate speeds in similar programs - kazaa etc.
Mabye this will
help us to see more consistent rates if not anything else..

Rob

Jack Price

unread,
Dec 4, 2001, 12:12:03 AM12/4/01
to
Well, that's just typical of AT&T or @home tech support to give different
answers figuring they really don't seem to know what's going on. I've asked
the same question before to two different techs on the same night and got
two completely different answers.

Tonight, I plugged in my old Host name from @home and I have the router
working and all 5 PC's on the net. I give up trying to figure the logic out,
it just works now.
Jack


"Robert" <bsi...@hotmail.com> wrote in message
news:9%QO7.3215$R84.2196@rwcrnsc52...

david parsons

unread,
Dec 4, 2001, 1:35:38 AM12/4/01
to
In article <oczO7.1852$Px.44755@rwcrnsc54>, Robert <bsi...@hotmail.com> wrote:
>For the record, i had my system set up static, obviously couldn't get
>anywhere since everyones ip address changed. I set up for dhcp and still
>couldn't get anywhere. Called tech support who as usual was very little
>help. The level ones like most companies are helpful to help newbies make
>sure everything's set right, but not much beyond that. Graduated to level 2
>tech, who seemed to know a bit more but she started BSing me near the end of
>the call just before everything started working suddenly. Access was
>intermittent for a few hours, today everything seems fine. Agreed, happy
>with the changeover- yeah, could have been alot worse.
>
>Downstream capped at 1.5? Anyone know what the rated bandwidth was
>originally?

A lot higher. The first week after the at&t installer came around,
I was getting on the order of 550mbytes/sec transferring large files
(and if the upload cap is there, I don't think I'll be doing much
of THAT anymore -- a few 700m OS install images a month and there
goes all my bandwidth.) I'd guess that the raw cable is capable of
10mbit and that's what @home was offering.

Another annoying feature of the at&t service is that I seem to be
having a hell of a time resolving domain names with the nameservers
they supply with their dhcp leases.

____
david parsons \bi/ And if I tell them I'm using a FreeBSD router serving
\/ a computer cluster and a pair of Windows clients, the
heads of the support staff will explode.

Chris Jaggers

unread,
Dec 4, 2001, 2:25:47 PM12/4/01
to
with the dns issues, look at my post higher up in the thread, it shows where all
the name servers are located. I'd suggest getting a program called visualroute and
entering the names into it, and see which NS is closest via ping.

John Meissen

unread,
Dec 4, 2001, 5:08:54 PM12/4/01
to
In article <9uhqrq$r...@pell.pell.portland.or.us>,

david parsons <o...@pell.portland.or.us> wrote:
>In article <oczO7.1852$Px.44755@rwcrnsc54>, Robert <bsi...@hotmail.com> wrote:
>>
>>Downstream capped at 1.5? Anyone know what the rated bandwidth was
>>originally?
>
> A lot higher. The first week after the at&t installer came around,
> I was getting on the order of 550mbytes/sec transferring large files
> (and if the upload cap is there, I don't think I'll be doing much
> of THAT anymore -- a few 700m OS install images a month and there
> goes all my bandwidth.) I'd guess that the raw cable is capable of
> 10mbit and that's what @home was offering.
>
More like 550Kbytes/s, probably. I belive the cable technology is
capable of 200Mb/s (bit/s), as opposed to the 768Kb/s or 1.5Mb/s
available from Verison DSL. So the current cap makes it ~100x slower
than it used to be. Of course, they probably connected to the system
with 10-baseT ethernet, so you only saw 10Mb/s out of that 200Mb/s
potential anyway. So I guess it's really only 10x slower.

john-


Scott Rainey

unread,
Dec 4, 2001, 6:32:14 PM12/4/01
to
Yup. Not however without having to read clueless websites and
talk to clueless tech support people. Old same things, really.

The big deal is to reboot your modem - power off for 5 minutes, then
reboot your system. Dunno what that accomplishes exactly but perhaps
the modem is designed to seek a new momma if the old one isn't there.

Change your settings: anything that was nnn.y...@home.com is now
attbi.com
mail.attbi.com
netnews.attbi.com
yourus...@attbi.com

PJ

unread,
Dec 5, 2001, 2:08:26 AM12/5/01
to
Now that sounds like what I was getting.
The fastest download speed I ever got was when I connected to the news
server.
anywhere off the local network was alot slower.
My cable modem is a 10baseT output only.

"John Meissen" <jmei...@shell1.aracnet.com> wrote in message
news:WPbP7.78672$Lc.26...@sjcpnn01.usenetserver.com...

Robert

unread,
Dec 5, 2001, 3:34:18 AM12/5/01
to
Don't know alot about this one, but some from when i installed cable modems
for at&t@home.. Provisioning a modem means someone on the at&t side tells
their computers that your modem has been assigned. Whenever that happens,
the modem needs to be reset because of who knows what- probably MAC
addresses have to be reregistered for the system to recognize traffic from
your modem as authorized.

When the changeover was made, from what i'm told, each modem had to be
re-provisioned one by one. which was causing alot of the problems.

re:
***


with the dns issues, look at my post higher up in the thread, it shows where
all
the name servers are located. I'd suggest getting a program called
visualroute and
entering the names into it, and see which NS is closest via ping.

***

Thanks, chris, i'll do that

"Chris Jaggers" <yeag...@home.com> wrote in message
news:3C0D2816...@home.com...

david parsons

unread,
Dec 5, 2001, 12:04:02 PM12/5/01
to
In article <3C0D2816...@home.com>,

Chris Jaggers <yeag...@home.com> wrote:
>with the dns issues, look at my post higher up in the thread, it shows where all
>the name servers are located. I'd suggest getting a program called visualroute and
>entering the names into it, and see which NS is closest via ping.

Bleah. G-d invented dhcp to handle those details, and it's too much
trouble for me to go in and manually edit /etc/resolv.conf every time
the dhcp lease renews.

[I wrote]


>> A lot higher. The first week after the at&t installer came around,
>> I was getting on the order of 550mbytes/sec transferring large files

^^^^^^^^^
550kbytes/sec.
A little different, but still a lot faster than the nominal 1.5mbit
that at&t is providing.

As more people are switched over to attbi, the cable is getting
slower. Ugh.

____
david parsons \bi/ At least I'm in range for DSL now.
\/

Robert

unread,
Dec 5, 2001, 4:45:28 PM12/5/01
to
Yeah, more and more people going broadband, by the time most people are,
companies like excite are bankrupt because they can't hold out long enough
to wait for everyone to switch to keep them out of the red. But by the time
that happens, DSL'l be the way to go since it doesn't share bandwidth with
all the neighbors. But then sharing is neighborly..

Rob

James Long

unread,
Dec 5, 2001, 10:46:14 PM12/5/01
to
david parsons wrote:
>
> Bleah. G-d invented dhcp to handle those details, and it's too much
> trouble for me to go in and manually edit /etc/resolv.conf every time
> the dhcp lease renews.

Agreed, although AYMK, you can (at least with BSD UNIX) run dhclient
in such a way that it will not overwrite /etc/resolv.conf.
man dhclient, noting 'supersede' and 'prepend'. You could either
supersede the nameservers with ones you like better, or at least insert
your favorite(s) at the beginning of the hunt list.

> As more people are switched over to attbi, the cable is getting
> slower. Ugh.

Almost as though it was a shared medium. :)

James Long

unread,
Dec 5, 2001, 11:03:11 PM12/5/01
to
Robert wrote:
>
> Yeah, more and more people going broadband, by the time most people are,
> companies like excite are bankrupt because they can't hold out long enough
> to wait for everyone to switch to keep them out of the red. But by the time
> that happens, DSL'l be the way to go since it doesn't share bandwidth with
> all the neighbors. But then sharing is neighborly..

It still shares bandwidth, just not as soon in the line from customer to
ISP. DSL is shared from the DSLAM on to the ISP. But the advantage for
the ISP is that if the DSLAM becomes oversubscribed, it's relatively
easy
to just buy more bandwidth between the DSLAM and the ISP. When cable
becomes oversubscribed, they have to physically sever the cable segment,
and physically install a second cable head at the point of the severance
to drive the new segment. Obviously, this requires a truck roll to do
the work, a new cable head every time they split a segment, and a new
feed
to service the physical location of the new cable head. DSLAM bandwidth
can be upgraded by the ISP just by buying more bandwidth from the LEC.
It doesn't require anybody to drive out somewhere and climb a pole, and
figure out a way to get a feed to this new cablehead out in the middle
of
nowhere. DSL bandwidth is always upgraded right at the CO, where it's
pretty darn easy to get bandwidth. Usually. ;)

So they're both shared, and yeah, if you're not publishing any web
content,
just downloading stuff without giving anything back, then cable will be
faster. But in an overloaded scenario, it's easier for a DSL ISP to fix
overloading than it is for a cable ISP to fix overloading.

david parsons

unread,
Dec 6, 2001, 3:40:51 AM12/6/01
to
In article <3C0EEA06...@nospam.museum.rain.com>,

James Long <james_...@nospam.museum.rain.com> wrote:
>david parsons wrote:
>>
>> Bleah. G-d invented dhcp to handle those details, and it's too much
>> trouble for me to go in and manually edit /etc/resolv.conf every time
>> the dhcp lease renews.
>
>Agreed, although AYMK, you can (at least with BSD UNIX) run dhclient
>in such a way that it will not overwrite /etc/resolv.conf.
>man dhclient, noting 'supersede' and 'prepend'. You could either
>supersede the nameservers with ones you like better, or at least insert
>your favorite(s) at the beginning of the hunt list.

When it was @home, the local proxy server was about 5 hops away from
my gateway, so that was one thing I didn't have to worry about (my
machine downtown -- also on @home, but on the business side[1] --
was a whopping 8 hops and 12 ms away from my house.

The AT&T dhcp provides me with 4 dns servers -- one in Los Angeles,
one in New Jersey, and two on the other side of gateway in seattle.
The slower ones are the first on the list. I'd forgotten about the
tweaks I could do to dhclient.conf, but, bleah, that's a pretty
dumb way to provision a network.


>> As more people are switched over to attbi, the cable is getting
>> slower. Ugh.
>
>Almost as though it was a shared medium. :)

Well, unless AT&T has materialized a bunch of new subscribers, the
people on the segment are the same people who were on there when
@home was providing the service. It got congested then during
the evenings, but not nearly as bad as now.


[1: Which means that it may keep connectivity until February, if I'm
lucky. Hope I can get a job before then so I can run a T-1 to
my house and not colocate at a more expensive place.]

____
david parsons \bi/ setenv DISGRUNTLED T
\/

0 new messages