Date: Mon, 27 Sep 1999 12:04:57 -0400 (EDT) From: Nathan Stratton <nathan@robotics.net> To: "Charles A. Peters" <cpeters2@home.com> Cc: Dan Bongert <dbongert@ssc.wisc.edu>, freebsd-questions@FreeBSD.ORG Subject: RE: getting @home to work with FreeBSD Message-ID: <Pine.BSF.4.10.9909271201280.12795-100000@skipper.robotics.net> In-Reply-To: <000501bf0904$ca6fb1a0$0700a8c0@stealth.xxx>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 27 Sep 1999, Charles A. Peters wrote: > I know that this does not answer your question, but I have @home service, 3 > static IP addresses, and several machines connected to the internet via a > dual-hommed gateway. I find that it is convenient to be able to have a > static address in the event that I need to telnet or pcanywhere into one of > my boxes from another location. You can request a static ip address for no > additional cost from the @home people. I had @Home in Columbia, MD and now have it in Aliquippa, PA. In both locations they only provide static IPs. I did need to provide them a windows box to destroy with their software, but after they left connected it to my FreeBSD box and use NAT to give access to my 2 other windows computers. BTW, the thing that sucks about @Home is that they don't have peering with UUNet. They get their UUNet routes via CIX (I have the password to this router). So if you live on the east coast, your packets need to travel to Palo Alto, CA and back to the east coast, not to mention that UUNet has a crapy connect into CIX. :-( -Nathan > Charles > > cpeters2@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9909271201280.12795-100000>