From: Kirk Wood <cpt.kirk@1tree.net>
To: speakup@braille.uwo.ca
Subject: Re: Cable Modem
Date: Tue, 20 Nov 2001 00:27:45 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.21.0111200015520.24869-100000@ignatious> (raw)
In-Reply-To: <Pine.BSF.4.41.0111191747240.52009-100000@server1.shellworld.net>
On Mon, 19 Nov 2001, Amanda Lee wrote:
> Okay good enough. I was a little suspicious when he offered to rent us a
> second "static IP" for an additional $6.95 per month. Go figure! A
> little mixing of terminology to obscure the real truth. Another complaint
> I have about excite@home is that they won't allow you to use it for
> telecommuting and I find that to be an accessibility issue especially for
> those who are persons with disabilities because we all pay for our own
> broadband service no matter what we use it for. But that's not an issue
> we need to discuss here. DSL providers don't care or seem to want to
> prevent you from using your broadband connection for accessing your
> employer's network.
First, the second IP is just that. You can then put two computers on the
internet. Second, there is nothing to keep you from using your @home
connection to telecomute. They do not block any ports nor do they
routinely monitor anything. As for the Acceptable Use Policy (AUP) I just
checked it. The only thing that could possibly be construed to prohibit
using your service for telecomuting is that "The service may not be used
for comercial purposes." I have never heard of such being used to say you
can't connect to your corperate lan via vpn.
Key thing here: relax and breath. If you don't cause harm, they don't give
a rat's ass. Technically, I am hosting a server. But nobody has said
anything over the past three years I have been doing so. I telnet to my
home computer from work regularly. In the next week I will telnet from my
brother's pc. Nobody cares. Just protect your machine and don't let it be
a platform for someone to launch an attack. Don't try to run some
industrial grade server. Not only will performance suck with 128Kbit
upstream, it will piss someone off.
Do use your internet connection for any person (including doing your
personal work) thing you want. Just don't think you have a colocated
server.
=======
Kirk Wood
Cpt.Kirk@1tree.net
"When I take action, I'm not going to fire a $2 million missle at
a $10 empty tent and hit a camel in the butt. It's going to be decisive."
- President George Bush
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
I am now getting started Glenn Ervin
` Jacob Schmude
` Thomas Ward
` Dave Hunt
` Janina Sajka
` Dave Hunt
` Janina Sajka
` Dave Hunt
` lynx and ssl randy turner
` randy turner
` Jacob Schmude
` Shaun Oliver
` randy turner
` Cable Modem Amanda Lee
` David Poehlman
` Kirk Wood
` Amanda Lee
` David Poehlman
` Kirk Wood [this message]
[not found] ` <Pine.LNX.4.21.0111181954590.15589-100000@darkstar.example. net>
` lynx and ssl Adam Myrow
` I am now getting started Thomas Ward
` Kirk Wood
` Dave Hunt
` William F. Acker WB2FLW +1-303-777-8123
Cable Modem Dawes, Stephen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.21.0111200015520.24869-100000@ignatious \
--to=cpt.kirk@1tree.net \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).