Networking

[Sean]

On Sun, 7 May 2000, Paul Donahue wrote:

>  @home however goes to Detroit and is connected through New Jersey's
> internet pipeline (again this all to the best of my knowledge) and there it
> routes through @home's routers that I believe are out on the west coast.
>

when I did a traceroute on a @home machine, in indianapolis, the
connection went from here to san fran than back to indy. I dont recall
seeing a new jersey on it, but it may have. 

And you wonder why the network is flooded..
 
> Things to know:
> 
> - @home they have some weird configurations that require your computer to be
> a specific host name in order to remain talking on the network. This is ok
> as long as you don't care about being creative with the name of you Linux
> server. I have one that is like:
> c183601-a.elnsg.mi.home.com or something along that line.
 
horizon/millenium has the same thing, its the reverse dns entry, which
they told me for 5 bucks a month extra they would change it. *eyeroll*

The weird dns name isnt a problem for about 98% of the server things, it
only matters for things that do a reverse dns lookup on your connection,
IRC, BBS, some web based places, etc. 

> I setup everything
> like normal and have no problems with that service. I do recommend that you
> have a winblows box there for the "technician" (loosely defined) to setup
> the service, then after they pack up and leave you can port all the
> information over to your Linux box.

When I set up this machine. I didnt have an OS on it. I just asked for the
dns numbers, they plugged it in and I did an ftp install. I got a weird
look and the technician wasnt exactly sure what to say. but what can you
do when there isnt an os on it? 

I still havent let the cable guy touch the box. They dont "support" linux
and im not even sure they "support" macs.  
*shrugs*

Im not saying @home is the greatest service in the world, I know a few
people that love it and more than a few that either switched, or want to
switch.