Unfortunately, this seems to be too little too late for one user who's account has already been revoked for 90 days.
Roadrunner refuses to comment on the matter. Here is the former customer's side of the story.
You receive: 1 network interface card 1 Motorola CyberSurfer cablemodem 1 diskette containing the RoadRunner softwareThis is the service agreement that they wish you to sign. Read this before you sign it! Make the techinicials wait as you're getting charge $100 whether they are there for 5 minutes or 2 hours. There are several clauses and other fine print that users have repeatedly gotten burned about because management decided to change the way the service worked.
Critical sections include:
As of 6/2/97, they have started a commercial service. Same equipment, same connection, except you pay $149.95/month for a static ip address and $99.95/month for each additional ip address. Although they do not currently offer DNS services for their business plan, I have been informed that they have plans to do so.
However, a few of users have taken it upon themselves to "port" the login program to other plaftorms.
A brief description of a Linux RoadRunner setup.
(excerpt from a usenet post of mine)
As always, there has been a big clamor about dynamic ip addresses. In most cases, users do not need a static ip address. What you need is a static hostname. You want to make sure that everyone knows that your webserver is joeblow.san.rr.com. You don't/shouldn't care if the ip address changes every hr as long as the hostname maps to your machine. Kirk seemed intrigued by this idea and was going to pass it up the line. We'll see if anything will come of this. Users can implement this feature (static hostnames) themselves via a 3rd party until this is implemented by TW, if ever. There are organizations like http://www.dyndns.com and http://www.ml.org that offer this service. If your sysadmin at work requries that you have a static ip address in order to access the site, tell him to install ssh, http://www.ssh.org. As it does a local authentication and then a host authentication based upon info in your local config files, it does not care what the hostname or ip address of the machines are that are talking. I have ssh running on my home linux box, several work boxes that have a shared nfs mounted account and other ISP account that just recently changed hostnames. Ssh still works fine between them without changing a thing. At most, you might want to clean out your known_hosts file when you know that a hostname has changed.
Online Professional Xchange (OPX) is also offering this service. Contact David Bullock for details.
If you are using Netscape: Go to Options->Network Preferences...->Proxies->Manual Proxy Configuration Enter the hosts in the "No Proxy for" field. Netscape 3.x uses spaces to separate hosts and matches the end of a string. No wildcards. Minimal list should include: ams-server login-server:8081 ftp:// gopher:// 127.0.0.1 san.rr.com If you are using Internet Explorer: Go to View->Options->Connection Click on proxy settings. Enter hosts into the "Exceptions" box. IE uses ; to separate hostname. Minimal list should include: ams-server;login-server:8081;ftp://;gopher://;127.0.0.1;http://204.210.*.* If you are using lynx: 1) Edit your lynx.cfg and modify/add the following line: http_proxy:http://proxy-server.san.rr.com:8080 2) Contributed by Guy BerlinerTo use a proxy server with lynx, set an environment variable called PROTO_proxy, where PROTO is the protocol for which the proxy is used. For example, to set up an http proxy using the server proxye3-atm.san.rr.com, port 8080 in a Bourne style shell, add export http_proxy=proxye3-atm.san.rr.com:8080
| Questions/comments: | webmaster@seawood.org |